3 ms·

With all due respect, React and Redux are still "in" and one of those buzz word frameworks right now. Your sentiment would mean a lot more if you were still hav

With all due respect, React and Redux are still "in" and one of those buzz word frameworks right now. Your sentiment would mean a lot more if you were still having success with something like Angular 1. You aren't proving you are resilient to changes by using one of the most current buzz-word filled frameworks out there for two years. The real test happens when your framework of choice truly becomes obsolete, like with what happened to Angular 1.

gtsteve 9y ago
Is React still "in"? I thought the recent BSD+Patents furore had made it uncool, but perhaps this doesn't bother developers as much as I originally thought.
- jonny_eh 9y ago
  A lot of that was overblown, I haven't seen a change in sentiment in the projects I work on. It's not like the patents clause was new, it was just Apache Foundation deciding to ban it that way. So as long as you're not working on an Apache project, you're unaffected.
  - dceddia 9y ago
    Also, WordPress is dumping React - https://ma.tt/2017/09/on-react-and-wordpress/ https://ma.tt/2017/09/on-react-and-wordpress/ But I agree, I do not think everyone is jumping ship to Vue (or whatever) over the license.
- deleted 9y ago
  [deleted]
morgancmartin 9y ago
I completely agree. We are using Angular 1.x at my day job and my team and I are feeling the pain. Manual DOM manipulation compared to React's virtual DOM feels like what it must have used to feel like comparing jQuery to Angular 1. Perhaps frameworks don't rust in the sense that they deteriorate in terms of capabilities over time. But that doesn't mean that they don't become obsolete. Especially when you're building a product and trying to stay competitive, all the while all the the innovation surrounding a framework has packed up and left for a nicer camp.
- botskonet 9y ago
  We're using Angular 1 too, chosen just over two years ago. The two-way binding/digest nature has really become our enemy. Everything we write has to account for digests and we've wound up with some terribly ugly code to account for digest problems. Angular 1 is great for hobbyists and it makes implementing simple forms easy but when you use it for an enterprise app, it hurts. Our app is still vastly better than decade-old 1.0 we've replaced, but we sure hate the digest now.
  - PopsiclePete 9y ago
    >We're using Angular 1 too, chosen just over two years ago. Good god. You chose Angular 1 two years ago? As in 2015? When its horrific shortcomings were already known and the Angular devs were working on Angular 2.x?

gtsteve 9y ago

Is React still "in"? I thought the recent BSD+Patents furore had made it uncool, but perhaps this doesn't bother developers as much as I originally thought.

jonny_eh 9y ago
A lot of that was overblown, I haven't seen a change in sentiment in the projects I work on. It's not like the patents clause was new, it was just Apache Foundation deciding to ban it that way. So as long as you're not working on an Apache project, you're unaffected.
- dceddia 9y ago
  Also, WordPress is dumping React - https://ma.tt/2017/09/on-react-and-wordpress/ https://ma.tt/2017/09/on-react-and-wordpress/ But I agree, I do not think everyone is jumping ship to Vue (or whatever) over the license.
deleted 9y ago
[deleted]

morgancmartin 9y ago

I completely agree. We are using Angular 1.x at my day job and my team and I are feeling the pain. Manual DOM manipulation compared to React's virtual DOM feels like what it must have used to feel like comparing jQuery to Angular 1. Perhaps frameworks don't rust in the sense that they deteriorate in terms of capabilities over time. But that doesn't mean that they don't become obsolete. Especially when you're building a product and trying to stay competitive, all the while all the the innovation surrounding a framework has packed up and left for a nicer camp.

botskonet 9y ago
We're using Angular 1 too, chosen just over two years ago. The two-way binding/digest nature has really become our enemy. Everything we write has to account for digests and we've wound up with some terribly ugly code to account for digest problems. Angular 1 is great for hobbyists and it makes implementing simple forms easy but when you use it for an enterprise app, it hurts. Our app is still vastly better than decade-old 1.0 we've replaced, but we sure hate the digest now.
- PopsiclePete 9y ago
  >We're using Angular 1 too, chosen just over two years ago. Good god. You chose Angular 1 two years ago? As in 2015? When its horrific shortcomings were already known and the Angular devs were working on Angular 2.x?