This seems to dissuade some of the rumors on HN about React Native not being supported by Facebook.
The development experience is incredible (probably why Facebook mentioned instant reload), lots of companies are trying it out e.g. Evernote and the community is buzzing with new plugins. Plus it doesn't wrap native components so the core of it just works cross-platform.
I've love a JSX like tool for Flutter, especially since JSX is just syntactic sugar over a c-like syntax.
eh. The wrong type of typo can take down the entire app. Other typos it can recover from. Trying to change redux components just doesn't work. All in all it isn't too hard to fool RN's hot loading.
I'd also note that hot loading is turned off by default for RN! I can see why, having it on I have to know what types of things I can use it with and what types of changes will need a full relaunch.
Let's not even get into the "reload" button and what that may or may not do. (Note: I am using expo, so I have an additional layer of bugs and abstraction on top, having to force close Expo on the phone is way too common in my experience)
Instead of being wrappers around complicated native UI libraries, it's a 'game engine' over a lower level graphics layer. It's a smaller surface area to screw up on and create abstraction leaks. You don't have to be a iOS/Android and react native expert to fix hard issues, just a flutter expert for the most part.
It's just too bad the language run time is dart and it's run by google, which is infamous for being fairly ADD with projects.
2. This project definitely feels different compared to some of their others. The experience is just so much better than writing iOS or Android code that I think they would be insane not to support it.
https://harveynick.com/2018/05/21/an-ios-developers-opinions...
That would also be the day that I stop using MS Office as my go-to.
Because the performance was just not good enough.
They had custom, native UI while the backend was running in Java.
And it just wasn't fast enough. Even when hot, throughput and latency weren't good enough.
So, they started moving to C++ as much as possible, as fast as possible. By now you can run Writer without Java at all.
Current JS runtimes are all slower than HotSpot.
Yet somehow we're to believe that doing the exact same mistake again will work better this time?
It'll still end up being slow and a memory hog.
Moore's law is dead. RAM is more expensive than at any other point in almost 10 years.
You can't just throw abstractions at everything at the cost of performance anymore, expecting the hardware to catch up.
Somehow I got the feeling that MSFT has been invaded by JavaScript developers.
Working in C# on .net 4.5-4.7 is such a tremendously productive platform.
It appears it is the usual political issues between Microsoft divisions, which I thought had gotten better after all the re-organizations that took place.
I wouldn't be surprised if this JavaScript everywhere wasn't yet another way Microsoft is trying to appear cool among the Google devotees crowd, like how they are jumping in PWAs as well.
Microsoft is as relevant as ever outside SV coffee shops.