4 ms·

There are millions of react developers so learning RN is much more easier. Dart is good but learning it just for flutter makes less sense

comatory 3y ago
I picked up Dart in a week or so and felt very productive with it in less than a month, the language itself is very easy to understand if you already know Typescript or Java. Flutter has a learning curve as well, you need to understand the concepts and the built-in widgets but even after month or so I was able to code up basic cross-platform app for iOS/Android. Ended up spending almost a year working on that project and gradually evolving it to support offline state, geolocation and real time updates.
pzo 3y ago
If you are comming from front-end side (javascript, typescript, react) then sure. But for me who didn't touch front-end since 10 years and did mostly: Java nad C++, Objective-C, Swift, Python there is no easy way to learn the React Native ecosystem. I tried RN last week and I been all the time googling to figure out all the choices: 1) should I use nvm, n, nodenv for for nodejs management? Should I use script or homebrew? 2) what's the difference between npm, npx? Why npx giving mi different version number than node? Did I had some old version of nodejs from some dependency when using homebrew? Will it bite me in the future (those all questions were in my head) 3) should I use expo cli, ignite cli, react native cli? 4) expo vs repack vs vite vs capacitor vs tauri 5) webpack vs metro vs swc vs esbuild vs rollout vs sucrase... 6) vanilla react or next.js or react native or solido? 7) what ui kit to use? native-base? tamagui? react-native-paper? They all sucks in some way comparing to flutter proposition 8) should I use style-components? emotion? tailwindcss? nativewind? 9) should i use vanilla javascript or typescript? (is learning typescript straight away is too big to swallow in one bite?) 10) learn vscode shortcuts + figure out which plugin to install and how to setup 11) JSON config hell in RN for everything: postcss, vite, tailwind etc. 12) react-navigation vs react-native-navigation vs expo-router 13) redux vs mobx vs mobx-state-tree React native feels to me like thinkpad + dekstop linux: you like the philosophy, crossing finger it gets better and less fragmented and working out of the box But in the end you end up buying macbook with macOS (feels like flutter) even though you hate apple solders stuff and it's gonna cost you a lot of it breaks and apple giving you limited choices and too much constrained walled garden.
- cageface 3y ago
  This is one of the nicest things about Flutter. Out of the box you get most of the things you need to build an app. There's a lot of competition for state managers but other than that you have a lot fewer choices you have to make to get started and fewer third party pieces to break on you.

comatory 3y ago

I picked up Dart in a week or so and felt very productive with it in less than a month, the language itself is very easy to understand if you already know Typescript or Java. Flutter has a learning curve as well, you need to understand the concepts and the built-in widgets but even after month or so I was able to code up basic cross-platform app for iOS/Android. Ended up spending almost a year working on that project and gradually evolving it to support offline state, geolocation and real time updates.

pzo 3y ago

If you are comming from front-end side (javascript, typescript, react) then sure. But for me who didn't touch front-end since 10 years and did mostly: Java nad C++, Objective-C, Swift, Python there is no easy way to learn the React Native ecosystem. I tried RN last week and I been all the time googling to figure out all the choices: 1) should I use nvm, n, nodenv for for nodejs management? Should I use script or homebrew? 2) what's the difference between npm, npx? Why npx giving mi different version number than node? Did I had some old version of nodejs from some dependency when using homebrew? Will it bite me in the future (those all questions were in my head) 3) should I use expo cli, ignite cli, react native cli? 4) expo vs repack vs vite vs capacitor vs tauri 5) webpack vs metro vs swc vs esbuild vs rollout vs sucrase... 6) vanilla react or next.js or react native or solido? 7) what ui kit to use? native-base? tamagui? react-native-paper? They all sucks in some way comparing to flutter proposition 8) should I use style-components? emotion? tailwindcss? nativewind? 9) should i use vanilla javascript or typescript? (is learning typescript straight away is too big to swallow in one bite?) 10) learn vscode shortcuts + figure out which plugin to install and how to setup 11) JSON config hell in RN for everything: postcss, vite, tailwind etc. 12) react-navigation vs react-native-navigation vs expo-router 13) redux vs mobx vs mobx-state-tree React native feels to me like thinkpad + dekstop linux: you like the philosophy, crossing finger it gets better and less fragmented and working out of the box But in the end you end up buying macbook with macOS (feels like flutter) even though you hate apple solders stuff and it's gonna cost you a lot of it breaks and apple giving you limited choices and too much constrained walled garden.

cageface 3y ago
This is one of the nicest things about Flutter. Out of the box you get most of the things you need to build an app. There's a lot of competition for state managers but other than that you have a lot fewer choices you have to make to get started and fewer third party pieces to break on you.