NodeJS 22 Just Dropped, Here's Why I'm Hyped 

There wouldnt be a need for a build system if ESM didnt exist to begin with (not to mention with ESM there it's a problem for everyone not just the package devs). And so far, outside of some specific development-only scenarios that could have been achieved either way with just a slight change to the spec (just make default require not dynamic or error out for those builds), every promise ESM has made has not been fulfilled in any meaningful way that's useful for things we ship. Need to ship code? you're still bundling even after years of this thing being out, the only difference is you now have to do it while there's this holy war of CJS vs ESM in the background and have deal with nonsensical problems caused by it. This idea of "only browsers matter" is also extremely unhealthy stance to take to base one of the key features of the language.

@@felix_xb ESM design had a massive design flaw, if it had of gone `from "module" import { method }` , at least if node did implement we would have had better code completion, and that would have given us at least something better than CJS.. :)

Word. 💯

Great to hear all that. BTW it would be great to know some direction on learning how to write NPM packages and some tips.

They've been gatekeeping NodeJS from adding these cool features, because "it shouldn't be part of NodeJS", but suddenly when they got a bit of competition they started implementing them. They did add them in a short period of time, so unsure how stable they are

It's just a cultural thing with the way he speaks, combined with him wanting to keep his tone and content mostly positive. Personally, I appreciate it. Snarky criticism gets more views, but this man doesn't encourage the habitual, seething negativity that many do. We can all be thankful he's not reading stuff like a reporter at a television news desk or baiting us with his sexual or parasocial charms either. 😉

@@tantalus_complex He used to be a lot more snarky before. I can't lie, I'm probably more happy than not that he's shifted. Feels more mature and respectful. Sometimes it's fair to be bothered by things, but when you're bothered by everything (especially when it stems from lack of understanding) it's just kinda frustrating to watch lol. But then I have also focused on reducing rage bait in my life. It's nice.

it's the stash

Still both a runtime. Comparing them makes perfect sense

😂😂😂😂

JITties sorry

Doesn't take much to hype him up

When you commit to keeping your community mostly positive, it's almost unavoidable that you come off that way.

I’d love to see that too

bun team has a nice article on this

@ronaru link it

You should've paid attention to History of JavaScript class 😂

If you are still using anything else than ESM at this point, you missed out for a few years 😬

Not so bad honestly

The tutorial was nuts 🥜

But to be fair that's not a Node issue but an Angular one, it's similar with binary packages, and if the dev of the package doesn't do a binary build for it, again it's not really NodeJS fault. I would also say it's not a JS issues either, other languages have issues if the dev's of package X don't come out with updates for a new feature / breaking change in language X.

​@@keithjohnson6510 that's not what I said, I said the problem is NPM modules failing to keep up so they break, angular cli was using some module that only support node 18 till I logged a bug to get it fixed with the maintainer. So indirectly it's going to be a problem with node if you can't simply just install the latest node LTS, unless you code with js and have zero depencencies with node modules. Coding is JS sucks, there is way too much constant change causing stuff to break, get deprecated in toolkits that you're forced to keep up to date, then some idiot hipster decides they going to change how we all should do X because the new way is more cool. These Clown don't understand or respect backway compatibility. Imagine the web breaking because some clown decides to change how HTML, CSS should work or be coded. Just remember all we're doing is rendering a web page, and handling dom events. This doesn't need constant churn. For a node server it's dealing with simple request / response. Only express js and or Koa have stayed unchanged, increasing ROI and developer producitivity. Who needs to waste their time fixing code when you do an update and now something is broken. JS coding is futile, it's full of hipster clowns doing agile releases. Why should anyone have to keep re-learning and fixing working code?

​@@sonicewave NodeJS came out over 14 years ago, but to be fair it's backwards compatibility has been pretty good. Yeah, upgrading to newer versions of node doesn't always go smooth, my main issues have been when binary packages don't get updated quickly. You could say JS has it's flaws, like many other languages I use, but a good experienced coder doesn't bitch about his tools, but adapts to it's Pro's & Con's. Can you image the developers of uTube and all the websites you visit, just spitting there dummy out and saying, JS is just a Joke, Nahhhh!!.. Now sonic, pull yourself together, re-read what you have just posted, and say to yourself, "Am I really that person?". I believe in you, you just need to believe in yourself.

For production you should always use an LTS release unless you really don't have any other option.

"...using RegEx and iterating over reddit" was almost the best troll comment I've seen in a while, even if it was accidental.

Yes

I think is warp

Wait nevermind, theo just made a oof. He confused me there for a second now I've got it.

Arc

Yeah, but that has nothing to do with watchman. This is talking about watching for file changes, a build system doesn't watch for file changes, it checks for file changes when you request a compile. In fact watching for file changes over network shares is still pretty lame, and poling needs to be used. BTW, this is nothing to do with Node either, it's just that OS's have not always been great at exposing a file change callback api.

@@keithjohnson6510 Maybe you're looking at the wrong thing, but the Watchman he references does indeed watch for file changes. A distinction for when the build system does anything is irrelevant unless you're saying that the project he was referencing that supposedly used Watchman didn't actually use Watchman. If that's the complaint, then you'll have to take it up with him.

@@anon_y_mousse So what's your point on a build system and comparing timestamps got to do with it?.. Comparing timestamps is not the same thing as making the OS watch for file changes.

@@keithjohnson6510 He used it as an example. I criticized such a usage. If he was erroneous in it being used for the purpose stated in the video, then take it up with him.

@@anon_y_mousse Take what up with him?, Theo mentions what a pain watchman was for watching files, to known "WHEN" to do a build. And again what has that got to do with how a build system compares dates when "DOING" a build?. I'm really finding it hard to see what point your trying to make here. Yes, we all know how say a C++ compiler works etc. Are you just saying it's funny that he used a 3rd party service to watch for file changes, seems a strange thing to find funny, because how you watch for file changes in Windows is totally different to Linux, that is again different to Mac, sure maybe Theo should have spent time writing all this, instead of using a 3rd party lib.

No, and you should not use Windows 7, it's end-of-life.

please don't use windows 7, it dosen't get security fixes anymore (and no, just not downloading sketchy programs won't protect you, RCE vulnerabilities exist)

lambda functions ? we already have function expressions and arrow functions

@@moussaadem7933 AWS Lambda. The video mentioned it as well.

Gotta pay the bills bro, I don’t blame him

Lambdas can be way cheaper though if you expect little to no, or spiky traffic. Idk about vercel

He sells a service, and his mindset is that people should pay for what they can have for cheap.

How about a C compiler targeting WASM? 🤣

@@anon_y_mousse yes, that's Emscripten? what's so funny about that?

@@somenameidk5278 I guess you'd have to be into C to get it.

I came from my mothers ass

JAAA PIERDOLE, POLSKI PROGRAMISTA!!

Polska gurom 💪🇵🇱

Als deutscher Ingenieur bin ich da anderer Meinung

Insert Obama honoring himself meme

My mother was born in Poland (my grandparents escape from aegean, greece calvary against them, expelled) and I can take polish citizenship, but I don't like, because they don't support Russia

Old man yells at the sky

Node is good on the server. Its just less good than about 10+ other options and more or less exists for those who cant be bother to learn any of them

Honestly I would like to move to Go or C#, but at this time it's just more efficient to remain on TypeScript+ Node. Is it perfect? No, but it's good enough. Is it the fastest? No, but it can handle more requests/s than the APIs I'm building will ever need, plus we use serverless anyways so they would easily scale to the point the DB would be the bottleneck way before a large bill would come. I'm happy with TS and the Node team are doing a killer job at improving performance, capabilities and security and it shows. Don't forget it's all C++ underneath via libuv, so they can tap into serious gains that way

@@boscodomingo When your database is a bottleneck, you add a caching layer or you add another node to your cluster, or you do both. I prefer Go for its ease of use and actual concurrency. The performance gains are indeed massive too.