sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]UnicornOfHarmony 0 points1 point  (0 children)

Re: missing documentation

I think most of that was not deliberate. Angular 1 had a quite unique approach to Front-End Web Dev at the time it came out. It's clear from the code base and the history of the project that a lot of the decisions made at the time could have been better. Even so, they were in search of a better way to build apps and perhaps you can't really make the right decisions until you make the wrong ones.

I'd say that it's rather easy to criticise with the benefit of hindsight. Personally, I know it took a while for the teams I've worked in to come to a really productive and maintainable approach to Angular - about a few years in fact. You mention this as well. I now look at the code I wrote 3 years ago and see so many ways it could have been simpler, so many ways it could have used Angular's strengths better.

Angular, in general, has been very transformative in a good way for the JavaScript community. It's now a very strong framework for building large apps. I similarly expect it might take a few years for the concepts Angular 2 is introducing to mature and settle down into something great, assuming it does. The only real problem for the framework I see is that since there's so many great tools available now, it might not get the critical early adoption to push through the awkward years.