You just press backspace and hit the accent mark key or for a printing press stack the accent mark on top of the letter. People ditched accents because they were rarely used in English writing (only really being used for some loanwords), not because simplifications were forced by typewriters or the printing press (which handle non-English languages just fine).
"This is why Hebrew's alphabet near-perfectly phonetically represents the spoken language" - nonsense. That's just because modern Hebrew is based on the written language and thus reflects spelling pronunciation rather than historical pronunciation.
Also, proto-Sinaitic is not an alphabet. That's why Persian writing became harder to read when they switched from the nearly alphabetic Old Persian cuneiform to Aramaic abjad descended from proto-Sinaitic.
Why go through the trouble of shoehorning SQLite into a cloud database by getting solutions for HA/failover and DR, when you can just use Postgres off the shelf?
Interesting project in general. I wonder whether it could be adapted to behave reasonably without relying on threading. E.g. run the GC only when *alloc is called.
What's a situation where one needs to use `eval` in benign way in JS? If something is precomputable (e.g. `eval("1 + 1")` can just be replaced by 2), then it should be precomputed. If it's not precomputable then it's dependent on input and thus hardly benign -- you'll need to carefully verify that the inputs are properly sanitized.
I would argue that hardened mode should be default though, similar to how siphash is the default hashing function in Rust hash maps. Faster mode should be opt in if the user is confident that the supplied data is nonmalicious and they need the speed up.
I've worked on optimizing modern slow code. Once you optimize a few bottlenecks it turns out it's very hard to optimize because the rest of the time is spread out over the whole code without any small bottlenecks and it's all written in a slow language with no thought for performance.