• folkrav
    link
    fedilink
    8
    edit-2
    2 days ago

    The stuff like Flash, Java applets and Silverlight it eventually replaced were arguably even worse. There’s a legitimate need to run client-side code at times, IMHO the mistake was making it so permissive by default. Blaming the language for the bad browser security model is kind of throwing away the baby with the bathwater.

    • trevor
      link
      fedilink
      English
      41 day ago

      WASM is a better way to run code client-side, and has the benefit of not being a terribly slow, untyped mess 😌

      • folkrav
        link
        fedilink
        220 hours ago

        It desperately needs interface types if we ever hope to make it a serious contender for general purpose web development. The IO overhead of having to interface with JS to use any web API is itself pretty slow, and is limiting a lot of usecases.

      • folkrav
        link
        fedilink
        21 day ago

        Considering the community we are on, I assumed the criticism was more about the privacy problems surrounding the engine and browser security model than the quality of the language itself. If that was the intent, I mean… Yeah, its weak typing is a fucking mess.

        • @[email protected]
          link
          fedilink
          2
          edit-2
          1 day ago

          That’s fair. I just assume most people who reflexively insult JS are like that usually because they’ve written something in it, rather than having dealt with the many vulnerabilities and annoyances browsers have made possible with it