3 ms·

I'm looking forward to trying this out. Having written Ember, Angular, and React apps now, I feel like they are all getting closer, but a lot of rough edges st

I'm looking forward to trying this out. Having written Ember, Angular, and React apps now, I feel like they are all getting closer, but a lot of rough edges still exist. Ember: interesting framework, but all too often, you would hear a team mate say "wait, why is that working, it shouldn't be?" Mixed with equal parts "logically, that SHOULD work, what am I missing?" React: I love the component focus, and redux is pretty slick. However, the insistence on using JavaScript in lieu of helpful abstractions that clean up the code for easier maintainability, is frustrating. The whole point of JSX is syntactical sugar, but the team went with half measures. You also end up with a lot more plumbing code than the other two. Sure, I can reuse some of these components, but in truth, most of your components will be single use. Angular 1: by far the easiest and most intuitive. Enough magic to make setup and a basic app easy, but not so much magic that you can't figure out why something is working. However, the more complex an app, the less Angular 1 serves. And you really need to use directives as a component, and follow a more react pattern, or you're going to have a bad time. Also, the dependency injection is a nice thought for simple directives, but when you're done, you'll very likely have so many dependencies being injected that unit testing becomes burdensome. And if it's burdensome, it won't be done as much as needed. All that being said, if your app is primarily collecting data through forms, you can't beat angular. If it's highly dynamic, and you want a more native feel to your app, react is the clear winner. Ember is a neat, but I won't be using it again. Angular 2 doesn't fix all of my complaints, but it's getting closer.

zxcvcxz 10y ago
>the insistence on using JavaScript in lieu of helpful abstractions I appreciate this. The javascript world already has too many abstractions. >Angular 1: by far the easiest and most intuitive. How on earth do you find Angular more intuitive than React? Angular is a behemoth compared to React. This is like saying Rust is easier and more intuitive than Go. Angular 2 forced me to switch to React because it made me weary of Angular 3 and the new abstractions that that will bring. It seems also that a lot more big sites are choosing react over angular and I see a lot more job postings for react devs.
spriggan3 10y ago
> However, the more complex an app, the less Angular 1 serves. That's not really true. The problem is that all three frameworks are supposed* to require the same discipline when it comes to managing state, but only React forces that discipline onto the developer. I'm not saying React is better, but learning from React is important to be able to write maintainable applications in any framework. You don't want to have 30 services, each services managing there own little state in AngularJS for instance. Unfortunately that's usually what happens when an app grows with time. Angular2 does seem to get rid of the dirty checking, allowing better performances. It also has a good router. But does it really bring something new in terms of view layer and state management, considering the cost ? I like Angular1, it's one js file you drop in an HTML page, no need for nodejs, NPM, a third party language and what not. And it's mature. It's absolutely unfortunate that Angular2 basically forces developers to use Typescript. That's a huge mistake IMHO. edited
- notsotrue 10y ago
  I'm curious, what would you consider a complex app?

zxcvcxz 10y ago

>the insistence on using JavaScript in lieu of helpful abstractions I appreciate this. The javascript world already has too many abstractions. >Angular 1: by far the easiest and most intuitive. How on earth do you find Angular more intuitive than React? Angular is a behemoth compared to React. This is like saying Rust is easier and more intuitive than Go. Angular 2 forced me to switch to React because it made me weary of Angular 3 and the new abstractions that that will bring. It seems also that a lot more big sites are choosing react over angular and I see a lot more job postings for react devs.

spriggan3 10y ago

> However, the more complex an app, the less Angular 1 serves. That's not really true. The problem is that all three frameworks are supposed* to require the same discipline when it comes to managing state, but only React forces that discipline onto the developer. I'm not saying React is better, but learning from React is important to be able to write maintainable applications in any framework. You don't want to have 30 services, each services managing there own little state in AngularJS for instance. Unfortunately that's usually what happens when an app grows with time. Angular2 does seem to get rid of the dirty checking, allowing better performances. It also has a good router. But does it really bring something new in terms of view layer and state management, considering the cost ? I like Angular1, it's one js file you drop in an HTML page, no need for nodejs, NPM, a third party language and what not. And it's mature. It's absolutely unfortunate that Angular2 basically forces developers to use Typescript. That's a huge mistake IMHO. edited

notsotrue 10y ago
I'm curious, what would you consider a complex app?