Good data (and program) structures are definitely quite important. Well chosen structures make implementation much easier (and likewise bad structure makes things needlessly difficult).
Also, the film editing example is also an example of a piece table, which makes cutting very simple. Cutting out a section is just a node insertion + update the end of the original node ({0-3} -> {0-1}, {2-3}).
I’ve had similar issues as well very rarely with other languages. I’d type out a bit and get a syntax error, but when I complete the partial code it won’t update the errors. When that happens restarting the language server tends to fix it, so I presume the language server just locks up sometimes.
Self-plagiarism to me is more of a related but separately defined term from “true plagiarism,” but defining it based on work rather than author does make a lot of sense.
How do you define the two terms? I’m genuinely curious since the definitions I’ve seen for the terms imply that it is a type of plagiarism, but they definitely don’t have the same connotations.
Plagiarism is misrepresenting someone elses’ work as your own, so wouldn’t having a ghostwriter write “your” article still be plagiarism regardless?
Strings work fine, the problem is the (single) quotes:
~ $ foo="echo 'hello world'"
~ $ for x in $foo; do echo $x; done
echo
'hello
world'
~ $ $foo
'hello world'
~ $ eval "$foo"
hello world
The splitting is by whitespace, so the single quotes remain in the arguments. Using eval (and double quotes to preven splitting), it gets processed correctly. That said, don’t use eval; use functions or aliases instead.
The paper for the trolly problem has some interesting details. In experiment 2, those who considered themselves worse at the foreign language were more likely to make the utilitarian choice, which indicates that it might just be a matter of proficiency in the language, rather than whether or not it is the participant’s primary language.
The Temple examples look very nice; the Builder ones to my eye look quite cluttered in comparison, which I’m guessing is due to differences in syntax between their respective languages.
I tink the main downside of templating in general is that it ends up making interfacing with JavaScript and plain HTML harder, compared to CustomElementRegistry based components.
Karax has the appeal that it is just Nim code, so there is no new syntax.
Now I kind of want an linter that checks that compound words in a given dictionary are joined, and those that are not are separate…
The example implemented in Mithril.js, for comparison.