← Back to context

Comment by alightsoul

17 hours ago

With wasm, I see a future where the browser and thus web technologies are a UI toolkit for a Linux desktop environment. It already is, people hardly use GTK and qt anymore except for desktop environments or embedded like on cars due to performance limitations. It would be cursed to see a browser running within a browser. But then replacing a desktop environment might be the limit of replacing GTK qt and other UI toolkits with web technologies, making it unnecessary and opposite to the reason people use Linux which is performance

7 comments

alightsoul

Reply
thomashabets2  17 hours ago

I agree. Browser APIs don't have as much coverage as native APIs, but I would say that by far most UIs should be in the browser nowadays.

Quake can run in the browser, so in my opinion so can the likes of Photoshop. Maybe the latest AAA game is a different beast, but that's a tiny edge case.

Websites instead of apps on mobile is something that basically always sucks, but I don't see the same on desktop.

Just build your UIs in WASM already. :-)

> It would be cursed to see a browser running within a browser

It's been done.

  • necovek  16 hours ago

    > Websites instead of apps on mobile is something that basically always sucks

    I find it's the opposite: on my computer, I want native apps, but on the phone, it is very hard to manage a large collection of single use apps because I do not have a keyboard to quickly navigate between them.

    • pipe2devnull  13 hours ago

      If you are on an iPhone you can add a website to the Home Screen and it functions as a dedicated app essentially and the opened instance is treated separately from safari

      2 replies →