21–30 of 81 posts
React has made me a happier developer and affords me a lifestyle to take care of my family very well. So I'm very thankful for everything that's taken place to bring React to where it is. I got the same feeling many many years ago when I made the switch from PHP > Rails. Edit: Why is this being down voted? shrug Must be 2 sad Ember devs... Badum PSSH
I think it's being down-voted because it sounds like a incontinence commercial.
In my day work we're using Angular 2 (Angular 4 technically), and while I prefer React it's not necessarily bad, just not as good in my opinion. That being said, backward compatibility is crazy non-existant. I had a library that required me to update to the latest version, would have been a minor bump. It wouldn't work with my current version, but then I upgraded and other libraries started breaking because they woul…
I’m not sure why this myth about Google not using Angular keeps propagating - I have heard it powers over 70% of Google’s frontends straight from multiple members of the Angular team. The one time AngularJS had a broken release, Google halted to a standstill.
Pete Hunt did make a great point about React avoiding the Angular 2 fiasco, although for Angular, I feel they were caught between a rock and a hard place - it probably would not be nearly as strong now if it weren’t for that choice.
I have mostly enjoyed my time with Angular 2+, and I have mostly enjoyed my time with React. I think it’s worth avoiding being quick to judge on these things, especially when the differences aren’t currently extraordinarily meaningful for most cases. When my current team was evaluating choices, we settled on React for team developer ergonomics. For some teams, that may not be React. A couple years down the line, it may be something else.
React has made me a happier developer and affords me a lifestyle to take care of my family very well. So I'm very thankful for everything that's taken place to bring React to where it is. I got the same feeling many many years ago when I made the switch from PHP > Rails. Edit: Why is this being down voted? shrug Must be 2 sad Ember devs... Badum PSSH
In my day work we're using Angular 2 (Angular 4 technically), and while I prefer React it's not necessarily bad, just not as good in my opinion. That being said, backward compatibility is crazy non-existant. I had a library that required me to update to the latest version, would have been a minor bump. It wouldn't work with my current version, but then I upgraded and other libraries started breaking because they woul…
Angular 2+ is "Angular"; Angular 1.x is "AngularJS"
React is great but this: "I’m waiting for the day when the only way that you build UI, the only way you can build UI is with the React paradigm." is scary.
React is great but this: "I’m waiting for the day when the only way that you build UI, the only way you can build UI is with the React paradigm." is scary.
TLDR React is not efficient enough, the performance requirements of next-gen apps of 2020s is going to break React because rendering is not incremental. These warts are basically places where React departs from pure functional programming to achieve ease of use.
1) Fundamental performance problem in render-tree-pruning (it is not truly reactive, it does more work than necessary). This is not an issue today except in the most sophisticated apps, but in apps of the 2020s it's going to be a huge problem. My startup http://hyperfiddle.net/ spends a great deal of energy trying to make React faster, it all boils down to forceUpdate which breaks the "functional programming" philosophy and makes the programming model significantly worse.
2) The solution to (1) is a reactive, spreadsheet-like programming model that generalizes to more than just the View-as-a-function, but also to the rest of the functions. React's solution injects fat "Component" instances everywhere in the view; its not actually just functions, so it breaks for the other expensive computations in the app, which will also need to be optimized in the 2020s.
https://github.com/slamdata/purescript-halogen is the best shot i know of at solving all this; it may be 5 more years yet until this is simplified enough to become mainstream, but all-in-all the ever increasing complexity of apps means truly efficient rendering is inevitable, and React is not that.
React has made me a happier developer and affords me a lifestyle to take care of my family very well. So I'm very thankful for everything that's taken place to bring React to where it is. I got the same feeling many many years ago when I made the switch from PHP > Rails. Edit: Why is this being down voted? shrug Must be 2 sad Ember devs... Badum PSSH
How did React do those things for you?
In my day work we're using Angular 2 (Angular 4 technically), and while I prefer React it's not necessarily bad, just not as good in my opinion. That being said, backward compatibility is crazy non-existant. I had a library that required me to update to the latest version, would have been a minor bump. It wouldn't work with my current version, but then I upgraded and other libraries started breaking because they woul…
"The main reason I've heard for using Angular 2 at my work is that it's made by Google" I say I used React, because it's made by Facebook. They say they use Angular, because it's made by Google. Others say, they use Ember or Vue, because it ISN'T made by a single big corp. In the end these reasons are often meaningless and don't have any effect on the users in their whole lifetime.
React is great but this: "I’m waiting for the day when the only way that you build UI, the only way you can build UI is with the React paradigm." is scary.
Why is that scary? React's paradigm has changed how UIs are built in many different platforms. And you don't have to use React directly to enjoy its paradigm since other libraries and technologies have appeared that follow the same approach.
Earlier quoted context omitted.
"The main reason I've heard for using Angular 2 at my work is that it's made by Google" I say I used React, because it's made by Facebook. They say they use Angular, because it's made by Google. Others say, they use Ember or Vue, because it ISN'T made by a single big corp. In the end these reasons are often meaningless and don't have any effect on the users in their whole lifetime.
It is a proxy for how likely the library will continue to exist, and how likely you can hire folks that know these libraries, in several years