Eh ECS is basically all about making SELECT ... FROM bar, baz WHERE bar.id == baz.id, joins on primary keys, as fast as possible and use it as often as possible. Games are real-time databases with gaudy user interfaces so it stands to reason that posgresql is a game with a bland user interface.

There’s plenty of schemes that aren’t fully standards-compliant but I don’t think leaving out eval is common – it’s easy to implement and nothing about the standard says that it needs to run code fast.

Just wanted to point out that eval is the real static vs dynamic boundary. As to evil, sure, you shouldn’t run just any code you find without having a sandbox in place, C’s way to do the same thing is to call cc followed by dlopen, that’s way scarier, which is why people just link in lua or something instead. I guess in <currentyear> you should probably include a wasm runtime instead of using dlopen.

Fork. Setting up a whole new project infrastructure, getting fellow developers on board with your putsch and everything can be a PITA but all those are natural hurdles, due to how the licensing works the BDFL has no way to stop you.

As such, as a BDFL you rule by the grace of authority of the bootmaker. If you don’t make sense, if you aren’t respected, sooner than later the community is going to leave you behind.

Rust has affine types and gets close to linear when you include #[must_use] (you can still let _ = foo but at least it won’t be an accident, also, drop code isn’t guaranteed to run and there’s good reasons for that), refinement types there’s a library for that. GADTs… I mean sure trait magic can get annoying and coming from Haskell you’d want to do more in the type system but in the end the idiomatic rust way to do many of those things is with macros. Which, unlike Haskell, Rust actually is really good at. Really good. Tack refinement types onto the language kind of good.

Proving tools, honestly, there’s only one piece of actually proven software (SeL4) and the only language it’s really written in is Coq. Which Rust will never, ever, compete with on its home turf.

Any language containing eval in its spec cannot be (fully) compiled ahead of time, you’ll need interpretation or JIT.

Also last I checked (it’s been a while) Racket compiles to bitcode and then links in a bitcode interpreter. There’s static lisp/scheme compilers but when they come across an eval, they’re going to bail and compile in a JIT compiler or interpreter to deal with that stuff.