• thanks_shakey_snake@lemmy.ca
    link
    fedilink
    arrow-up
    2
    ·
    10 months ago

    Well… The circumstances were that he was asked to whip up a little scripting language, that felt a little like Java and a little like Scheme, which could be used to add simple manipulations and interactions to web pages. Specifically to web pages. Not webservers, mobile apps, databases, banking systems, physics simulations, robotics… Only web pages. And nobody had even conceived yet of something like Google Sheets-- It was simple HTML forms and DOM manipulation.

    IMO in that context, it makes alot of sense. I think it was probably still the wrong decision-- definitely with the benefit of hindsight, and quite possibly even at the time, even in that narrow context. Way more trouble than it’s worth.

    But it’s beneficial to know that there was a principled (if misguided) reason behind it, that ties into the nature and history of the language-- It’s not simply “dude was in a hurry and not thinking.” Both are kinda true, but the former perspective helps us understand something useful, whereas the latter doesn’t get us anywhere interesting.

    • cmdrkeen@programming.devOP
      link
      fedilink
      arrow-up
      3
      ·
      10 months ago

      TBF he probably had know way of knowing that the language he was creating would one day end up being as popular as it is now.

      I guess the moral of the story is that you can never really predict what long term consequences your decisions might have down the road.