3 ms·
Then why build another incredibly slow dynamically typed monstrosity that breeds bugs and bad quality at industrial scale? Stop building JavaScript infrastructu
by henning 3y ago
Then why build another incredibly slow dynamically typed monstrosity that breeds bugs and bad quality at industrial scale? Stop building JavaScript infrastructure.
- nforgerit 3y agoC'mon it wasn't that bad. npm was a fun experiment on what could possibly go wrong with putting leftpad into a single package. For me it's still by far the best runtime to do anything event-alike/http/json/web. It's quick to develop small things and quick to deploy (if you omit the whole transpilation shenanigans which of course help if you have dozens of engineers working together).
- rektide 3y agoHe took one of the fastest & most successful & invested in existing JS engines & bolted on a pretty decent standard library. Great winning move, where a ton of the hard part of language optimization & growth is other people's problems, & Ryan could focus on making a great developer experience, which he and izs (npm author) did.
- richardjam73 3y agoThey probably realised after that was done.