6 ms·

The code style really reminds me of ExtJS circa 2.x (not sure what it's like now), which was pretty good at what it set out to do. However, React Native require

The code style really reminds me of ExtJS circa 2.x (not sure what it's like now), which was pretty good at what it set out to do. However, React Native requires compiling down to various different platforms which means having to maintain multiple compatibility layers to continually shift to keep up with the native vendors. You're also pretty much stuck with proprietary distributors as well. Fun. Fun. This does look interesting, but honestly, I think this can either already, or very soon, be replicated on the web, a platform which holds tremendous advantages that native will likely never be able to catch up to. Perhaps there's an argument that these apps can also be translated to the web when their time comes, but I wonder what sacrifices are being made in the name of going Native? React Native seems to be an attempt to fight in the opposite direction (Web -> native) while the real momentum is going the other way (native -> Web), and the best part is, you don't even have to do anything to get it, the major players are building that open ecosystem for us.

martco 12y ago
How is the real momentum going the other way (native -> Web)?
- jsprogrammer 12y ago
  Those who have created the native environments (Google, MS, Apple) are also creating the browsers, with another big player thrown in (Mozilla). Facebook makes web applications, has no native environment, and is trying to swim the other way.
- egillie 12y ago
  Google Native Client is a big push for native -> web, though I haven't heard much about it lately...
nwienert 12y ago
I agree with the "swimming the wrong way" sentiment, in my own very biased opinion. I'm working on reapp.io to solve just that. What's funny is react actually makes it possible to make hybrid a real option.
- jsprogrammer 12y ago
  That looks pretty interesting. Are there any plans to support responsive designs? What I really need (don't we all?) is a unified desktop & mobile code base.
- droidist2 12y ago
  Very interesting looking! One thing though is that the back button looks a little wonky in the Kitchen Sink demo.
pjmlp 12y ago
> I think this can either already, or very soon, be replicated on the web, a platform which holds tremendous advantages that native will likely never be able to catch up to. Looking at what HTML 5 offers and what any native platform from desktops to mobiles OS offers, I would rather stay with the disadvantages of native platforms. > while the real momentum is going the other way (native -> Web) Really? Is WebGL OpenGL 4.5 compatible already? What about those sensor APIs? Oh, which browser is doing OpenCL and CUDA? Web is stuck in a 90's desktop feature level and it will always be playing catch up native. The real direction is web -> native/micro-services.
- jsprogrammer 12y ago
  There will likely always be uses for the native platforms, especially on the desktop/power machines. I don't think React Native is targeting any of what you're talking about though. What the web has going for it (and what native will never catch up to) is having solved the distribution problem. Fact is, I can deploy to more machines, faster, and more securely than native (at least if there remain fragmented vendors) ever will be able to. I can already access most sensors and can run shaders. It's not like it's difficult to get what's missing into the browsers either and all the native vendors are also spending the resources to develop the browsers.
  - pjmlp 12y ago
    > What the web has going for it (and what native will never catch up to) is having solved the distribution problem. apt-get, yum, app stores, click once, web start, ...
    - jsprogrammer 12y ago
      Right: fragmented, environment dependent, user learning curve, etc. Web: URL + links
      - pjmlp 12y ago
        Web: Network always on required (offline apps is a joke), code behind a pay wall, data behind a pay wall, forced upgrades, removal of features without respect for the users, no guarantee of availability
sgk284 12y ago
I suspect your perspective is a bit skewed as most companies are building native apps first and only doing a webapp when / if it becomes necessary. Native apps have won the this round and their momentum isn't slowing down. IIRC, Facebook is seeing 78% year over year growth on their mobile app, while desktop usage is declining. Instagram is another huge use-case where the web app is a second-class citizen.
- jsprogrammer 12y ago
  What "most companies" are doing is mostly irrelevant in the larger picture. You're talking about proprietary networks and how they are shuttling their users around, while the interesting things are the opening up of real information and creating linked, collaborative, open ecosystems where everyone is free to participate. That's happening on the web, not in Facebook's latest iOS offering.
arxii 12y ago
this. i think the future is all about code flexibility. if your code is responsive and performs via stable hardware accelerated animations it will win because you only have to write it once. web will take over the mobile industry eventually, i can feel it.

martco 12y ago

How is the real momentum going the other way (native -> Web)?

jsprogrammer 12y ago
Those who have created the native environments (Google, MS, Apple) are also creating the browsers, with another big player thrown in (Mozilla). Facebook makes web applications, has no native environment, and is trying to swim the other way.
egillie 12y ago
Google Native Client is a big push for native -> web, though I haven't heard much about it lately...

nwienert 12y ago

I agree with the "swimming the wrong way" sentiment, in my own very biased opinion. I'm working on reapp.io to solve just that. What's funny is react actually makes it possible to make hybrid a real option.

jsprogrammer 12y ago
That looks pretty interesting. Are there any plans to support responsive designs? What I really need (don't we all?) is a unified desktop & mobile code base.
droidist2 12y ago
Very interesting looking! One thing though is that the back button looks a little wonky in the Kitchen Sink demo.

pjmlp 12y ago

> I think this can either already, or very soon, be replicated on the web, a platform which holds tremendous advantages that native will likely never be able to catch up to. Looking at what HTML 5 offers and what any native platform from desktops to mobiles OS offers, I would rather stay with the disadvantages of native platforms. > while the real momentum is going the other way (native -> Web) Really? Is WebGL OpenGL 4.5 compatible already? What about those sensor APIs? Oh, which browser is doing OpenCL and CUDA? Web is stuck in a 90's desktop feature level and it will always be playing catch up native. The real direction is web -> native/micro-services.

jsprogrammer 12y ago
There will likely always be uses for the native platforms, especially on the desktop/power machines. I don't think React Native is targeting any of what you're talking about though. What the web has going for it (and what native will never catch up to) is having solved the distribution problem. Fact is, I can deploy to more machines, faster, and more securely than native (at least if there remain fragmented vendors) ever will be able to. I can already access most sensors and can run shaders. It's not like it's difficult to get what's missing into the browsers either and all the native vendors are also spending the resources to develop the browsers.
- pjmlp 12y ago
  > What the web has going for it (and what native will never catch up to) is having solved the distribution problem. apt-get, yum, app stores, click once, web start, ...
  - jsprogrammer 12y ago
    Right: fragmented, environment dependent, user learning curve, etc. Web: URL + links
    - pjmlp 12y ago
      Web: Network always on required (offline apps is a joke), code behind a pay wall, data behind a pay wall, forced upgrades, removal of features without respect for the users, no guarantee of availability

sgk284 12y ago

I suspect your perspective is a bit skewed as most companies are building native apps first and only doing a webapp when / if it becomes necessary. Native apps have won the this round and their momentum isn't slowing down. IIRC, Facebook is seeing 78% year over year growth on their mobile app, while desktop usage is declining. Instagram is another huge use-case where the web app is a second-class citizen.

jsprogrammer 12y ago
What "most companies" are doing is mostly irrelevant in the larger picture. You're talking about proprietary networks and how they are shuttling their users around, while the interesting things are the opening up of real information and creating linked, collaborative, open ecosystems where everyone is free to participate. That's happening on the web, not in Facebook's latest iOS offering.

arxii 12y ago

this. i think the future is all about code flexibility. if your code is responsive and performs via stable hardware accelerated animations it will win because you only have to write it once. web will take over the mobile industry eventually, i can feel it.