←back to thread

The tragedy of running an old Node project

(abdisalan.com)
272 points abdisalan | 1 comments | 18 Nov 24 18:24 UTC | HN request time: 0s | source
Show context
binarymax ◴[18 Nov 24 18:57 UTC] No.42175675[source]▶
I always try to remember to put the node version in my package.json - but I do agree that the dependency chain on node-gyp has been a blight on node packages for awhile. Really wonder how that wart became such a critical tool used by so many packages.
replies(2): >>42175709 #>>42175766 #
ramesh31 ◴[18 Nov 24 19:01 UTC] No.42175709[source]▶
>Really wonder how that wart became such a critical tool used by so many packages.

The original dream for Node was that it would simply be a glue wrapper around libuv that allowed for easy packaging/sharing of modules written in C++. But everyone just started writing everything in JS, and the ecosystem ended up as a mish-mash of native/non-native. Ryan Dahl stated this was indeed his biggest mistake/regret with Node, thus we have Deno now.

replies(2): >>42175791 #>>42182330 #
watt ◴[19 Nov 24 11:34 UTC] No.42182330[source]▶
What is the Deno solution though? (I assume it's not sharing modules written in C++?)
replies(1): >>42182468 #
1. DecoySalamander ◴[19 Nov 24 11:54 UTC] No.42182468[source]▶
Deno's solution is coming out years later when JS is fast enough that there is no need to involve C++ for most applications.