News for hackers. Stuff that matters.

A comment on Twitter.com's HTML, which is produced by React Native for Web, explained. Parent comment

Re:Twitter.com's HTML, which is produced by React Native for... by solarkraft on Thursday September 02, 2021 @01:40PM (#28395018)
Same here, with the same conclusion. React may not be my favorite web framework, but the native ecosystem blows everything else out of the water.

Desktop support is approaching “okay” (judging by the almost kinda somewhat native feeling flagship app Facebook Messenger on macOS), which puts it many kilometers ahead of any alternative.

The main alternatives for native feeling apps seem to be Xamarin Forms and Qt Quick, the former seems hard to do special things with and the latter has a pretty confusing and convoluted setup process. Neither has real web support.

[ Parent | on HN ]
Re:Twitter.com's HTML, which is produced by React Native for... by dmitriid on Friday September 03, 2021 @02:03AM (#28400905)
> kinda somewhat native feeling flagship app Facebook Messenger on macOS

You mean "horribly slow, loses scroll position, can't reliably load and display images, bad click targets everywhere" flagship app?

[ Parent | on HN ]
Re:Twitter.com's HTML, which is produced by React Native for... by solarkraft on Friday September 03, 2021 @08:04AM (#28403062)
… yeah. It’s not great. The corners aren’t even rounded. But my gut feeling is that it’s mostly a failing of the Facebook Devs, not React Native Desktop.
[ Parent | on HN ]
Re:Twitter.com's HTML, which is produced by React Native for... by dmitriid on Friday September 03, 2021 @09:41AM (#28404095)
More: it doesn't remember window size, takes up to several seconds to apply a custom background to a group chat, and requires a measly 1.1 GB of memory (3.6 GB of real memory) to fail to do all that.

This is the failing of both React Native Desktop and of the Facebook Devs that couldn't even make a rather primitive chat work properly.

[ Parent | on HN ]
Re:Twitter.com's HTML, which is produced by React Native for... by nyanpasu64 on Thursday September 02, 2021 @06:43PM (#28398304)
Judging from KDE's Kirigami apps and Subsurface on Android, I would not describe Qt Quick apps as native-performing or feeling.
[ Parent | on HN ]
Re:Twitter.com's HTML, which is produced by React Native for... by heavyset_go on Thursday September 02, 2021 @10:37PM (#28399843)
Last time I used Qt Quick, native looking widgets were outside of its scope. You're meant to define the styling you want for all of your widgets, and Qt will render them consistently across platforms.
[ Parent | on HN ]
Re:Twitter.com's HTML, which is produced by React Native for... by solarkraft on Friday September 03, 2021 @08:12AM (#28403113)
Out of scope for Qt Quick, perfectly in scope for Qt Quick controls. It looks very native on all the platforms I’ve tried, likely due to their experience with Qt Widgets.
[ Parent | on HN ]
Re:Twitter.com's HTML, which is produced by React Native for... by heavyset_go on Friday September 03, 2021 @05:27PM (#28409623)
Nice, thanks for pointing this out. Qt Quick Controls weren't around, or at least weren't available on the platforms I was developing against, like 9 years ago.
[ Parent | on HN ]
Re:Twitter.com's HTML, which is produced by React Native for... by solarkraft on Friday September 03, 2021 @08:10AM (#28403101)
Because you’re judging one that don’t try. There are demos of Qt Quick apps emulating Android very closely.
[ Parent | on HN ]
Re:Twitter.com's HTML, which is produced by React Native for... by nyanpasu64 on Saturday September 04, 2021 @04:59PM (#28419147)
What Qt Quick Controls 2 demos on Android would you recommend? Are they pre-built or do they require compiling myself?
[ Parent | on HN ]