It's so sad that node refuses to add websocket server support.
Adding websocket would simplify stuff tremendously, as well as make deployments much, much more secure.
Node.js 26.0.0 (Now with Temporal)
21–30 of 63 posts
Re: Node.js 26.0.0 (Now with Temporal)
#22Off-topic but, Safari seems to be the only browser that doesn't support Temporal yet. It looks like the only blocker for adopting it on web.
Re: Node.js 26.0.0 (Now with Temporal)
#23Also the release that drops typescript transforms: https://github.com/nodejs/typescript/issues/51 (I’m not disagreeing to remove it. It just took me a while to find out what happened to it)
Initially it didn't make sense to me... but it looks like type striping is really the way to go for future TS.
There's the "types as comments" proposal[1] which could even land on browsers one day.
I started using the erasableSyntaxOnly setting in my tsconfig to get ready for this.
Re: Node.js 26.0.0 (Now with Temporal)
#24Node JS team should look into bun and make progress. They are somewhat stable, but bun have lot of features and is more performant than Node.
/s ? Bun is not yet (ever?) compatible with Node. I'm sure if Node JS could trim the fat with breaking changes they'd be fast too
In my testing Bun wasn't much faster most of the time, usually on par for all non-IO related stuff, and there were some cases with scheduling where Bun was noticable slower.
Re: Node.js 26.0.0 (Now with Temporal)
#25It's so sad that node refuses to add websocket server support. Adding websocket would simplify stuff tremendously, as well as make deployments much, much more secure.
Why more secure?
I see that Deno has WebSockets, but I've never used them: https://docs.deno.com/api/web/~/WebSocket
Re: Node.js 26.0.0 (Now with Temporal)
#26> Upsert (https://github.com/tc39/proposal-upsert): [Weak]Map.prototype.getOrInsert(), [Weak]Map.prototype.getOrInsertComputed()
Their usage of upsert appears different than I was used to:
Me: Upsert = Update or Insert
Them: Upsert = Get or Insert
Re: Node.js 26.0.0 (Now with Temporal)
#27Earlier quoted context omitted.
/s ? Bun is not yet (ever?) compatible with Node. I'm sure if Node JS could trim the fat with breaking changes they'd be fast too
I expect bun to run almost everything that node runs these days. They have an extensive test suit to ensure that. Even the complicated NextJS runs with Bun: https://nextjs.org/conf/session/nextjs-bun Do you have a source for your claim?
[deleted]
Re: Node.js 26.0.0 (Now with Temporal)
#28Node JS team should look into bun and make progress. They are somewhat stable, but bun have lot of features and is more performant than Node.
I see no reason to leave node in what concerns JavaScript runtimes.
Re: Node.js 26.0.0 (Now with Temporal)
#29> Upsert ( https://github.com/tc39/proposal-upsert ): [Weak]Map.prototype.getOrInsert(), [Weak]Map.prototype.getOrInsertComputed() Their usage of upsert appears different than I was used to: Me: Upsert = Update or Insert Them: Upsert = Get or Insert
The proposal used to do more thing and we didn't change the URL after we ultimately arrived at this set of APIs.
Re: Node.js 26.0.0 (Now with Temporal)
#30Tangent: if you use Node.js at build time you should check out VitePlus https://viteplus.dev (No affiliation, just a fan of VoidZero's consistently excellent tools.)
Looks interesting, what's their revenue model? Or how do we know it won't be abandoned in the near future?
The same as any other dev tool startup, once money gets tight they will monetize and users will rightfully revolt.
Evan You won't break the cycle, tale as old as time.