This is based on the Chromium Embedded Framework. I've always been surprised this kind of framework was not encouraged for Firefox by Mozilla (I've read they were even against it).
This is a pretty neat idea, and shows that maybe a desktop environment could be a lot more flexible than we're used to if it was based on something flexible. Not exactly counter intuitive.
I'd like to see how complex a CEF-based Wayland compositor would be in comparison.
How about using Godot instead of CEF? It has a pretty full-featured UI system.
While you're at it, go on a huge tangent writing a library that allows one implementation to work as both an X11 and Wayland compositor.
Actually why stop there? Make said library also compile to a full screen Windows and Macos application that somehow renders the contents of windows to textures and does event handing etc. that way you can write your desktop environment once and use it everywhere.
When I was younger I thought of replacing most of the OS with a browser since that is how I used it. but this is weird and not in a good way. Maybe using Firefox would feel better.
> It’s quite a bit easier to tweak CSS constants, and JS snippets then it is to change style embedded already in a long standing modern desktop/window manager. So let’s bring the web to the desktop and have a browser control the system.
Jesus, bro, you can’t say stuff like this here.
Half of HN is going to have a stroke and will end up sounding like Hodor – native, natuve, ntve.
This is based on the Chromium Embedded Framework. I've always been surprised this kind of framework was not encouraged for Firefox by Mozilla (I've read they were even against it).
This is a pretty neat idea, and shows that maybe a desktop environment could be a lot more flexible than we're used to if it was based on something flexible. Not exactly counter intuitive.
I'd like to see how complex a CEF-based Wayland compositor would be in comparison.
How about using Godot instead of CEF? It has a pretty full-featured UI system.
So many possibilities.
While you're at it, go on a huge tangent writing a library that allows one implementation to work as both an X11 and Wayland compositor.
Actually why stop there? Make said library also compile to a full screen Windows and Macos application that somehow renders the contents of windows to textures and does event handing etc. that way you can write your desktop environment once and use it everywhere.
I've gone crazy with power.
I'm interested in a how-to which accomplishes the absolute opposite result.
here you go
https://plan9.io/magic/man2html/4/webfs
1) uninstall Chrome
2) install it once a year when some backwards website won’t work with anything else.
3) go to 1)
When I was younger I thought of replacing most of the OS with a browser since that is how I used it. but this is weird and not in a good way. Maybe using Firefox would feel better.
I believe the earlier versions of Chrome/Chromium OS took this to the logical extreme.
https://www.technologyreview.com/2009/11/19/208062/google-gi...
> It’s quite a bit easier to tweak CSS constants, and JS snippets then it is to change style embedded already in a long standing modern desktop/window manager. So let’s bring the web to the desktop and have a browser control the system.
Jesus, bro, you can’t say stuff like this here.
Half of HN is going to have a stroke and will end up sounding like Hodor – native, natuve, ntve.
Pyro Desktop! But with Chrome instead of Firefox. https://arstechnica.com/information-technology/2007/07/exper... https://news.ycombinator.com/item?id=39541
Sounds like a more performant and cleaner solution than TFA.