TelepathyConspiracy wrote:Not true, you're talking as if you write the whole thing all at once and then start debugging instead of what is much more sensible such as debugging in smaller steps, usually function by function as you go
Well, test-driven development is probably a good thing, but it does not at all guarantee that your programs are bug-free. I was doing test-driven development when writing the tokenizer and the parser of my AEC-to-WebAssembly compiler in C++ (
those tests are run before compilation), and nevertheless there were some bugs left in them. And for at least
one of those bugs, using a more sane language than C++ would have helped me avoid that bugs. It would have been even worse if I used JavaScript rather than C++. Who knows how many bugs are left in my
PicoBlaze Simulator in JavaScript (where I wasn't even doing test-driven development).
TelepathyConspiracy wrote:Reassigning console.log to something that renders on the app, such as my Um2MAk, makes the first go around easier if that's what you're saying...
No, that's not what I am saying at all. My point is that, for many bugs in your app, you are not even AWARE that they exist. Your testing simply did not test that PATH (if-else, switch-case...) in your program. A sane language helps you discover those bugs. Plus, a sane language helps you discover some bugs before you even run your program.
TelepathyConspiracy wrote:It's the best for the world we actually live in (all environments, historical success, V8 heavy lifting, GAS heavy lifting, etc) and the argument was that any marginal improvement isn't worth it in terms of making things as simple as possible for beginners...
Sorry, I don't understand what you are trying to say here. I don't even know what those terms (V8, GAS...) mean. I mean, "V8" is a JIT-compiler for JavaScript used in Chrome, and "GAS" is GNU Assembler, but I guess that you mean something different by those terms, as your sentence makes no sense.
TelepathyConspiracy wrote:These newer versions of JavaScript, they're adding features that are redundant and serve nothing but creating different conventions that make things harder to read...
There you go, criticizing the features of newer versions of JavaScript and other languages without even trying to understand the problems they are trying to solve.
Makes me wonder if that's how we anarchists sound like to statists, as we often seem to be criticizing various government programs without having a good understanding of the problems those government programs are trying to solve. Of course, it's not the same thing, but now I understand the statists better.
TelepathyConspiracy wrote:The classes you're referring to are very new in JS, acknowledge this...
I was never claiming otherwise. My entire point is that those new JavaScript classes don't solve what's probably the biggest problem of JavaScript prototype inheritance, that are that the program simply keeps going if you mistype a property name.
TelepathyConspiracy wrote:"const" and "let" do not add anything whatsoever
Yes, they do. "Let" solves the problem of unintentionally-function-scoped variables, and "const" solves the problem of unintentionally modifying a variable that's not supposed to be modified. Once again, you are criticizing programming language features without even understanding the problem they were trying to solve. And the problem that "const" and "let" solve is even more obvious than the problems that JavaScript classes solve.
TelepathyConspiracy wrote:Btw w3schools is often the best at cutting through the bullshit, much better than Mozilla
It really isn't. There is a reason why new features such as "const" and "let" were added to JavaScript. Why do you think they would be added otherwise? Because people making the standards (primarily from Google and Mozilla) are stupid? Since the tutorials at w3schools do not use them, they are bad tutorials that teach bad practices. So you are not only using a bad language that is JavaScript, you are also following bad practices within it. And are criticizing others for using the new features of JavaScript without even understanding the problems those new features are supposed to solve.
TelepathyConspiracy wrote:What is actually missing from the concept that you believe classes in other languages provide?
I've explained it multiple times, yet you won't listen. It's the compile-time errors in case of mistyped property name. In sane languages, those are compile-time errors. In JavaScript, these are bugs that are often hard to trace.
TelepathyConspiracy wrote:everything is organized into the single page
I hope you are not actually putting your entire program in a single file. That makes collaboration almost impossible. Not to mention it's hard to read.