Live data from Hacker News

React Native for Windows and Mac

microsoft.github.io

51–60 of 505 posts

Re: React Native for Windows and Mac

#51
post #17

React 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.

A fine grained capability system for packages would dramatically improve the safety profile, and if this were built into package.json and the lockfile we could do the following:

1. Packages advertise what their default capabilities should be limited to 2. Changes in those capabilities are encoded in the package lock file, and can't be changed without the user explicitly affirming them

¹ and other langs with extensive use of package managers and micro-packages

Re: React Native for Windows and Mac

#52
post #17

React 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…

wtf! that's insane! now I'm curious to look up other oss projects I use :)

Re: React Native for Windows and Mac

#53
post #6

I'd love to abandon my C/C++ UI frameworks for React, but I need - consistent rendering/support across multiple platforms and versions - multiple windows - rendering to a window that isn't owned by the UI being rendered or created by the framework Can I do that all in React native? Edit: don't need to bring up electron.

You could use Flutter. It has the first point, but I am not necessarily sure about the latter ones.

Re: React Native for Windows and Mac

#56
post #17

React 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…

I wonder why there is no effort towards reducing the dependencies, or at least vendoring the worst offenders.

It would be a huge quality-of-life improvement for React developers, not to mention the improved security and reliability.

Re: React Native for Windows and Mac

#57

Not sure what the advantage here is over Electron. I know the chromium engine is a resource hog, but the scalability/mix between platforms makes it worth it. Curious to know what your thoughts are folks!

EDITED React native's GUI compiles to native code. Or something like that. It is very different from Electron.

Re: React Native for Windows and Mac

#58

Not sure what the advantage here is over Electron. I know the chromium engine is a resource hog, but the scalability/mix between platforms makes it worth it. Curious to know what your thoughts are folks!

> I know the chromium engine is a resource hog, but the scalability/mix between platforms makes it worth it.

Worth it for some. Personally, I refuse to use any Electron apps because they have a highly non-native-feeling UX and because they're resource hogs.

This announcement excites me, because React Native is likely to be an improvement on both counts.

The UX still won't be quite as native-feeling as a single-platform app designed for that platform's unique idioms – but as long as it uses native controls under the hood, that's still 10x better than Electron in my book.

And even without the bloat of Chromium, an app written in JS is still likely to be slower than one written in, say, C++ or Rust – but most GUIs don't really need that level of performance. And at least on macOS, the competition is not C++ or Rust but Objective-C and Swift, which are both slower, more on par with JS in terms of performance.

Re: React Native for Windows and Mac

#59
post #17

React 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…

> A fine grained capability system for packages would dramatically improve the safety profile

I think Deno does that (the new project by Node's original creator):

https://blog.logrocket.com/what-is-deno/

Re: React Native for Windows and Mac

#60
post #45

Earlier quoted context omitted.

Windows Forms was released on 2002 and is still supported by Microsoft. How long do you think Flutter will be supported by Google? For dev technology, Microsoft has a well-deserved reputation for supporting products for a long time.

It... depends. Remember Silverlight?

The last version of Silverlight, Silverlight 5 is actually supported until next year, 10 years after the initial 5.x release, which is not really "short" by any standard.

It's mostly the browser's ecosystem moved away from these for more standard based approaches.

Post reply on HN