News for hackers. Stuff that matters.

A comment on Deno's Decline. Parent comment

Re:Deno's Decline by andrewmcwatters on Thursday May 01, 2025 @10:48PM (#43865671)
You avoid much of this by ignoring new things that are new for the sake of being new. Imports instead of require? Waste of time. TypeScript? Waste of time. Widely unpopular opinion. Package managers other than npm? Waste of time.

Just ignore it all and you're fine. And definitely ignore the people who keep changing things on you.

If it doesn't help me ship more product, I do not care.

[ Parent | on HN ]
Re:Deno's Decline by danpalmer on Thursday May 01, 2025 @11:45PM (#43865997)
Moving to Typescript may be unnecessary, but starting a brand new codebase in 2025 and using JavaScript instead of Typescript is a hard one to defend. The fact that Node.js doesn't support it out of the box, let alone encourage it as the default, is much of the reason why the community is constantly clamouring for something better.
[ Parent | on HN ]
Re:Deno's Decline by curtisblaine on Friday May 02, 2025 @01:56AM (#43866598)
Node.js supports typescript out of the box by stripping types since node 22 (current LTS is 24, iirc)

https://nodejs.org/en/learn/typescript/run-natively

[ Parent | on HN ]
Re:Deno's Decline by andrewmcwatters on Friday May 02, 2025 @10:44AM (#43870532)
It’s pretty easy, its not necessary.
[ Parent | on HN ]