3 ms·
> Web Components don't solve the problems React is solving. They are completely different (and sometimes complementary tools). No, they don't solve the same pr
by marknutter 12y ago
> Web Components don't solve the problems React is solving. They are completely different (and sometimes complementary tools).
No, they don't solve the same problem, but that's not what I was suggesting. What Web Components are trying to solve is the problem of sharing code, and if React doesn't play nicely with Web Components it's going to make it very difficult for React developers to partake in that sharing. Contrast that with the Angular team who are drastically overhauling their entire framework in order to be compatible with Web Components. I prefer that strategy over the long term (Ember is also actively preparing for Web Components).
> I can't speak for Facebook but I think you're missing the point of React Native. It's not a solution to run webapps on native platforms.
I am not missing the point. I get that it's goal isn't to allow web apps to run inside native wrappers.
> React Native is a solution to write native UI code with declarative paradigm. That it runs in JS is an implementation detail. If you look at it from that point of view, hybrid vs native doesn't even come into equation. "Native" is the original requirement here, as far as I understand it. Unless you propose to not write native apps at all.
I'm proposing it's better to either choose to write native apps using native languages and SDKs, or write them as web apps and embed them inside native wrappers like Reapp is doing. Hybrid vs. native does come into the equation because it's worth pointing out the pros and cons of every approach to mobile app development.
People are frothing at the mouth in response to React Native without fully understanding the tradeoffs inherit with that approach, so it's worth properly setting expectations in response to overwhelming hype. Appcelerator has been around for years and solves the same problem in the same way (minus React's declarative pattern) and it hasn't been a panacea.
- dustingetz 12y agoIt appears to me that you are misinformed, React plays just fine with Web Components. https://groups.google.com/forum/?fromgroups=#!searchin/reactjs/web$20components/reactjs/Z4jaRKJK5zU/uf4Ww9GU64AJ https://groups.google.com/forum/?fromgroups=#!searchin/react...
- marknutter 12y agoExactly which part of that thread leads you to believe that "React plays just fine with Web Components". I suggest you watch https://www.youtube.com/watch?v=g0TD0efcwVg https://www.youtube.com/watch?v=g0TD0efcwVg which gives a very clear picture of the current state of React/Web Component interaction, including the challenges associated with it. edit: another good read if you're interested: http://futurice.com/blog/combining-react-flux-and-web-components http://futurice.com/blog/combining-react-flux-and-web-compon...