• TCB13@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    11 个月前

    What are we talking about? If we can’t write a pure JS application that runs on a browser without performance issues than the problem is most likely the code and not the fact that it isn’t compiled. It’s not like an extra 500KB of data will slow down anything on a world where people have 12GB of RAM on phones and gigabit speeds on almost everything.

    I believe the price we pay by going into the compile/build is much larger than those few KB. Today everything works, tomorrow half of your compilation steps are broken because xyz package is no longe available, dead, replaced… JS was meant to be interpreted not compiled.

    Look I get that this compile/build hype in JS resulted from the fact that people wanted to workaround missing features on the language, I also get that it may make development faster but now in 2024 we should really reconsider this and simplify things. JS and CSS evolved a LOT.

    • Lmaydev
      link
      fedilink
      English
      arrow-up
      2
      ·
      11 个月前

      It’s more to do with larger teams. Frameworks should make it easier for multiple people to work on a codebase. As well as allowing much larger apps with less complexity.

      • TCB13@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        11 个月前

        Yes but why do they have to be compiled? For what’s worth jQuery is a framework and so is Vue without compiling.

        • Lmaydev
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          1
          ·
          edit-2
          11 个月前

          Usually because they have their own way of defining things that isn’t standard JS.

          For instance Vue can be compiled if you want to make full SPAs using it.