• @CanadaPlus
    link
    English
    43 months ago

    I guess the internet just grew that fast. The first arrival took all and locked everybody in.

    Now, we have just two browsers that are widely used, so maybe we do have an opportunity to go back and fix it. Go sounds like it’s a pretty popular choice for statically typed, imperative high-level language.

    • DarkenLM
      link
      fedilink
      163 months ago

      Honestly, given the context of a browser, Javascript’s “Everything is better than crashing” philosophy does not seem too out-of-place. Yes, the website might break, but at least it would be theoretically usable still.

      Yes, a statically typed language would help, but I’d rather not have one that is “these two types are slightly different, fuck you, have a segfault”, but rather one that is slightly more flexible.

      • @CanadaPlus
        link
        English
        4
        edit-2
        3 months ago

        Actually, that’s a good point, in scripting fatal type errors can happen at runtime. I guess Python is the right choice then, given it’s maturity and popularity, and then you can code the complex stuff in whatever you want via WASM like other people mentioned.

        • @stifle867@programming.dev
          link
          fedilink
          23 months ago

          It’s interesting to think how this would have changed some of the things we take for granted today. For example, for production we “minify” our CSS and JS, but Python has enforced whitespace. Would we still have come up with minifying and those on restricted data just take the hit?