> It was written in 3 weeks Actually 10 days, with 22 years of development, but that has nothing to do with how it fundamentally works. > The rest of it is li

> It was written in 3 weeks Actually 10 days, with 22 years of development, but that has nothing to do with how it fundamentally works. > The rest of it is like PHP Are you joking? Ok so, JavaScript is a prototype based language PHP is (now) an OOP language. They are not remotely the same with the exception of dynamic types and even that is nothing like PHP due to the nature of JS engines like V8. But because if the prototype system it can emulate classical OOP. JavaScript is also a higher-order language which mean it is a psuedo-functional programming language. PHP and JS could not be further apart. > The classic Perl defense I'd say: ~you don’t understand the beauty of it. It's not about beauty, I'm saying that most people who think the language is making mistakes or doing something wrong just don't understand how it works. They blame it for their lack of knowledge. > Well, every thing you can do in JS you can also do in TS. But that's not why people use TypeScript, they use it to do TypeScript styled things. > what you said above: ~ intuitive enough to create your own restrictions That's the problem, TypeScript comes with a bunch of constraints, that's its purpose. Yes you can choose to use them or not. You could also buy a new phone and throw it off a cliff, but that's not generally why people buy phones. > Also: By this logic we should be programming in assembly. Assembly serves a purpose well, so does JavaScript. I'm just saying rather than trash things why not learn them first properly.