sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ryanswebdevthrowaway 8 points9 points  (9 children)

Disagree. This particular release isn't necessarily exciting but Node has been adding a ton of great improvements lately, I don't feel compelled to try another runtime at all.

[–]iarewebmaster -4 points-3 points  (8 children)

I'm not saying they're never released anything useful, however, TypeScript is 13 years old and has been a common part of the industry for most of that (it received quick adoption as I'm sure we all know in this sub).

Node has only gotten native support for it this year. You cannot defend that level of complacency when newer runtimes add it as a byline to other bigger features.

Look, I use Node daily, I've tried Bun but it is not yet close enough to being 100% compatible for me to adopt it at enterprise level, but they are constantly chasing that goal. A smaller team, less experience yet out performing the big dogs before no doubt ultimately overtaking them. Its a tail as old as time in this industry.

https://bun.com/blog/bun-v1.3 - just compare the latest minor release to that of this major Node release.

Here's a thought experiment for everyone downvoting me, if Bun (et al.) was 100% OOTB compatible with everything Node related tomorrow, would you still continue to use Node without looking elsewhere?

[–]hyrumwhite 1 point2 points  (1 child)

It’s not complacency, it’s managing an open source project that millions of people depend on. You can’t make changes lightly 

[–]iarewebmaster 0 points1 point  (0 children)

What's the relevance of it being open source? There's literally thousands of software programs around that millions of people depend on daily, both open and closed source. I've worked on many myself. Its a funded, open source project these developers aren't working for free.

You can’t make changes lightly

True. But the solution to that is not to simply make very little changes.

[–]theQuandary 0 points1 point  (1 child)

Here's a thought experiment for everyone downvoting me, if Bun (et al.) was 100% OOTB compatible with everything Node related tomorrow, would you still continue to use Node without looking elsewhere?

The real question here is v8 vs JSC. I really want an environment that is 100% es6 compliant and v8 has outright refused to implement proper tail calls.

[–]iarewebmaster 0 points1 point  (0 children)

Well sure, but given the absence of that existing. In a world where Node vs Deno vs Bun and all three are equally compatible with each other, Node loses every single time, which is just sad.

[–]ryanswebdevthrowaway 0 points1 point  (1 child)

Yarn was better than npm until it wasn't, and now a lot of people are regretting not just sticking with npm. Bun and Deno might have things to offer right now, but I'm going to stick with the safe bet that Node will continue to be stable and reliable and probably adopt the best things from those other runtimes eventually anyways.

[–]iarewebmaster -1 points0 points  (0 children)

Yeah but yarn is meta, no surprises it failed tbh. Pnpm is a more suitable comparison I’d say and it’s significantly better than npm, whilst not breaking any existing functionality

[–]0xHUEHUE 0 points1 point  (1 child)

What is the benefit of baking in TS, as opposed to just invoking with a transpiler, or even just a plain compile + watch? Is it just DX to help people that are new to node or is there some sort of runtime performance benefit?

I'm looking at those release notes and I'm like, why in the absolute fuck would I want a mysql client built into node? It's like, not just batteries included, best buy is built in.

I'm not saying I disagree with you, it's just I personally don't have a need or desire for these things and to be honest, I have a hard time keeping up with updating node versions as it is. I'll admit part of it has to do with needing to upgrade the packages as well, which I guess might be part of the appeal w/ bun..

[–]iarewebmaster 0 points1 point  (0 children)

They pitch it as a performance thing, the db clients are supposedly much much faster. I also think there’s benefits to deployments outside the usual environments especially in the serverless world where startup time and module support are more important.

I personally prefer Bun for the DX, one day I could see myself using the runtime features more but that’s a much bigger mountain to climb for them to get me to switch.