| Hey thx for the comment. Per the post, I already stated I don't much experience yet and that will change come next mo. But wanted to simply emphasize that after working with RN that I'm quite excited about Flutter. Re the JS hate, it's more of "JS exhaustion" but yes I'm strongly opinionated. Hopefully WebAssembly will cure this down the road who knows. For example, it's almost 2018 and folks are still trying to settle on something as fundamental as React Native navigation. I guess with the dev landscape now the JS love/hate varies. Re the hiring pool that's a great point. But hiring JS devs sometimes is like hiring PHP devs: if you're doing something simple it's no problem, but more complex then you get lots of horrible candidates to sift through until you hopefully manage to find someone good/with a proper programming education. But I guess it also greatly depends on the hiring location too. Re adoption, I think if you're a web dev already, you're used to it, but if you're a backend dev or native mobile dev it's something hard to deal with. I guess I can point out some situations: 1. People who can tolerate JS but no mobile dev exp yet -> React Native is a great option. 2. Existing native mobile engineers used to compiled languages like Swift or Java and who want to pick up a hybrid dev framework -> Flutter, (while still in alpha) has a ton of potential. Note that anyone who knows Ruby, Go, C#, etc etc can easily pick up Dart in less than a day. As stated in my original post, I do plan to re-write some of my apps with Flutter and I will be reporting about my experiences for better or worse. |