4 ms·

Why can't the "back end community" agree on a single server side language and database and compiler? Gee so much churn!

• monkey_monkey 4y ago
  We both know those aren't even close to the same thing. All this grunt->gulp->webpack->vite->'the inevitable replacement for vite' are really achieving is finding slightly different ways of doing the same thing.
  • mikewhy 4y ago
    "all this monoliths->microservices are really achieving is finding slightly different ways of doing the same thing" "all this python->go are really achieving is finding slightly different ways of doing the same thing" "all this relational db->document stores are really achieving is finding slightly different ways of doing the same thing"
    • monkey_monkey 4y ago
      Once again, we both know those aren't even close to being the same. Your attempts at snidey mimicry just expose the poverty of the point you think you're making.
      • mikewhy 4y ago
        Awwww but you're so close to getting the point. Hopefully one day.
      • strokirk 4y ago
        As a backend developer, I’d say that it is a very apt comparison to your point. The backend and infrastructure space also has a lot of new projects solving old problems being released.
  • bilalq 4y ago
    All this make->ant->maven->gradle->'the inevitable replacement for gradle' are really achieving is finding slightly different ways of doing the same thing.
    • monkey_monkey 4y ago
      I'm glad you agree with me.
      • woojoo666 4y ago
        As another commenter pointed out [1], backend "reinventions" don't seem to receive the same criticisms, so in general there really does seem to be a double standard [1]: https://news.ycombinator.com/item?id=31970112 https://news.ycombinator.com/item?id=31970112
• deleted 4y ago
  [deleted]