8 votes

Topic deleted by author

2 comments

  1. [2]
    Comment deleted by author
    Link
    1. Akir
      Link Parent
      That's a bit sad, personally speaking. I don't think that having a programming language fall to the whims of the commons is a good thing. Programmers always want to be using whatever's new and...

      Losing ES4 allowed the language's users to vote with their feet about which type system they want.

      That's a bit sad, personally speaking. I don't think that having a programming language fall to the whims of the commons is a good thing. Programmers always want to be using whatever's new and shiny. And when it comes to the history of Javascript, nobody was willing to wait. Far before they were standardized, there were libraries to add new features and APIs to the language. That's when frontend codebases started to really bloat. The author says it best:

      Perhaps if ES4 landed, fewer people would need complex build tools like Babel, Webpack and Typescript.

      And while I don't think that accommodating programmers is a bad thing by any means, it seems that JS has a lot of 'cruft' in the language design, with a number of features being essentially forgotten about because they were implemented poorly or are simply unpopular.


      On a different line of thought, I'm sure you have probably heard a lot of outsiders saying that they wish that we could start all over again with web applications without the weight of HTML/CSS/JS. If XHTML and ES4 happened, I think they would be the happy web developers of today.

      Natively being able to use types and a better Class-based inheritance system are two features that would make JS more appealing to an "old school" type programmer like myself. As it is, I'm waiting for the tooling for WASM to get good enough that I can run Python, Java, Rust, or whatever language of my choice for frontend development.

      2 votes
  2. nothis
    Link
    Wait, javascript was about the get int?

    Wait, javascript was about the get int?