3 ms·

Justification is so weak it's literally just rewrite it in rust because I wanna

winrid 1y ago
Getting Node installed is a blocker for some of their customers, evidently. It doesn't surprise me. If it holds back one mid sized enterprise customer, the rewrite is worth it.
- rcleveng 1y ago
  It's a blocker for many windows enterprise customers. The suggested way is to use nvm to manage it (link: https://learn.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-windows https://learn.microsoft.com/en-us/windows/dev-environment/ja...). This needs admin permissions, which means a ticket with IT and a good chance it'll be rejected since it's scary as it'll open up the door to many admin level installs of software that IT has no control over. Installing node under WSL is a better approach anyway, but that'll make it harder for enterprise customers still.
  - pjmlp 1y ago
    It can literally be a zip that one unpacks somewhere and sets the PATH. https://nodejs.org/en/download https://nodejs.org/en/download I never used nvm. If someone doesn't get this, it is a skill issue.
- mahmoudimus 1y ago
  I have largely avoided the entire typescript / JavaScript ecosystem specifically because I don't want to deal with node or its ecosystem. It's just so confusing with yarn, npm, npx, then the build systems gulp, grunt, webpack, etc etc - felt very overwhelming. Yes, if I spent more time learning these things, it would become simple but that seemed like a massive waste of time.
rileytg 1y ago
node install can be a real pain sometimes. node ecosystem has had a number of security related issues over the years. supply chain attacks are one of my main fears.
- mahmoudimus 1y ago
  I think most package systems are going to start, if not already, facing real supply chain attacks. The node ecosystem, from an attacker's lens, had quite a heavy leaning ratio of non-security conscious users which makes a better breeding ground for exploitation.
unshavedyak 1y ago
Is that not a valid justification?

Getting Node installed is a blocker for some of their customers, evidently. It doesn't surprise me. If it holds back one mid sized enterprise customer, the rewrite is worth it.

rcleveng 1y ago
It's a blocker for many windows enterprise customers. The suggested way is to use nvm to manage it (link: https://learn.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-windows https://learn.microsoft.com/en-us/windows/dev-environment/ja...). This needs admin permissions, which means a ticket with IT and a good chance it'll be rejected since it's scary as it'll open up the door to many admin level installs of software that IT has no control over. Installing node under WSL is a better approach anyway, but that'll make it harder for enterprise customers still.
- pjmlp 1y ago
  It can literally be a zip that one unpacks somewhere and sets the PATH. https://nodejs.org/en/download https://nodejs.org/en/download I never used nvm. If someone doesn't get this, it is a skill issue.
mahmoudimus 1y ago
I have largely avoided the entire typescript / JavaScript ecosystem specifically because I don't want to deal with node or its ecosystem. It's just so confusing with yarn, npm, npx, then the build systems gulp, grunt, webpack, etc etc - felt very overwhelming. Yes, if I spent more time learning these things, it would become simple but that seemed like a massive waste of time.

rileytg 1y ago

node install can be a real pain sometimes. node ecosystem has had a number of security related issues over the years. supply chain attacks are one of my main fears.

mahmoudimus 1y ago
I think most package systems are going to start, if not already, facing real supply chain attacks. The node ecosystem, from an attacker's lens, had quite a heavy leaning ratio of non-security conscious users which makes a better breeding ground for exploitation.

unshavedyak 1y ago

Is that not a valid justification?