Echo JS 0.11.0

<~>
tenpkj 2909 days ago. link 4 points ▲ ▼
<speculation> Angular 1, while having its fair share of oddities and complexities and frustrations, is able to provide a measure of fun in how you work with the web. Without much ceremony and overhead, you can make something cool in relatively short time.

The reaction to Angular 2 within the development community has been more mixed than the reaction to Angular 1. Maybe this is because Angular 2 takes a lot of the fun out of web development. The concept count is way higher, the template syntax looks nasty compared to Angular 1, the project now seems to cater to architecture astronauts, etc.

Combine this with how parts of the tech ed community have a vested interest in making it seem you need to use Angular 2 (maybe they have a fee-based course or are promoting one thing or another). Yet what is the sweet spot for Angular 2? Does everything you do on the web now have to be in Angular 2? Do even most line-of-business projects have to be in Angular 2? You won't find as much discussion along these lines.

So maybe when an inflammatory headline like "Angular 2 is terrible" comes along, there are many who may have a lot of sympathy with that viewpoint, regardless of the merits of the content below the headline. 
</speculation>.

Replies

sylvainpv 2909 days ago. link 4 points ▲ ▼
Exactly. I found the article content to be technically low and sometimes incorrect, yet I can't help but upvoting this because I totally share the feeling of dispair and distress of the author. 

I work on a large Angular 2 project for a year now and the development has been chaotic compared to my previous experiences with Angular 1. At the time, we decided to go with ES6 instead of TypeScript as the Angular team made this promise that we could have the choice of the language. The truth is, there is no documentation and tooling for non-Typescript users and migrating from ES6 to TypeScript on big projects is much more complicated than expected.

Currently we have major issues such as the bundle size (1.7 megabyte only for angular and related dependencies) and render performance in our views (fixed by changing ChangeDetectionStrategy and manually updating the view, which makes angular zones mechanism almost pointless). Debugging is also terrible since angular and zone call stacks are hiding all the valuable information in the exceptions.

Today I bitterly regret this choice and would not recommend Angular 2 to anyone. I worked with dozens of JS frameworks in the past but none of them has leaved me to such a state of mind of frustration and discouragement. I know it sounds like whining and my testimony may not be very constructive but it needed to be told. Angular 2 is terrible.
tracker1 2906 days ago. link 2 points ▲ ▼
One of my experiences was pretty similar... I've been happy with React (w/ redux/thunks/fetch), and would recommend it whole heartedly over ng2... as a migration, ng1 to ng2 is even more painful than a planned rewrite path.

Most of my biggest complaints on ng2 have been addressed (although after rc1), and even then, it just feels weird in a day when we have a lot of tooling around npm, the stuff baked into ng2 just feels like too much, and too difficult to really use.