6 ms·
Things you're sacrificing when going away from React: 1. Stability. FB uses it for their main product, which is probably the biggest web app of them all, they
by k__ 9y ago
Things you're sacrificing when going away from React:
1. Stability. FB uses it for their main product, which is probably the biggest web app of them all, they pay many devs to work fulltime on it. People coming from Angular, who had to migrate all those breaking changes over the years know the struggle.
2. Options like React-Native, React-VR and co. React enables your devs to acquire a whole new range of possibilities. It isn't just a web framework.
- thejosh 9y agoIts what they use right now, who knows what is coming down the pipeline?
- k__ 9y agoI honestly don't know, but using it 1. for their main product 2. for many different products in general and 3. rewriting most it (v16) to be more future proof without public API changes sounds like a pretty save bet.
- coldtea 9y agoNobody. But the fact that they use it now makes it less likely to be abandoned by them that something they don't use (which, while they can't abandon, they haven't adopted either). Besides in 10 years the whole of IT changes. Don't look for "50 year frameworks".
- thibaut_barrere 9y agoI don't consider the fact that a large company uses something for their main product is enough to actually make it future-proof. Previous instances of that pattern: - three20 (used in FB ios app https://en.wikipedia.org/wiki/Three20 https://en.wikipedia.org/wiki/Three20) - GWT - Angular is actually a similar instance of that problem, to some extent If "large company" switches their goal at some point, then you're still alone. Currently I'm kind of more confident (in some way) to the future stability of Vue, than of React (just a gut feeling, time will tell!).
- vosper 9y agoGWT was first released 11 years ago, the most recent update was less than a month ago. If that's not an example of future-proof (for web technologies) I don't know what is. Whether it's kept up with the state of the art I don't know, but I think that's a different thing.
- thibaut_barrere 9y agoI was referring to http://www.gwtproject.org/release-notes.html http://www.gwtproject.org/release-notes.html - e.g. the release hole that happened between 2.7.0 and 2.8.0 (2 years). Some clients actually decided to stop using GWT at that time, because of that.
- baxtr 9y agoAbsolutely. Look at google for instance and all the things they've stopped supporting. I find the argument also quite disturbing because this will add to the already existing monopolies of these "large companies".
- plorkyeran 9y agoThree20 was made obsolete by the useful parts of it getting built into the platform SDK, and yet it was still maintained and kept in a working state for longer than it was ever actually useful.
- thibaut_barrere 9y agoI know that - but the fact is that for one client of mine, the app was initially build on three20, then they had to literally rebuild it from scratch as they realised that three20 was becoming obsolete. One of the reasons for the choice was the FB branding associated as something that can be trusted!
- amauta 9y agoVue is backed by one of the biggest companies in China and many Chinese startups.
- coldtea 9y agoWell, and lots of Western startups from what I gather...
- TekMol 9y agoOptions like React-Native When you use React for a web app, how close are you to turn it into a React Native app?
- chii 9y agothe hearsay is that if you used only components that are available for both, it'd take very little extra boiler plate to get it working on both native and web. But all non-trivial apps have their own components and that's what makes native difficult.
- nathan_f77 9y agoThis is not really true, the react-native-web project provides compatibility for all of the fundamental components that you need, such as View, Image, ScrollView, TouchableOpacity, etc. There are still some missing components [1], but nothing I really needed (or couldn't work around). [1] https://github.com/necolas/react-native-web/issues/91 https://github.com/necolas/react-native-web/issues/91
- zackify 9y agoThis really isn't the case. I have built apps with lots of code reuse on native and web. Abstract all data logic and you can use the exact same code for both apps. This of course does not include your view layer. If you do it correctly, all you have to do is make a new set of view components. Stateless ones. Because you are injecting the state from your non platform specific components. It makes it extremely fast to build for other platforms. It just takes a few apps to fully understand how to abstract these things perfectly.
- k__ 9y agoI'm a freelancer, so I do different projects. Web, Mobile, etc. Now I can do them all with one framework.
- t1amat 9y agoIf you stick to using `react-native-web` components to design your web UI then your app is likely compatible with React Native and can be run as a mobile app in addition to deployed as a web site.
- matt2000 9y agoJust because Facebook is big and supports something isn't necessarily a good thing. Their goals, resources and accepted trade-offs aren't likely the same as your own. For a large company like Facebook, handling large changes to a library aren't a concern because they have essentially limitless development resources. For small operations like mine (and maybe yours) these breaking changes can reduce the time you spend actually improving your product significantly. For me, the instability and unopinionated nature of the group of technologies that loosely define "React" have been a real turn off. When answers to questions like "What language should you program in?", "How should you store your data?" and "How should I handle routing between pages?" all have no specific answer, it leads to a fragmentation of knowledge that in my past experience usually leads to a technology's demise.
- reaperducer 9y agoJust because Facebook is big and supports something isn't necessarily a good thing Not in hobbyspace. But in Deliver-a-Product World, it matters a lot.
- davidy123 9y agoReact has some of the best migration policies I've seen. They give plenty of notice about upcoming breaking changes, including messages with pointers output by the library in development mode when code is used in a deprecated way. As well, since there are so many people using React, you can nearly always find a solution to a even obscure problems. I agree about the un-opinionated nature, though the resulting flexibility has led to some good options, they can be complicated to choose and wire together.
- pier25 9y ago1. Vue has been pretty stable, and Angular has learned from its previous mistakes. Also, remember Parse. 2. There is NativeScript which supports Angular 2+ and shortly Vue, and Weex build by Alibaba on top of Vue.