81–90 of 102 posts
Earlier quoted context omitted.
ExtJS went through some rough upgrade cycles as well. From what I remember, the 2->3 upgrade path covered a small subset of codebases.
Ember OTH has the smoothest upgrade path known to man.
Earlier quoted context omitted.
Remember separation of concerns ? Fuck that, let's just mash code and markup together.
What concerns do you think you're separating exactly, when you're dealing with presentation-tier markup and code that combine intimately to a single component?
I had similar worries when I first saw JSX. Having used it quite extensively, though, it does feel like it's a sensible idea now, from a development perspective at least. That said, it does increasingly feel like the days where certain people could just write HTML and CSS, and other people could handle the trickier JavaScript, are long gone (especially with things like Radium for React).
Commets here made me think about whether it's forward-looking using angular 1.0 for next projects: i guess i'll go with React with my short-coming project then... I don't know what to do
In my limited experience React is way easier to comprehend than Angular.
Took less than a day to understand angular from nothing -- taking more than a day just to evaluate flux implementations with react.
I know that hating angular is popular these days, but i'm still using it, and it serves me well. Looking forward to Angular 2!
Every time I use Angular it feels like it's doing things the right way and it's becoming the Rails or Django of the JavaScript world. Wish I had fought to use AngularJs directives and $resource instead of messing about with ReactJS and jQuery ajax calls. With this migration plan it seems silly not to keep hacking with AngularJS 1.x
Earlier quoted context omitted.
Remember separation of concerns ? Fuck that, let's just mash code and markup together.
The fun part is that Angular (1, anyway) has pretend-separation. Sure, there's truth in DOM, but not really. Littering your custom directives all over the place may feel like progressive enhancement but if you're using an app framework like Angular your JS is likely already complex enough that you can't meaningfully consider it a mere "enhancement" -- we're talking core functionality, not fairy dust. People react (he…
I see 2-way data-binding is mentioned here and will still be supported (good). Curious why has 2-way now become 'uncool' recently, e.g. React? 2-way is what got me excited about client side JS due to the code reduction in an average app. Is just that Angular 1's implementation was non-performant? (lots of other frameworks use it as well, e.g. Knockout, RactiveJS, etc).
Two way data binding is awesome and neat and shiny and chrome. It's also pretty slow; a lot of pragmatic angular work involves keeping the number of watchers firing during digest cycles minimized. If you have a lot of data that's all two-way-bound by default, but aren't making any use of the bindings, that's a lot of wasted cycles. I mean, my app has a lot of data in it, stuff like {{username}} which rarely ever chan…
Every time I use Angular it feels like it's doing things the right way and it's becoming the Rails or Django of the JavaScript world. Wish I had fought to use AngularJs directives and $resource instead of messing about with ReactJS and jQuery ajax calls. With this migration plan it seems silly not to keep hacking with AngularJS 1.x
Yep, even though directive implementation is verbose in 1.x, once you get really comfortable building them it's a pleasure to use them.
Earlier quoted context omitted.
Ember OTH has the smoothest upgrade path known to man.
Not that smooth if you saw the comments on HN last week - teams lost months of productivity keeping up with the rewrites in Ember, even with no immediate breaking changes.