Can we please stop trying to Javascriptify everything? The cross-platform thing has been tried again and again and again, and always runs into the same pitfalls: poor mimicry of native standards, inefficiency, debugging difficulty because of abstraction layer built on abstraction layer, enabling developers with poor understanding of the underlying platform to make an absolute mess of an app for others to maintain later on, and so on.
With the issues I've had with React Native, I'm keeping my eye on Flutter, great dev experience backed by a well resourced team, hope to see its ecosystem catch up.<p>A couple of projects to watch out for:<p>[1]: <a href="https://feather-apps.com/" rel="nofollow">https://feather-apps.com/</a><p>[2]: <a href="https://github.com/google/flutter-desktop-embedding" rel="nofollow">https://github.com/google/flutter-desktop-embedding</a>
I'd love to hear more about how this differentiates from existing alternatives, namely Proton Native[1] and the NodeJS bindings to libui[2]. I am specifically interested to see how/if/when Microsoft will support Linux and macOS, as the aforementioned solutions already do.<p>[1] <a href="https://proton-native.js.org/#/" rel="nofollow">https://proton-native.js.org/#/</a><p>[2] <a href="https://github.com/parro-it/libui-node" rel="nofollow">https://github.com/parro-it/libui-node</a>
Anyone know which definition of lightweight is in effect here? :)<p>I see Atom called lightweight all the time. I remember when my PC had a 5MEG HDD and exactly 640k of RAM, so...<p>I'm curious what amount of resources (disk, runtime memory etc) is used for something like a small CRUD app (think simple phonebook or CD library)<p>If you know the answer for proton native, please post that too!
I’d be more interested in knowing if someone had ported the ideas behind react in a cross platform language, rather than shipping a JavaScript engine with all your apps. Or maybe there should a JavaScript virtual machine in the OS itself.
There's mention of MacOS in the codebase and a few PRs but there are no samples or documentation on getting it working, which is a little frustrating.<p><a href="https://github.com/Microsoft/reactxp/issues/19#issuecomment-371781900" rel="nofollow">https://github.com/Microsoft/reactxp/issues/19#issuecomment-...</a>
I think ReactXP is not a visionary project but Microsoft's approach to take advantage of javascript developers and make them able to build mobile apps for Windows phones beside indispensable platforms(Android, iOS).
Seriously, Microsoft? From your own websites:<p>Xamarin: <i>Deliver native Android, iOS, and Windows apps with a single shared .NET code base.</i><p>ReactXP: <i>Share most of your code between the web, iOS, Android, and Windows.</i>
From the article:
""XP means X-Platform
Share most of your code between the web, iOS, Android, and Windows.""<p>So, not exactly cross-platform.
> Share most of your code between the web, iOS, Android, and Windows<p>How is it better than React and React Native if it still is web+mobile+Windows and doesn't offer Linux and macOS support? Also doesn't the fact React is by Facebook and ReactXP is by Microsoft and introduces Windows support look suspicious like if they were building an incompatible version of React like they've done with Java in the past?
I'm sure this was in the works well before Safari/iOS 11 implemented the majority of the PWA standard, but can someone help me understand what the target market is for this in 2018?<p>We just built a ground-up PWA and users LOVE it (Android/iOS, tablet/phone/PC).<p>Why complicate and slow your programming + production software down by trying to XP?
What a surprise that a supposedly "cross-platform" solution from Microsoft does not support any of the competing platforms (macOS, Linux...). /s
Smells of EEE...
That name harkened back to era of Internet Explorer 6 and evoked painful related JS/CSS development memories even before realizing it's Microsoft's project :D