• Balder@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 days ago

    I mean, this post makes no valid argument against JavaScript, there’s no benchmarks or anything aside from an opinion.

    I don’t personally like webdev and don’t like to code in JavaScript, but there are good and bad web applications out there, just like any software.

    A single page can send out hundreds or even thousands of API requests just to load, eating up CPU and RAM.

    The author seems to know the real problem, so I don’t know why they’re blaming it on JavaScript.

    • Kairos@lemmy.today
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      8 days ago

      Because only JS is able to do that in a web browser. Everything else is just a dependency tree.

      • watty@lemm.ee
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        8 days ago

        That’s not necessarily special to JS. It’s special to client-side code. A mobile app writing in swift could do this. A cli tool written in any language could do this.

        This isn’t an argument against JS, it’s an argument against misuse of client resources.

          • watty@lemm.ee
            link
            fedilink
            English
            arrow-up
            1
            ·
            6 days ago

            Seems like you read the first two sentences of my post and stopped there, so you completely missed the point.

            It’s not JS that is the problem. It’s an issue of client resource use. That would be true no matter what language is being used.

            • Kairos@lemmy.today
              link
              fedilink
              English
              arrow-up
              0
              arrow-down
              1
              ·
              6 days ago

              Not necessarily. Programmers are heavily influenced by the language they use. There’s a reason there’s so many JS frameworks.