Comments by "" (@diadetediotedio6918) on "So Many Programming Languages" video.

  1. Also, I think the "one language for a specific purpose" is both a good take and also in some level bullshit (relating to the title of your video as well). It is good because specialization tends to make better tools fit to their specific purposes, it is good for organization and also allows for more conciseness in what you are trying to express with code. And it is also bullshit because learning more languages do not imply in a loss, it expands your domain over all the languages you've already learned by generalizing the knowledge, having competition is also extremely good and factually one of the most common reasons I heard from people is that they "don't want needing to learn so much" (which is lazyness³; you also don't need to learn everything, because competition exists and thus you can work with whatever you want most of the time), and also because the more specialized you are the more you lose context about the world of other things, and the more you need that 'recurrence' and fragmentation inside one workload. You can see this with people using JSON, but still inventing more and more protocols around it, or with alternative solutions to protobuf that tries to cover logic or some other bs, or even with Lua where there are like dozens of versions of it trying to generalize it for more cases or for performance-based tasks (like lua-jit or Luau [the roblox version of Lua with types and other features]). I'm also not saying this is bad, but specialization can be a good or a bad thing and it is generally harder to know the exact domain of the problems you are trying to solve (the problems you are tring to find in the real world to specialize in) than to make a general-purpose language that can be used in certain contexts more than others. I think we should have even MORE languages, more and more and more of them, because no one will fullfil all the needs of all programmers ever. This is one of the reasons of why I think AI's can hurt the developer environment much more than aid, they are good at specific things they have tons of material to train on, and their general tendency is not to innovate but to homogeinize everything (the wet dreams of the "we already have many languages" person).
    5
  2.  @viniciusmachadorodrigues1724  It is not a "nope" bro, you can use JS as a thin wrapper for other languages, and in the future proper DOM support can come. It can also be used to replace JS in most of the tasks that require speed.
    4
  3.  @brawlgammer4424  WASM don't even have 10 years bro, shill out. Technollogies are extremely slow to develop, and even more to be adopted.
    4
  4. WASM can be used to replace the need of docker in future, and also to replace JS in browsers, so it kinda is a W.
    3
  5. And the thing 4:46 is that the performance difference should not be extreme.
    1