▲ | ramesh31 7 days ago | ||||||||||||||||||||||
>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. | |||||||||||||||||||||||
▲ | com2kid 7 days ago | parent | next [-] | ||||||||||||||||||||||
> But everyone just started writing everything in JS, and the ecosystem ended up as a mish-mash of native/non-native. Because the native written stuff breaks all the darn time and it creates cross-plat nightmares. My stress levels are inversely proportional to how many native packages I have to try to get building within a project, be that project in Python, Java, or JS. JS+Node runs on everything. Prepackaged C++ libraries always seem to be missing at least one target platform that I need! | |||||||||||||||||||||||
| |||||||||||||||||||||||
▲ | watt 7 days ago | parent | prev [-] | ||||||||||||||||||||||
What is the Deno solution though? (I assume it's not sharing modules written in C++?) | |||||||||||||||||||||||
|