4 ms·

Basically avoiding the mistake Angular made (moving from 1.x to 2+)

• jzig 3y ago
  And yet Angular is now the less complicated framework and easier to work with (IMO).
  • jmondi 3y ago
    If Angular wasnt based on RXJS, I would agree with you that the defined structure of Angular makes it nice and predictable. RXJS pipe hell is a hell I wouldnt want to send my worst enemies to.
    • mickael-kerjean 3y ago
      Well I absolutly love rxjs, in my opinion it's one of the very few library in the JS ecosystem that are actually worth their weight
    • ttfkam 3y ago
      While RXJS definitely still has a role in the Angular ecosystem, a lot of what RXJS used to do is being handled by signals in the newest versions.
  • atomicfiredoll 3y ago
    I admire parts of Angular's vision and think there are patterns where it shines, but it's never quite felt like they actually hit 2.0 to me. I haven't worked with it in a few versions, but I think it's just a different set of complexities. There's always some big or missing thing right around the corner... reworking Material components for years, reworking internationalization, improvements to reactive forms, zoneless Angular, single file components, etc. And, for as many bugs as they fight down, it's always felt like there were several obvious frustrations waiting to be fixed. It's all just left me with an impression that the team bit off more than they could chew in creating such a holistic solution and can't quite get to something solid, hence the need to shed things like Protractor. Hopefully the cumulative effort to improve gets them somewhere and helps get Angular into a more complete and compelling place for folks.