Why Learning Angular 2 Was Excruciating
Liz Bennett

I think this type of article is really important.

I apologize for the defensive and critical responses you’ve gotten.

I don’t think in any way that this experience was your fault for trying alpha software, or your fault for not studying javascript for 10 years before using a framework.

I believe that you are right to feel that having alpha dependencies in a “final” product is wrong. You are absolutely correct that APIs should not break during RC.

Lastly, I think it would be a shame to dismiss this as an Angular problem and move on. JS is a wonderfully simple language with an incredibly complex ecosystem. The fact that every app is abstracted to death by frameworks, then transpiled, then run through ultra complex dev & test runners means production code rarely resembles anything someone actually wrote. Your stack traces and errors are common pitfalls that I’ve seen in virtually every existing framework. IMO any framework choice you could make would leave you in this same situation.

Thanks for taking the time to document this experience — it’s a good reminder to the community that we still have a long way to go.

One clap, two clap, three clap, forty?

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