Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Node.js 26.0.0 (Now with Temporal)

nodejs.org

Post reply on HN
Print view View original

31–40 of 63 posts

Re: Node.js 26.0.0 (Now with Temporal)

#31

Post by xkcd-sucks »

HatchedLake721 wrote: post #8
cute_boi wrote: post #6

Node 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

Honest question, what isn't compatible? Where I work we've simply replaced node with bun across a lot of overcomplicated + crappy projects, and on my work+personal computers I alias bun/bunx to node/npx with seemingly no issues at all

Re: Node.js 26.0.0 (Now with Temporal)

#32

Post by manniL »

shimman wrote: post #30
rumblefrog wrote: post #18

Earlier quoted context omitted.

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.

VoidZero's business model is in Void, their deployment platform. Open source projects will always stay open source. This was announced at the very beginning.

Re: Node.js 26.0.0 (Now with Temporal)

#34

Post by owebmaster »

skybrian wrote: post #25
emilfihlman wrote: post #21

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.

Why more secure? I see that Deno has WebSockets, but I've never used them: https://docs.deno.com/api/web/~/WebSocket

"ws" is regularly the only package in my package.json

Re: Node.js 26.0.0 (Now with Temporal)

#36

Post by kaoD »

jpsimons wrote: post #4
noodlesUK wrote: post #2

I'm really looking forward to the temporal api being universally available. Moment and Luxon are fairly good but sensible date/time handling is something that really ought to be baked into the platform ootb.

I always thought the old Date is kind of elegant... increment anything with an overflow and it all wraps around correctly, like `d.setDate(d.getDate() + 100)` to advance a date 100 days. "March 208th" is interpreted like you'd expect, as are the hours and minutes and such. Of course, complete lack of non-local non-GMT time zones is a huge downside.

That's how you get date bugs.

Re: Node.js 26.0.0 (Now with Temporal)

#37

Post by lioeters »

shimman wrote: post #30
rumblefrog wrote: post #18

Earlier quoted context omitted.

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.

After getting burned so many times on libraries, frameworks, services and platforms, even entire languages - one learns to be wary of critical dependencies. Every new project offers convenience in exchange for you giving up control of part of the software stack, and the power dynamic is often exploited sooner or later as revenue source. You can't trust anything that becomes irreplaceable, or that you can't write it (or at least understand it) yourself.

Re: Node.js 26.0.0 (Now with Temporal)

#38

Post by shimman »

manniL wrote: post #32
shimman wrote: post #30

Earlier quoted context omitted.

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.

VoidZero's business model is in Void, their deployment platform. Open source projects will always stay open source. This was announced at the very beginning.

Yes, nothing different from any other VC dev tool startup. When the community fractures people simply move on to something else. See rome -> biome for a very recent example.

Re: Node.js 26.0.0 (Now with Temporal)

#39

Post by OptionOfT »

jdthedisciple wrote: post #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

Reminds me of the weird C++ map operator[] behavior.

If you use that operator and the value doesn't exist, it'll default create one and return a reference to that.

And as I'm writing this I realize why... references cannot be `null`.

Post reply on HN