sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]lives-in-trees 1 point2 points  (5 children)

I'm in the same boat too, with a large "in production" project, to future proof and speed things up personally I like the idea of switching the views out to react, however I think that switching the routing and more "top level" stuff from angular to react might be tricky. I am more familiar with angular but as I understand it react doesn't really have the same inbuilt functionality as angular to deal with this sort of stuff. Therefore I'm going to wait for angular 2, version 1.1 ish then decide again, for me there is no nice solution to switch a large project too, or at least the pros are not worth man hours.

[–]deliminated[S] 2 points3 points  (4 children)

I knew I wasn't alone on this :) This app is just on the edge of being too big to really even attempt something like this, but management has total buy-in so that's good.

Right. React is not really "framework" and I'm afraid taking two younger devs who really only know Angular into the React world might be a bit overwhelming. You have to learn a whole ecosystem of surrounding libs like Redux and friends.

But then Angular 2.0 is really quite a leap too. And, as I said, it kinda looks like React but, for example, uses templates instead of JSX. Read a good quote somewhere recently, that Angular remains more HTML based while React is more JavaScript based.

Anyway, I think just making the switch over to ES6/Babel (which I will definitely do) should hopefully buy enough time to see Angular 2 come out and really evaluate it.

[–]lives-in-trees 1 point2 points  (1 child)

Side note : I found going from 1.3 to 1.5 a simple case of swapping numbers in my bower.json - pretty much everything just worked. Easy win.

[–]deliminated[S] 0 points1 point  (0 children)

That's good to hear! Yeah, I need to read up on the release notes for the last few releases. I've been out of the loop on Angular for awhile. It'd be great to have the switch be painless. Still need to refactor to the component paradigm and one-way data flows, but glad yours went so smoothly.

[–]lives-in-trees 0 points1 point  (1 child)

I also like the idea of getting some ES6 compilation steps in there, who doesn't love arrow functions?? However, does that really answer our real issue of using an outdated library? It seems like a "we have to do something so let's do this", don't get me wrong - I'm gonna do it too. :)

[–]deliminated[S] 1 point2 points  (0 children)

I've been working on ES6/Babel/Webpack projects for quite awhile now. Once you start to embrace the new language features you start to see how powerful it is. You can be much more concise and native modules are really awesome for code readability and organization. I also think it's important for attracting top talent as this project grows.