Popcorn

  • jaykrown@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    30
    arrow-down
    1
    ·
    14 days ago

    JavaScript was originally built in just ten days to handle lightweight tasks within a web browser, like validating forms or animating buttons, not to power the heavy logic of server-side infrastructure. Using Node.js forces this fragile scripting language to do work it wasn’t designed for, lacking the strict stability, type safety, and multi-threading capabilities of robust languages actually engineered for servers, like Java or Go. By pushing JavaScript onto the backend, the industry prioritized the convenience of not learning a second language over engineering rigor, resulting in bloated applications, security vulnerabilities from excessive dependencies, and significant performance ceilings that proper backend languages simply do not have.

    • Blue_Morpho@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      1
      ·
      14 days ago

      I believe the problem is developers, not the language. The problem is developers importing node.js and other giant frameworks for a simple function. That’s not a language problem. Bad coders are going to cause the same problems in any language.

      The same problem exists in C when a simple Windows app requires a separate install of the vcruntine140.dll. Java also has enormous libraries that programmers abuse because they are cutting and pasting codestack they don’t understand.

      • jaykrown@lemmy.worldOP
        link
        fedilink
        English
        arrow-up
        4
        ·
        14 days ago

        I agree that’s the main problem, but if it didn’t exist or was never attempted to be used that way, it wouldn’t be a problem to begin with.