501–505 of 505 posts
Earlier quoted context omitted.
Flutter on desktop has been "right around the corner" for about 5 years now.
I've been building in Flutter for desktop (macOS) for a year and a half. It's _still_ feeling early, but if you're comfortable writing a bit of native code, it pretty much just works (for single window applications — hopefully that changes soon).
Earlier quoted context omitted.
The most glaring is the ability to measure things (including text) in order to lay them out, rather than adding stuff to the tree and waiting a while for somebody else to lay them out in order to measure them. Followed closely by absolutely everything about the way overflow "works". After that I'd add the absolutely batshit insane hoops through which one still must jump to build any sort of text editing component wit…
> The most glaring is the ability to measure things (including text) in order to lay them out ... This has nothing with the DOM (or HTML or CSS for that matter). Yes, sometimes in desktop UI you will need to know exact element position/dimensions. That's why in Sciter I've added: 1. element.update(); method, it will force dimensions to be calculated at this moment. 2. element.onSize = function() {...} called when dim…
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…
Earlier quoted context omitted.
"Useful" as long as you don't care about battery life, memory usage, taking advantage of features of the host platform, or the native UI. As an end user why do I care about "openness"? If I pay a premium for my platform, why would I want second rate cross platform software?
> As an end user why do I care about "openness"? If I pay a premium for my platform, why would I want second rate cross platform software? Falsehoods HNers believe about how people buy/use software. Didn't stop Slack/Discord from become ubiquitous. "But native tho" just becomes a circlejerk. Talking about what users care about, most people don't know what native means nor if a given app is it. They don't know if Zoom…