Farewell Node.js — Code adventures — Medium

/farewell-node-js-4ba9e7f3e52b

  • @0gust1
    0gust1 CC BY-NC
    4
    @fil
    @neurolit
    @liotier
    4

    Un important contributeur de #nodeJS, TJ Holowaychuk, lui dit « au revoir ».

    Farewell Node.js
    Leaving node.js land

    I’ve been fighting with Node.js long enough in production now that I don’t enjoy working with it anymore unfortunately, so at least for now this my formal farewell! And more importantly I need maintainers

    ▻https://medium.com/code-adventures/farewell-node-js-4ba9e7f3e52b

    Ce qui est rigolo, c’est que c’est un personnage quasi mythique : personne ne l’a vu, son style de code change souvent, etc.

    #javascript #go

    0gust1 CC BY-NC
    • @fil
      Fil

      don’t get stuck in your own bubble! See what else is out there, you just might enjoy programming again.

      Fil
    • @0gust1
      0gust1 CC BY-NC

      Une « réponse » de Dustin Diaz.

      Why I’m staying with Node

      ▻https://medium.com/@ded/why-im-staying-with-node-e6fd3be62e34

      But I bet on JavaScript a long time ago, and alas, like English — it’s everywhere.

      The problems that T.J. points out with Node.js are very similar to the problems we have in English, metaphorically speaking of course. Error handling is natively error prone, callbacks are harder than regular synchronous transactions, errors, errors, errors. We make grammar mistakes all the time in English, but for the most part, we all understand each other, and have known solutions to fix those mistakes.

      As far as measuring concurrency and speed between Go and Node, it would the equivalent of comparing whether a for loop performs better going backwards or forward. These kind of microbenchmarks don’t appeal to me. When choosing a programming language or framework or library, always consider the ROI for your product and how effective you’ll be between your users, your team, and yourself.

      0gust1 CC BY-NC
    Écrire un commentaire