Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

React Native for Windows and Mac

microsoft.github.io

Post reply on HN
Print view View original

131–140 of 505 posts

Re: React Native for Windows and Mac

#131

Post by c-smile »

qppo wrote: post #113
c-smile wrote: post #98

Earlier quoted context omitted.

Sciter then ( https://sciter.com ): - multiple platforms... Yes: Windows (x32,x64, ARM64), from XP to 10, MacOS, Linux/GTK, IoT and mobiles. - multiple windows - Yes. Multiple desktop windows and you can even render separate DOM elements in popup windows. - rendering to a window that isn't owned by the UI being rendered Yes, you can render it on top DirectX, OpenGL, Vulkan (coming) or in child window/nsview/gtkwidget…

Kind of a chicken and egg situation, I looked at sciter for a project about a year ago and estimated that it would cost more time/money to get things off the ground in your framework than using my existing codebase and frameworks with larger ecosystems. I can't really commit to sciter and your flavor of JS until it has a larger community, more docs, and more onboarding materials so I can get teams up to speed and wor…

1. I've been told that it takes 1..2 weeks for average front end developer to get into Sciter and features that I've added to HTML/CSS to support desktop UI use cases.

2. "larger ecosystems..." Sciter is embeddable and extendable engine, this means that you can extend it by existing native libraries, time proven and effective. Here is how SQLite native namespace looks in Sciter: https://github.com/c-smile/sciter-sdk/blob/master/sqlite/sci...

3. "it has a larger community..."

I am aiming not to larger but rather more professional community. Sciter sources contains patches from these dev teams: https://sciter.com/#customers Security audit was made by Symantec and 3 more AntiVirus vendors. All that... Source code base is compact enough for a C++ programmer to get into when needed.

"Some bencharks comparing engine performance to V8"

Slower than V8 but faster than Python 3. But script performance in Sciter is not that critical (never been a bottleneck) for simple reason: script treated as a glue between native function calls. If you need something to run with bare metal speed - just provide native function(s) for this functionality. JS approach in this respect is simply crazy: to run something fast add megatons of JIT implementation and then another twist: WebAssembler. Why not just to compile what is needed with C++ into native code and call it? Again, Sciter is embeddable and extendable by design.

Re: React Native for Windows and Mac

#132

Post by RobertKerans »

0xDEEPFAC wrote: post #40
mynameisvlad wrote: post #35

Earlier quoted context omitted.

It is not. Here's the GitHub for the Windows implementation: https://github.com/microsoft/react-native-windows And here's the fork of React Native for the Mac one (it doesn't seem to be as polished as the Windows one yet): https://github.com/microsoft/react-native-macos

I would be very surprised if they didn't use any pieces used by Edge (how else would they render css?). A quick search of their code though and I couldn't find it. Perhaps I assumed too much

It doesn't render CSS, not in that context. The way styling for layout and for colour/text/etc is specified is designed to match a subset of CSS so that developers can easily transition across to the platform, that's all (and for layout it uses an engine called Yoga, which implements CSS' flexbox spec). So in the context of actual component code, it's a layer designed to look like CSS that can generate whatever the backend being used requires to render (so it should be able to produce valid CSS as an output, as in the case of React Native Web)

Re: React Native for Windows and Mac

#133

Post by acoates »

brdd wrote: post #23

I'm really excited, although the Mac part of this page is somewhat misleading — there isn't anything available on the Mac side yet (everything is "coming soon")

react-native-macos is available today. The documentation is linked on the sidebar: https://microsoft.github.io/react-native-windows/docs/next/r...

Re: React Native for Windows and Mac

#134

Post by qppo »

c-smile wrote: post #131
qppo wrote: post #113

Earlier quoted context omitted.

Kind of a chicken and egg situation, I looked at sciter for a project about a year ago and estimated that it would cost more time/money to get things off the ground in your framework than using my existing codebase and frameworks with larger ecosystems. I can't really commit to sciter and your flavor of JS until it has a larger community, more docs, and more onboarding materials so I can get teams up to speed and wor…

1. I've been told that it takes 1..2 weeks for average front end developer to get into Sciter and features that I've added to HTML/CSS to support desktop UI use cases. 2. "larger ecosystems..." Sciter is embeddable and extendable engine, this means that you can extend it by existing native libraries, time proven and effective. Here is how SQLite native namespace looks in Sciter: https://github.com/c-smile/sciter-sdk/…

Very interesting work. I need to re-evaluate in the future.

Re: React Native for Windows and Mac

#135

Post by yesimahuman »

tphan wrote: post #114

I've used React Native for a client and, whilst it was super clunky, I still enjoyed being able to write React to deploy to mobile. With React Native for Web, you can technical write code that writes to a bunch of different platforms, a big selling point for businesses.

Check out Ionic which now fully supports React and will give you a similar benefit but without the need to use RNW or have different code for each platform. Also Ionic’s components are much more robust and widely used than RNW.

Re: React Native for Windows and Mac

#137

Post by _bxg1 »

gitgud wrote: post #115
yesimahuman wrote: post #76

Earlier quoted context omitted.

I would be careful with Flutter’s web port. It’s going to be a pretty divergent approach in terms of web dev familiarity, bundle size, and compatibility with native web features (they had to implement copy and paste from scratch, for example). It is very similar to the approach Famous took back when. It is not looked kindly upon by many web platform advocates I know.

The Flutter web port is ridiculous. It circumvents the entire point of a Web page as it's literally just a canvas on the Web page. You lose all advantages that HTML and CSS gives you, links, styling, accessibility, text selection! ... It's basically a flash website... Which admittedly is okay for some applications

It's Flash all over again, with a fresh coat of paint.

Re: React Native for Windows and Mac

#138

Post by ubercore »

Exuma wrote: post #122
wyc wrote: 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…

It was the worst experience of my development life, building a phone app with it........................ never, never, never again. If you want to know what it's like to have everything break LITERALLY every few days, use react native.

There were breaks for sure, but I worked in a shared-codebase web/native app using RN and React, and it was overall pretty pleasant. How early were you using it? It was actually pretty reliable.

Re: React Native for Windows and Mac

#139

Post by ahupp »

AaronFriel wrote: post #51
wyc wrote: 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…

This is a really cool idea.

Re: React Native for Windows and Mac

#140

Post by fermienrico »

wyc wrote: 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…

The web has become truly awful and it’s invading desktop apps. We need to refactor our technology stack.
Post reply on HN