Recent searches
Search options
Having worked with #Angular in-depth for 2 years now, I can articulate what I don’t like about the #framework.
1. #RxJS is a terrible primitive to build most #CRUD software upon. #Promises are better for most things, and event listeners are fine.
2. Its #DI system encourages long-lived, easily-accessible Singletons that are serious “foot guns.”
3. Data management is painful. Resolvers are a worse DX than either #EmberJS’s Ember Data or #React’s TanStack Query.
@kerrick That's a great point!
I'm currently learning Angular. What advice do you have for me?
@real_pouria For 2, I’ll quote @russolsen from “Design Patterns in Ruby”:
> There is only one solution to this problem: _Don't do that_. Properly applied, singletons are not global variables. Rather, they are meant to model things that occur exactly once. Yes, because it occurs only once, you can use a singleton as a unique communications conduit between bits of your program. But _don't do that_.