Live data from Hacker News

DaedalOS – Desktop environment in the browser

dustinbrett.com

51–60 of 141 posts

Re: DaedalOS – Desktop environment in the browser

#53

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…

Linux can already run in the browser: https://bellard.org/jslinux/vm.html?url=alpine-x86.cfg&mem=1...

Re: DaedalOS – Desktop environment in the browser

#54

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.

Check https://bellard.org/jslinux/vm.html?url=alpine-x86.cfg&mem=1...

Re: DaedalOS – Desktop environment in the browser

#55
post #48

Earlier quoted context omitted.

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

Yet another step backwards.

Current desktop user interfaces are terrible, and we need the flexibility of a web browser to innovate and implement better ones, since Wayland is simply not up to it, because it's not extensible at runtime in JavaScript or any other language. (No, recompiling or dynamically linking in DLLs doesn't count -- that's just ActiveX.)

Re: DaedalOS – Desktop environment in the browser

#56

There's also https://www.windowmaker.org/ The website of a window manager impersonating the window manager.

I don't mean to be boring, but Emacs has had a window manager for years, EXWM. Oh, and a browser, EWW. If you want Inception-level recursion, a virtual LISP machine is your friend.

Re: DaedalOS – Desktop environment in the browser

#57

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 wonder what the venn diagram is between people that want this and those that buy a new laptop every few years. Because you can say goodbye to responsive IDEs, indexing and disk performance. And when you’re on spotty WiFi you have intermittent access.

Re: DaedalOS – Desktop environment in the browser

#58
post #48

Earlier quoted context omitted.

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

Yet another step backwards. Current desktop user interfaces are terrible, and we need the flexibility of a web browser to innovate and implement better ones, since Wayland is simply not up to it, because it's not extensible at runtime in JavaScript or any other language. (No, recompiling or dynamically linking in DLLs doesn't count -- that's just ActiveX.)

>because it's not extensible at runtime in JavaScript or any other language.

Nothing is stopping someone from making a wayland compositor that is.

Re: DaedalOS – Desktop environment in the browser

#59

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…

All too prescient: https://www.destroyallsoftware.com/talks/the-birth-and-death...

Re: DaedalOS – Desktop environment in the browser

#60

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…

Rather than the "easy" way of porting an x86 emulator to WASM, I've been trying to natively port the Linux kernel to WASM.

UML[0] and LKL[1] prove that running the kernel in a process is viable. μClinux efforts like NOMMU and binfmt_flat prove that you don't need memory-management nor ELF to run the kernel.

Both my own independent experiments and WALI[2] have shown it's possible to port the Linux syscall interface and userland ecosystem to WASM.

I'm confident it's doable, but there are a number of other challenges to solve along the way (like dynamic linking, the Harvard architecture, etc). Currently I'm blocked on the fact that while the kernel supports running non-ELF binaries, it really wants to be an ELF itself.

[0]: https://en.wikipedia.org/wiki/User-mode_Linux

[1]: https://github.com/lkl/linux

[2]: https://arxiv.org/abs/2312.03858

Post reply on HN