Yes, I am stupid and I know it 😂 But I know lot of people that think just because something is mature, it must be worthless or dead. By the way, I think Fortran really just got resurrected from it's death.

No, I dont want to argue. Of course I can do TS in Node, but first TS was widely adopted later on than Node as far as I remember. And as I already said, I can equally use Haxe to generate JavaScript for Node as I can also use Haxe to generate PHP. I just think ... why should I switch from PHP exactly to Node when I can switch from PHP to any other technology (let's say anything from Elixir and Closure to Go and Rust). I assume some developers stay with PHP for serious reasons. :rolleyes:

TypeScript is a superset of JavaScript.

Correct, but it is still an improvement that JavaScrip neeeded, in my opinion. Of course, not everybody agrees or needs to agree. The whole point is that I could never switch to Node for backend (even though I've tried) because I found JavaScript too dynamic, even though I was writing JavaScript for the browser, but at that point I had no alternative, WASM to the rescue.

For me NodeJS or even Python was never a solution to replace PHP. First I would go for TypeScript instead of JS and Bun instead of Node/V8. Take a look at Bun — A fast all-in-one JavaScript runtime[^], you can run TypeScript with it directly (though it is internally converting it to JS not running TS directly). Probably a good replacement for PHP was Scala IMHO, not js, but that was in the past, now Lightbend prioritised Java support and that was a disaster for Scala. I personally now use Haxe to target both PHP and JS runtimes, Haxe is stronger typed than TypeScript and that's why I prefer it, at the same time I can target C# and Java runtimes from the same Haxe codebase (this is not possible with TypeScript yet). But unfortunatelly Haxe doesn't have php8 support yet. The advancements in php8 are stunning. You should take a look.