7 ms·

How do you fix node without breaking it? I don't think this is possible.

• Swizec 3y ago
  The benefit has to be big enough to warrant switching. Incremental improvements aren’t gonna cut it Breaking is fine if it’s worth the effort. 10x better is the usual rule of thumb for this sort of thing.
  • bryanrasmussen 3y ago
    huh we recently had to update our React 18 usage and it's had a few programmers spending weeks on it. So why not move to Deno.
    • rglover 3y ago
      That's a React problem, not a Node problem.
      • bryanrasmussen 3y ago
        ugh. The parent poster's point was that it was not reasonable to consider moving off any platform that did not offer significant improvements. Now I realize that I did not painstakingly spell out the point I was making but it was not that React === Node, rather since upgrading part of your stack to a new version can have similar difficulties to moving to another language maybe moving to a different language isn't the big problem the parent poster implied. There are multiple times during long running sites when you may need to do significant rewrites of things to move between vendors, to upgrade versions of libraries, frameworks or languages or similar things for incremental benefits.
        • Swizec 3y ago
          The risk in upgrading React is lower than the risk in changing your server runtime. React still to this day guarantees a lot of backwards compatibility and the upgrade path has been thoroughly battle tested inside Facebook. Moving to Deno is full of unknown unknowns. It’s very early.
  • handsclean 3y ago
    1.25 ^ 10 ≈ 10
  • croes 3y ago
    That requires people realizing the benefits. But it seems people don't learn from left-pad or node-ipc.