3 ms·

I think I'm misunderstanding your reasoning. To me, an app's feature set and its implementation details are unrelated topics. Whether your project came from an

I think I'm misunderstanding your reasoning. To me, an app's feature set and its implementation details are unrelated topics. Whether your project came from an app store, the web, a friend's USB stick, etc, is irrelevant to what it does. Ditto for the internal technologies it uses -- Qt, Electron, .NET, pure assembly, etc. I absolutely sympathize with webpages disabling search features and so on, but I'm not sure why exactly. Pointing to app implementation doesn't seem quite right, if that makes sense.

recursive 3y ago
I'm not talking about where it came from. All web apps use the "web platform". HTML, CSS, JS, DOM, and related technologies. Web apps are limited to behaviors that are possible using these technologies. As an example, you can't make a web app that controls display brightness.* It has everything to do with the fact that it's a web app. Web apps are built on web stuff, and web stuff provides no way to do it. So it is with keyboard events. * As far as I know, this is true. Maybe there's some new experimental spec or something? But you get the point.
- sublinear 3y ago
  Again, you can say the same about native apps and userland. It sounds like you just don't like the way the Web APIs have expanded in scope over the last 20 years or so. This is the better future. It used to be so much uglier in the era of flash, activex, etc. https://developer.mozilla.org/en-US/docs/Web/API https://developer.mozilla.org/en-US/docs/Web/API Oh and by the way the screen brightness probably can be adjusted using the USB APIs if someone bothered to port over drivers for the most common keyboards. At least all major browsers alert the user to choose if the web app can use these APIs unlike native apps.
  - recursive 3y ago
    It's the opposite criticism. Web APIs have expanded a lot. But still not as much as native. And probably never. Not sure what usb has to do with display brightness.

recursive 3y ago

I'm not talking about where it came from. All web apps use the "web platform". HTML, CSS, JS, DOM, and related technologies. Web apps are limited to behaviors that are possible using these technologies. As an example, you can't make a web app that controls display brightness.* It has everything to do with the fact that it's a web app. Web apps are built on web stuff, and web stuff provides no way to do it. So it is with keyboard events. * As far as I know, this is true. Maybe there's some new experimental spec or something? But you get the point.

sublinear 3y ago
Again, you can say the same about native apps and userland. It sounds like you just don't like the way the Web APIs have expanded in scope over the last 20 years or so. This is the better future. It used to be so much uglier in the era of flash, activex, etc. https://developer.mozilla.org/en-US/docs/Web/API https://developer.mozilla.org/en-US/docs/Web/API Oh and by the way the screen brightness probably can be adjusted using the USB APIs if someone bothered to port over drivers for the most common keyboards. At least all major browsers alert the user to choose if the web app can use these APIs unlike native apps.
- recursive 3y ago
  It's the opposite criticism. Web APIs have expanded a lot. But still not as much as native. And probably never. Not sure what usb has to do with display brightness.