doing my best to ignore the rick and morty usage
Okay, besides that petty complaint, good article. However, knowing Dart somewhat and knowing JS very well... And seeing that it was inspired by React Native, and the code samples and terminology is all weirdly overloaded terms being used for different purposes.... kinda just wants to make me stick with react native and/or true native development
Maybe in an ideal world we would all be using Dart for all mobile applications and job boards would be full of listings for Haskell devs.... but we don't live in that world and I think working in xCode is a lot nicer than fucking around with Dart UI syntax.
If things get serious with their Fuchsia OS things may change rapidly, it's easier to use 1 language for 3-4 platforms.Ofc we will never get rid of the native part (libraries), but at least we can try.
doing my best to ignore the rick and morty usage
Okay, besides that petty complaint, good article. However, knowing Dart somewhat and knowing JS very well... And seeing that it was inspired by React Native, and the code samples and terminology is all weirdly overloaded terms being used for different purposes.... kinda just wants to make me stick with react native and/or true native development
Maybe in an ideal world we would all be using Dart for all mobile applications and job boards would be full of listings for Haskell devs.... but we don't live in that world and I think working in xCode is a lot nicer than fucking around with Dart UI syntax.
also this (pay attention to eich's quote: walkercoderanger.com/blog/2014/03/... )
I think their issue with the type system is fixed in Dart 2.0
If things get serious with their Fuchsia OS things may change rapidly, it's easier to use 1 language for 3-4 platforms.Ofc we will never get rid of the native part (libraries), but at least we can try.
Good point! Native still has an upper hand tho. Could you point out some weird terms as relating to Flutter?