Earlier quoted context omitted.
It's just not the default. As the developer, it's trivial to make text selectable.
I meant it as an user.
WASM Wayland Web (WWW)
201–210 of 226 posts
Re: WASM Wayland Web (WWW)
#202Earlier quoted context omitted.
Flutter even had a DOM renderer which should in theory have fixed approximately all the issues (I don’t know for sure, I never knowingly encountered anything using it), but they’ve killed it off fairly recently, doubling down on the fundamentally unfixable direction that is the pure-canvas approach.
Yeah, the strategic direction of flutter feels like the famous "embrace, extend, extinguish" approach. All the big companies prefer walled gardens.
Re: WASM Wayland Web (WWW)
#203The absolute lack of professionalism among most web developers—many of whom are essentially glorified framework developers, barely understanding what they’re doing—is what led us here. This, combined with a complete disregard for web standards and the W3C (dismissed as too consensual, too European, and too slow of an approach), created the perfect shit-storm. Google insists on pushing its own "standards". And other b…
Not saying I like it, but I'm not surprised at the current state of the ecosystem.
All developers should understand basic web standards, particularly accessibility.
Re: WASM Wayland Web (WWW)
#204Earlier quoted context omitted.
> unable to select text Because of this alone I would not use.
It's just not the default. As the developer, it's trivial to make text selectable.
The only way you can get the proper behaviour for these things on the web is to use actual DOM text. Some parts of it could in theory be made possible, but I doubt that anything meaningful will ever change—it’s too antithetical to the nature of the web.
Re: WASM Wayland Web (WWW)
#205Earlier quoted context omitted.
I've never understood this "every program on my device should look like the same company designed it" mentality. Nothing against using the pre-built ui components provided by the OS, but looking down on a developer that decides to use something else? Just weird to me. A checkbox is a checkbox, it really doesn't matter whether App A's checkboxes look identical to App B. Now, if App A's checkboxes look different than A…
Having things look the same makes everything easier to use. I know exactly what's clickable and what happens when I click them, instead of having to figure it out each time. I don't understand why you'd be annoyed at different checkboxes within an app but not at different checkboxes between apps. Do you only ever use a single app? I constantly switch between many apps. More importantly, having things behave the same…
OS Widgets don't implement undo. Undo is inherently tied to app state and the developer is responsible for managing it. At most, the OS will give you an undo button/icon and you can use it to fit in visually.
Frankly, building a separate version of my app per platform to conform to your nativist standards is a huge waste of time. My UI will work across all target platforms. If you can't figure out interfaces that aren't straight out of an Apple/Microsoft design document, that's on you.
Re: WASM Wayland Web (WWW)
#206Earlier quoted context omitted.
It's just not the default. As the developer, it's trivial to make text selectable.
You can make text selectable, but it still won’t behave at all like normal text. Selection word boundary things won’t match the local platform behaviour, touch behaviour cannot possibly work properly, things like context menus won’t work properly, and more. The only way you can get the proper behaviour for these things on the web is to use actual DOM text. Some parts of it could in theory be made possible, but I doub…
Indeed, Flutter will never do everything "properly". But that's not its selling point. It doesn't need to, as long as the number of users reached from a multi-platform release outweighs the users lost because they were offended by a missing native feature. (Assuming you're not some massive company developing a parallel app for each platform)
Re: WASM Wayland Web (WWW)
#207> it seems likely there will soon only be 1 What have I missed, will Firefox adopt Webkit?
You've missed Firefox's marketshare inching towards irrelevance, its revenue - "charitable" donations from competitors worried about monopoly lawsuits that can stop at any time - in freefall, and more and more websites not working with anything other than Safari or Chrome.
Re: WASM Wayland Web (WWW)
#208Earlier quoted context omitted.
Ever heard about all those ChromeOS features that Safari is not supporting and how PWAs are a failure? How is that WebGL 2.0 experience going on iOS? Ever wondered why after a decade there is hardly any WebGL game that can match any serious game done with OpenGL ES.3.0 on mobile phones, starting with the famous Infinity Blade?
And this explains why Flash is dead? WebAssembly lives on. Embrace him. WebGPU will make you happier.
Re: WASM Wayland Web (WWW)
#209Earlier quoted context omitted.
Second try: Hi noduerme, I'm the guy who wrote the original 'Kaos'. I stumbled upon the discussion about it, and have no idea how to contact you besides commenting here... Any way I can message you?
Hi! I've temporarily put my email contact in my profile here...