Why Learning Angular 2 Was Excruciating
Liz Bennett

This is a great testimony. Angular (and TypeScript) wrap up JavaScript, HTML, and the DOM in elegant, but somewhat fictitious abstractions that don’t teach someone who is new to front end development what is really going on.

In Java, the priorities in terms of how you deal with the programming language itself are very different. In a language like Java or C#, the first and most important thing to know is that if a package is referenced in the correct scope and it’s physically there, the package loads so long as it was compiled with a compatible version of your language runtime.

In front end development, this is something which is entirely abstract. Some stupid framework has created some stupid metaphor for something akin to a “package” and you can “load” it if you have some stupid “namepace”. These are all valid principles of programming, but none of it really exists in JavaScript, which means in a perfect world I can make JavaScript quack like such a duck, but if something goes wrong, the duck reverts to the blob of shapeless gunk that JavaScript really is.

From a practical point of view, does it makes sense to put thousands of hours into making JavaScript pretend to be something else? Even ES2015 is to a certain extent “pretend” because its runtime is a work of fiction.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.