Live data from Hacker News

DaedalOS – Desktop environment in the browser

dustinbrett.com

41–50 of 141 posts

Re: DaedalOS – Desktop environment in the browser

#41

I'm really thinking that's the feature. Compile Linux kernel to wasm. So it can run inside a browser with a very nice performance. Write FS drivers to enable seamless caching and remote data storage, so you can shutdown your system on PC and boot from laptop. Or even some kind of hibernate mode, so you can just continue from where you left off. Write graphics drivers using WebGPU and other technologies, enabling very…

Is that possible? I really need to get into wasm, seems it might be the best development option for years.

Re: DaedalOS – Desktop environment in the browser

#42

I'm really thinking that's the feature. Compile Linux kernel to wasm. So it can run inside a browser with a very nice performance. Write FS drivers to enable seamless caching and remote data storage, so you can shutdown your system on PC and boot from laptop. Or even some kind of hibernate mode, so you can just continue from where you left off. Write graphics drivers using WebGPU and other technologies, enabling very…

I'm looking forward to the day when I can run a browser in my browser.

Re: DaedalOS – Desktop environment in the browser

#44
post #42

I'm really thinking that's the feature. Compile Linux kernel to wasm. So it can run inside a browser with a very nice performance. Write FS drivers to enable seamless caching and remote data storage, so you can shutdown your system on PC and boot from laptop. Or even some kind of hibernate mode, so you can just continue from where you left off. Write graphics drivers using WebGPU and other technologies, enabling very…

I'm looking forward to the day when I can run a browser in my browser.

The point would be to run the browser directly on the hardware without any intervening useless layers like X-Windows or Wayland, then implement the desktop environment in that, and when you needed to pop up a browser window on the desktop (which you always need to do frequently), or an html app like you'd usually run in Electron, simply and efficiently use the same browser that's running the desktop environment, sandboxed the way all modern browsers now already implement their renderers isolated from their chrome ui frames.

No need to run the user's browsers separately inside a slower layer of emulation, when you already have a browser implementing the desktop.

Fewer layers and less bloaty software is better. We're already stuck with the browser, and it's not going away, so use it for everything. X-Windows and Wayland are obsolete and useless, so should be flushed.

Re: DaedalOS – Desktop environment in the browser

#47

I'm really thinking that's the feature. Compile Linux kernel to wasm. So it can run inside a browser with a very nice performance. Write FS drivers to enable seamless caching and remote data storage, so you can shutdown your system on PC and boot from laptop. Or even some kind of hibernate mode, so you can just continue from where you left off. Write graphics drivers using WebGPU and other technologies, enabling very…

You can already do this today!

Re: DaedalOS – Desktop environment in the browser

#48
post #42

Earlier quoted context omitted.

I'm looking forward to the day when I can run a browser in my browser.

The point would be to run the browser directly on the hardware without any intervening useless layers like X-Windows or Wayland, then implement the desktop environment in that, and when you needed to pop up a browser window on the desktop (which you always need to do frequently), or an html app like you'd usually run in Electron, simply and efficiently use the same browser that's running the desktop environment, sand…

I think ChromeOS Freon was close to what you're describing, but they ended up switching to Wayland at some point

Re: DaedalOS – Desktop environment in the browser

#49

This reminds me of Berlin/Fresco. https://berlin.sourceforge.net/ I followed this project for years and it's still where I think we should be. X11 architecture with higher level primitives

You know there's a very good reason that failed, as did every one of the numerous projects named X12 and Y-Windows, and why Wayland has taken so many years to continue to fail or even displace X-Windows.

None of them are dynamically extensible at runtime the way the browser is with JavaScript, or Emacs is with Lisp, or NeWS was with PostScript (which failed for economic reasons).

Why not simply use a standards based web browser running directly on the hardware to implement the desktop user interface and window manager and network distributed app platform (i.e. Electron), instead of trying and failing to reinvent X-Windows for the 100th time?

Post reply on HN