selenium creator here. hi!

Your indicator of technology maturity is "is there an autocomplete script for my shell" ? I have autocomplete working on any CLI app I make before it's even functional.

This has nothing to do with the "node world". Such an enormous feature would have to go into ECMAScript. Which is very, very unlikely to ever happen, they may as well design a new language. All those runtimes implement that spec. Expecting them to write an extremely complex new feature that is easily more complicated than everything already implemented (especially with backwards compatibility, and given that the language was not designed for this) would be a bit much.

TypeScript is for compile time checking of a language that was not designed to have them. Runtime types have very different requirements! It has to be in the language from the early design phase, otherwise it will just be a hack with many conditions, restrictions and holes.

TS Types are only partially a description of the underlying types in the code, a very big part instead is that it provides guard rails that prevent you from using a lot of perfectly fine and valid JS code that would however be incompatible with type guarantees. You pay the price of using only a part of the large space of JS code possibilities for guarantees. If you were to put that into the runtime you would end up with two different versions of the language. If you still want to support the full JS you would end with two runtimes in one (or one that has so many branches and conditions that maintaining that runtime is a real beast).

What backend framework is the go to these days? Still Express?

I agree. I've tried the Node TS and test runner features, and they are still (not yet) as good as Bun's. So for now sticking with Bun for those.

Really, in the Node ecosystem you eventually learn not to put all your eggs in one basket. Different things excel in different aspects. Here is my preferred setup for now:

Bun.js: As a Node runtime, and for TS execution and test running. I tried lots: TSX, TS-Node, Node itself

NPM For executing tooling scripts

PNPM For installing dependencies. It's simply better than the rest (npm, yarn, bun) for several reasons

Biome.js For linting (superior to every other tool I tried)

I’m not a heavy JS/TS dev so here’s an honest question: why not use Bun and forget about node? Sure I understand that not every project is evergreen but isn’t Bun a much runtime in general? It supports TS execution from day 1, has much faster dependency resolution, better ergonomics… and I could keep going.

I know I’m just a single data point but I’ve had a lot of success migrating old node projects to bun (in fact I haven’t used node itself since Bun was made public)

Again, I might be saying something terribly stupid because JS/TS isn’t really my turf so please let me know if I’m missing something.

> Not familiar with that but I imagine that is going to be a controversial statement.

I'm not sure if it's fair to call it rigging, but there was a massive smear campaign against a judge nominated for their constitutional court. Leading to the nomination being withdrawn when it really should've been an appointment as usual. Which is likely the first massive step toward Germany politicising one of the foundations of their democracy, similar to how the USA supreme court seems like it's red vs blue when looked on from the outside.

I'm guessing this conference is rather left leaning, which is why they'd called that rigging, but there wasn't election fraud. It's an issue of course, since this means that rich people can essentially buy massive influence on the German democracy by clever use of social media and lies. Which may seem like the norm to a lot of people on HN, but that's not how it has traditionally been in Germany.

> We start to see unrest and/or riots against "the rich" because there are no jobs, and people are being evicted

I am surprised this has not already happened. The combination of rampant inequality and lax gun laws (in some states) is very explosive.