23 ms·

I dont have much experience, but with react native, you only need to build 1 app for iphone and android, then potentially use react for web. Is there any compe

I dont have much experience, but with react native, you only need to build 1 app for iphone and android, then potentially use react for web. Is there any competition here? I could be unfamiliar with other solutions, but I thought the purpose of using JS was to eliminate re-writing code in multiple front end languages.

akuji1993 8y ago
You can even go the Cordova route and just write your entire application ONCE and use it on any plattform that Cordova can compile it to. The JS hate on HN is obviously always strong, but in this case, not really justified. Ruby and RoR are slow, you can check that in any benchmark and scaling your application will become a nightmare very fast. Experienced that in projects I actively worked in where the Backend was eventually rewritten from scratch in Java.
- realusername 8y ago
  > You can even go the Cordova route and just write your entire application ONCE and use it on any plattform that Cordova can compile it to. You can't blame Ruby for speed and talk about Cordova just after, it's a bit ironic... Cordova is one of the slowest cross-platform framework I know and that's a big reason the adoption is not going that well.
aantix 8y ago
>Is there any competition here? Yes. Building a responsive web application. https://m.signalvnoise.com/program-to-where-the-performance-puck-is-going-to-be-not-where-it-has-been-2e1c89bac058 https://m.signalvnoise.com/program-to-where-the-performance-...
toasterlovin 8y ago
The code for the server is different from the code for the frontend, even if they're in the same language. You're trying to do vastly different things. Front end is about user interface. Server is about controlling access to and storing data. IMO, you should use the best tool for each. Rails has been encapsulating the best practices around server side web apps for 15 years. The ecosystem is unbelievably mature and productive, regardless of whether you want to do a traditional server rendered app, or a JSON API for a JS, iOS, or Android client.
- vram22 8y ago
  >Rails has been encapsulating the best practices around server side web apps for 15 years. Not to be pedantic, but I worked on Rails projects in 2006 and 2007, and had probably heard of it just a bit before that. This was during the initial Web 2 boom. I would not have thought that Rails was created much earlier than that, since I usually keep some track of at least major tech developments (although could be wrong, of course - I could have missed reading about it when it was created, or only first read about it after it became a bit popular). So anyway, I googled, and the Wikipedia article for Rails says: >Initial release: 13 December 2005; 12 years ago[1] Haven't used it lately, but I do keep reading that it is very mature and productive, as you say.
  - toasterlovin 8y ago
    Ah, sorry. I was thinking 2003 instead of 2005. But anyway. A long time.
transfire 8y ago
http://www.rubymotion.com/ http://www.rubymotion.com/
sametmax 8y ago
React is not a stack. It's a component of a stack. Which is never the same anywhere.

akuji1993 8y ago

You can even go the Cordova route and just write your entire application ONCE and use it on any plattform that Cordova can compile it to. The JS hate on HN is obviously always strong, but in this case, not really justified. Ruby and RoR are slow, you can check that in any benchmark and scaling your application will become a nightmare very fast. Experienced that in projects I actively worked in where the Backend was eventually rewritten from scratch in Java.

realusername 8y ago
> You can even go the Cordova route and just write your entire application ONCE and use it on any plattform that Cordova can compile it to. You can't blame Ruby for speed and talk about Cordova just after, it's a bit ironic... Cordova is one of the slowest cross-platform framework I know and that's a big reason the adoption is not going that well.

aantix 8y ago

>Is there any competition here? Yes. Building a responsive web application. https://m.signalvnoise.com/program-to-where-the-performance-puck-is-going-to-be-not-where-it-has-been-2e1c89bac058 https://m.signalvnoise.com/program-to-where-the-performance-...

toasterlovin 8y ago

The code for the server is different from the code for the frontend, even if they're in the same language. You're trying to do vastly different things. Front end is about user interface. Server is about controlling access to and storing data. IMO, you should use the best tool for each. Rails has been encapsulating the best practices around server side web apps for 15 years. The ecosystem is unbelievably mature and productive, regardless of whether you want to do a traditional server rendered app, or a JSON API for a JS, iOS, or Android client.

vram22 8y ago
>Rails has been encapsulating the best practices around server side web apps for 15 years. Not to be pedantic, but I worked on Rails projects in 2006 and 2007, and had probably heard of it just a bit before that. This was during the initial Web 2 boom. I would not have thought that Rails was created much earlier than that, since I usually keep some track of at least major tech developments (although could be wrong, of course - I could have missed reading about it when it was created, or only first read about it after it became a bit popular). So anyway, I googled, and the Wikipedia article for Rails says: >Initial release: 13 December 2005; 12 years ago[1] Haven't used it lately, but I do keep reading that it is very mature and productive, as you say.
- toasterlovin 8y ago
  Ah, sorry. I was thinking 2003 instead of 2005. But anyway. A long time.

transfire 8y ago

http://www.rubymotion.com/ http://www.rubymotion.com/

sametmax 8y ago

React is not a stack. It's a component of a stack. Which is never the same anywhere.