3 ms·

Maybe it's just me, but as an C++, Objective-C and Swift programmer, React Native doesn't really appeal to me that much. At least on the iOS and Mac, I don't r

Maybe it's just me, but as an C++, Objective-C and Swift programmer, React Native doesn't really appeal to me that much. At least on the iOS and Mac, I don't really want to give up on Swift in favor of Javascript. I like React on the web. In my view, conceptually it's the most interesting framework out there and that's saying a lot, given the jungle of JS frameworks populating the web. But I also like UIKit and the other native frameworks, now that I've spent so much time learning to use them right. I'll give it a try anyway, I'm sure there's something to like about it and probably something to learn too..

on_and_off 11y ago
As a Java, Kotlin & Rust programmer, React Native does not appeal to me either. The main appeal seems to be that web devs can continue to use js for most of their work, it does not really appeal to a mobile dev..
- LeoNatan25 11y ago
  Web developers should remain on the web, or put enough time to learn new technologies. For a good developer, moving to another language and framework is not really that difficult. Just means to a goal. If, however, the mere thought of learning Swift or Java scares the living hell out of a "developer", then that "developer" is better left outside of my ecosystem as a mobile apps user.
  - neoeldex 11y ago
    The thing about React Native vs other frameworks is that it is cross platform. There aren't many proper cross platform frameworks which allow for 1 app, to be web-based and have native siblings in 1 codebase. I'm not scared of Swift or Java, But I am frigthened of their ux. Even big apps like eclipse put me off, due to their bloat. Also frameworks like QT don't offer the same ease of development. Remember React-Native is currently on version 0.22, and over a year old. IMO it currently offers much better ux than TK/Swing/Qt/...
    - pjmlp 11y ago
      > Remember React-Native is currently on version 0.22, and over a year old. IMO it currently offers much better ux than TK/Swing/Qt/... The day it offers something like Expression Blend, Qt Creator, Netbeans Matisse, Scene Builder, Storyboards ... I will believe it.
  - gldalmaso 11y ago
    From what I gather this is more often a business decision than an individual developer's decision. When a product needs to go mobile for the first time on two platforms you have to make a business decision: 1) You can grow the team to tackle both platforms in parallel. 2) You can have the team do it one platform at a time. 3) You can have the team do it one time. Every option has big trade offs in either cost, time or user experience. There's somewhat of a gradient there as well in terms of code reuse giving the options avaiable right now. React Native sits somewhere between 2 and 3. It's really a matter of context for the business. How much time you have? Resources? What does your target user expect? For a lot of B2B companies, there's just not enough value added to choose between 1 and 2 since you either take more cost or more time to market and your user just needs the feature not the best possible experience. For a lot of B2C, your product may already be born mobile and you need the best possible experience to compete.
potomushto 11y ago
What do you think about ComponentKit, the Facebook's approach to declarative view model similar to React? You don't need js there.

on_and_off 11y ago

As a Java, Kotlin & Rust programmer, React Native does not appeal to me either. The main appeal seems to be that web devs can continue to use js for most of their work, it does not really appeal to a mobile dev..

LeoNatan25 11y ago
Web developers should remain on the web, or put enough time to learn new technologies. For a good developer, moving to another language and framework is not really that difficult. Just means to a goal. If, however, the mere thought of learning Swift or Java scares the living hell out of a "developer", then that "developer" is better left outside of my ecosystem as a mobile apps user.
- neoeldex 11y ago
  The thing about React Native vs other frameworks is that it is cross platform. There aren't many proper cross platform frameworks which allow for 1 app, to be web-based and have native siblings in 1 codebase. I'm not scared of Swift or Java, But I am frigthened of their ux. Even big apps like eclipse put me off, due to their bloat. Also frameworks like QT don't offer the same ease of development. Remember React-Native is currently on version 0.22, and over a year old. IMO it currently offers much better ux than TK/Swing/Qt/...
  - pjmlp 11y ago
    > Remember React-Native is currently on version 0.22, and over a year old. IMO it currently offers much better ux than TK/Swing/Qt/... The day it offers something like Expression Blend, Qt Creator, Netbeans Matisse, Scene Builder, Storyboards ... I will believe it.
- gldalmaso 11y ago
  From what I gather this is more often a business decision than an individual developer's decision. When a product needs to go mobile for the first time on two platforms you have to make a business decision: 1) You can grow the team to tackle both platforms in parallel. 2) You can have the team do it one platform at a time. 3) You can have the team do it one time. Every option has big trade offs in either cost, time or user experience. There's somewhat of a gradient there as well in terms of code reuse giving the options avaiable right now. React Native sits somewhere between 2 and 3. It's really a matter of context for the business. How much time you have? Resources? What does your target user expect? For a lot of B2B companies, there's just not enough value added to choose between 1 and 2 since you either take more cost or more time to market and your user just needs the feature not the best possible experience. For a lot of B2C, your product may already be born mobile and you need the best possible experience to compete.

potomushto 11y ago

What do you think about ComponentKit, the Facebook's approach to declarative view model similar to React? You don't need js there.