Node.js 26.0.0 (Now with Temporal)
nodejs.org
Node.js 26.0.0 (Now with Temporal)
1–10 of 63 posts
Re: Node.js 26.0.0 (Now with Temporal)
#2I'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.
Re: Node.js 26.0.0 (Now with Temporal)
#3I'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.
Until then, a solid backfill has been available for quite some time
Re: Node.js 26.0.0 (Now with Temporal)
#4I'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.
Re: Node.js 26.0.0 (Now with Temporal)
#526.2.0 is already out, why link to the previous release?
https://nodejs.org/en/blog/release/v26.2.0
What I would expect with the inclusion of temporal, is having a section on nodejs docs about Rust addons, alongside the C and C++ sections.
Re: Node.js 26.0.0 (Now with Temporal)
#6Node 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.
Re: Node.js 26.0.0 (Now with Temporal)
#7I'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.
i'm pretty sure all that stuff works w/ Temporal... Temporal is extremely well-designed, in my experience. the js date object, on the other hand, has insane pitfalls, and i say this as someone who thinks not understanding JS ASI is a "skill issue", among other happily-un-"ergonomic" worldviews...
Re: Node.js 26.0.0 (Now with Temporal)
#8Node 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
Re: Node.js 26.0.0 (Now with Temporal)
#9Node 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.
they should rewrite their whole stack by AI from one language to another language, it seems fun.
Re: Node.js 26.0.0 (Now with Temporal)
#10Node 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
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?