Comments by "" (@diadetediotedio6918) on "Every programming language explained in 15 minutes | Prime Reacts" video.

  1. hahahaahah no, because this movement started back to the beginnings of the popularization of internet, it just evolved this way because we could. But coder from a time will always complain about the code in their times, that's why we have so much new languages and technologies and algorithms that solves problems, the ammount of RAM is just a factor that losened our grips on a specific aspect of software development <in some cases>. Browsers are amazing pieces of software that can make the users safer than it was possible back then while still being able to exhibit an amazing ammount of content almost instantly to the average user.
    1
  2. 1. Because it makes things more obvious and well delimited 2. Because it does not matter, it is easily recognizable as 'function' and writting 'function' every single time is no better than writting 'fn' or 'fun' (and it is worthless to make it a requirement even with an IDE). So, it is a 'stylistic' choice in most languages.
    1
  3.  @roberthoople  What do you think it is obvious here? You need some way of differentiating functions from closures (so not every single () {} or () => or {} would be treated as a function) and you generally want to be around of what is traditionally being used when doing stuff, so using a keyword for it is okay, it also can make the parsing of the language easier.
    1
  4. 16:03 Nah, we have articles of like 50 years ago saying that software was bad written and messy, this is just a bias towards the past.
    1
  5. For the one who asked for sources (I cannot see your comment anymore, but notifications show it so...) OLD PROGRAMS, NEW PROBLEMS (1981) AN OPEN LETTER TO HOBBYISTS (1976) --- this is more for fun
    1
  6. 41:00 Are you saying like, pushing a 0.x.x language into one of the most used kernels in the world? Surely it looks like an amazing idea But seriously, I've used zig and it is just annoying for the most part, the ergonomics are not there yet and the lack of proper responsive code editing support makes it feel more of a beta than it should feel. The types as values is also an interesting thing, but it just feels awkward to handle types this way, and it makes complex type inference and generics programming a log harder to do (if not impossible in some cases).
    1