Either you don't understand what you're talking about, or your sarcasm is god tier.
You state: Go and Rust have grabbed mindshare for "stuff better than node".
I agree, particularly in the case of Rust. Considering things like dav1d (AV1 codec), WASM, and other projects of significance that will be of consequence to the web are written in it.
So do you know what one of the differences between node and deno is? Deno is written in Rust. Node still uses C/C++ via libuv...
Do you often contradict yourself? By your own logic, the first sentence of your comment is invalidated. 😁
Furthermore while Deno may not have a mature ecosystem internally (i.e. centralized tooling / repositories) currently giving off vibes of fragility, instead i suggest looking at how it will be supported externally. Example?
Microsoft are the proponent of typescript (arguable a very good preprocessor along with elm for JS), they also own github, npm and VScode.
With that in mind. Now ask yourself. Which of the 2 runtimes would MS rather support moving forward?
nodeJS: full of legacy hacks to make modules work that are not to spec, npm... a system they didn't really have much input in creating.
deno JS: Secure by default, native TS support, adheres to spec, has no centralized repo yet (opportunity to be active from the beginning in it's development), etc.
Furthermore consider for a moment electron. Electron also currently uses the node runtime and is quite difficult to compile with C/C++ modules. Compare that to Rusts crate system and ask, now that V8 has been implemented in Rust, how long before electron becomes obsolete (e.g. turn it into neutron or something 😂)?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Either you don't understand what you're talking about, or your sarcasm is god tier.
You state: Go and Rust have grabbed mindshare for "stuff better than node".
I agree, particularly in the case of Rust. Considering things like dav1d (AV1 codec), WASM, and other projects of significance that will be of consequence to the web are written in it.
So do you know what one of the differences between node and deno is? Deno is written in Rust. Node still uses C/C++ via libuv...
Do you often contradict yourself? By your own logic, the first sentence of your comment is invalidated. 😁
Furthermore while Deno may not have a mature ecosystem internally (i.e. centralized tooling / repositories) currently giving off vibes of fragility, instead i suggest looking at how it will be supported externally. Example?
Microsoft are the proponent of typescript (arguable a very good preprocessor along with elm for JS), they also own github, npm and VScode.
With that in mind. Now ask yourself. Which of the 2 runtimes would MS rather support moving forward?
nodeJS: full of legacy hacks to make modules work that are not to spec, npm... a system they didn't really have much input in creating.
deno JS: Secure by default, native TS support, adheres to spec, has no centralized repo yet (opportunity to be active from the beginning in it's development), etc.
Furthermore consider for a moment electron. Electron also currently uses the node runtime and is quite difficult to compile with C/C++ modules. Compare that to Rusts crate system and ask, now that V8 has been implemented in Rust, how long before electron becomes obsolete (e.g. turn it into neutron or something 😂)?