PHP is too high level for this task - might as well write Rust compiler in a Tiring Machine.

That’s true for any software project - on average only 5% goes into developing of the first version, while 95% goes into continuous development, support, and maintenance.

unsurprising, since they're also into Monoliths

https://www.youtube.com/watch?v=cHWs3c3YNs4

wait until they hear about microservices

just use TSV instead of CSV by default

Om = Forth + Tcl ?

We've already seen Forth + Lisp

What's next? Lisp + Tcl ? Or maybe: Lisp + Forth + Tcl ? ;)

Forth + APL: Uiua

There are also APL + Lisp variants, like April, or even q from kdb+/q (kinda like Lisp but without parens).

---

The APL programming language (a subset thereof) compiling to Common Lisp.

https://github.com/phantomics/april

APL and LISP—should they be combined, and if so how?

https://dl.acm.org/doi/10.1145/800136.804474

So UUIDv∞ will be at least 536 bit long?

And with group IDs, timestamp, etc. - 1024 bit long?

Say “halting problem” without saying “halting problem” ;)

There is a practical solution to it called “metering”, like gas mechanism in Ethereum’s EVM or cost calculation for complex GraphQL queries.

Yeah I think it's typically called "fuel".

A better solution would be first-class metaprogramming, like in Zig or LISP. Maybe with some subset which guarantees to halt (I.e. no unbounded loops, no recursion, no FFI, known input size, hard time limits, etc.)