4 ms·
> Why can't I have a file in two places at once on my filesystem? You can! Use hardlinks. > Window Managers on traditional desktops are not context or content
by microcolonel 9y ago
> Why can't I have a file in two places at once on my filesystem?
You can! Use hardlinks.
> Window Managers on traditional desktops are not context or content aware, and they are not controlable by other programs.
There are well established standards for controlling window managers from programs, what on earth are you talking about?
> Applications would do their drawing by requesting a graphics surface from the compositor. When they finish their drawing and are ready to update they just send a message saying: please repaint me. In practice we'd probably have a few types of surfaces for 2d and 3d graphics, and possibly raw framebuffers. The important thing is that at the end of the day it is the compositor which controls what ends up on the real screen, and when. If one app goes crazy the compositor can throttle it's repaints to ensure the rest of the system stays live.
Just like Wayland!
> All applications become small modules that communicate through the message bus for everything. Everything. No more file system access. No hardware access. Everything is a message.
Just like flatpak!
> Smart copy and paste
This is entirely feasible with the current infrastructure.
> Could we actually build this? I suspect not. No one has done it because, quite honestly, there is no money in it. And without money there simply aren't enough resources to build it.
Some of this is already built, and most of it is entirely feasible with existing systems. It's probably not even that much work.