> Windows
> We are actively developing React Native for Windows...
> Mac
> Coming soon
So React Native for Windows.
React Native for Windows and Mac
101–110 of 505 posts
Re: React Native for Windows and Mac
#102React Native scares me with its dependency webs: http://npm.anvaka.com/#/view/2d/react-native From my experience, it's really great to work with and definitely saves a ton of work, but the depgraph above fills me with doubt for use in sensitive applications such as in finance or healthcare. For this reason, I've been trying out Flutter or even considering to go back to native apps. Perhaps there's some kind of middle…
batter/faster: http://npm.broofa.com/?q=react-native
Re: React Native for Windows and Mac
#103Flutter seems to be gaining ground on React Native. And they also have web and desktop ports. Recently flutter overtook react native on Google trends.
> Recently flutter overtook react native on Google trends.
How did you query this? I want to have a look, but the fact "flutter" shows data since 2004 means the terms I'm using are inflated [1]. Flutter is a dictionary word after all.
[1]: https://trends.google.com/trends/explore?date=all&geo=US&q=r...
Re: React Native for Windows and Mac
#104Earlier quoted context omitted.
Particularly outside of the US, in my experience. Having spent considerable time in React, RN, and Flutter the difference is remarkable. Unless devs are big fans of JS, Flutter is a compelling alternative [1]. 1: https://blog.benroux.me/us-devs-are-sleeping-on-flutter/
Your conclusion re: Cordova is pretty outdated. Also these days folks are moving to Capacitor instead.
Cordova has a pretty high "Would not use again" score: https://2019.stateofjs.com/mobile-desktop/cordova/. No data on Flutter or Capacitor unfortunately.
Re: React Native for Windows and Mac
#105React Native scares me with its dependency webs: http://npm.anvaka.com/#/view/2d/react-native From my experience, it's really great to work with and definitely saves a ton of work, but the depgraph above fills me with doubt for use in sensitive applications such as in finance or healthcare. For this reason, I've been trying out Flutter or even considering to go back to native apps. Perhaps there's some kind of middle…
Speaking of trusting trust, I think I'd love for Node¹ to support something like OpenBSD pledge (2) and unveil (2) for imports, where once you enter into a particular package certain capabilities are disabled. I would like to be able to assert that when I import some package, it and all of the packages it recursively includes do not perform network requests, do not use the filesystem outside of some folder, and so on…
This is a much more productive answer to the node dependency tree question than I'm used to encountering, and it's much more in line with most large modern systems are tending to address security from >1th party sources. Wall it off, require explicit permission, worry more about the security of the sandbox and less about the security of the dependencies. It doesn't address everything (and it becomes a lot riskier when you do give permission), but it's a far better proposal than shouting about how many dependencies are common in the JS ecosystem without any additional steps.
Re: React Native for Windows and Mac
#106> Windows > We are actively developing React Native for Windows... > Mac > Coming soon So React Native for Windows.
Don't forget... Microsoft <3 Linux. You can tell it's a top consideration.
Re: React Native for Windows and Mac
#107Earlier quoted context omitted.
The package.json file hasn't been remotely close to representative of the actual dependency count of a JS project for years.
sure, but it gives you the list of packages to look at in the dependency visualizer
It gives you a list of directly depended-upon packages. It doesn't give you a list of _those_ packages' dependencies, or _their_ dependencies, which funnily enough also get installed when you install your direct dependencies.
Plus I forgot to address this in my earlier comment: that visualizer only shows dependencies. By default it doesn't load any dev dependencies. You can confirm that for yourself by checking out https://npm.anvaka.com/#/view/2d/rollup for example - only the single runtime dependency on fsevents shows up, the dozens of dev dependencies Rollup has don't.
So yes, React Native does ship that overcomplicated graph of dependencies to all its users. I'll grant that at least _some_ of the code in those dependencies gets tree-shaken out.
Re: React Native for Windows and Mac
#108I tried using this a few months ago, as well as React Native for mobile and React Native Web for web, and I felt like they were all just hacks glued together to get cross-platform support, and RN isn't even native, it still includes a Javascript bridge. Build dependencies and packages were a nightmare, things continuously broke. I tried Flutter afterwards and it just felt like a breath of fresh air. Everything "just…
Instead of "Flutter", use "Flash" and you got the same thing!
Except hot reload
Re: React Native for Windows and Mac
#109Earlier quoted context omitted.
Same feeling here. still waiting for that killer flutter app to convince me one can actually build a real app with decent latency in flutter
What do you mean by killer exactly? Splice is now on flutter, including web. I'd say that is a pretty demanding app.
A killer app is something like Rails. Rails made Ruby popular, because it was so good that people who otherwise wouldn't have been interested in Ruby were willing to use it for the benefits they got from Rails.
Re: React Native for Windows and Mac
#110What would be the benefit over electron?
1. Not using the DOM for rendering. 2. Integrating native APIs is much easier.
> Being compiled to native code is a huge benefit.
It's still just running Javascript. The real difference is that it uses widgets that are native to the platform, instead of a browser engine/DOM.