hence the friction (unity vs shell etc)
i am pretty sure that if they had the money/manpower they would have created something of their own
KMS solved this. If it flickers in ubuntu, then they're not doing it right.... or you're using some horrid blob graphics driver. You should see the transitions in Fedora -- it FADES from plymouth into X.Quote:
2) No flicker in video, switching to login screen, user switching and so on.
Why would you want to change resolutions? Make the game scale better and leave it at your panel's native resolution.Quote:
3) No weird bugs when switching to and from full-screen apps in other resolutions then default (mostly games)
Doubt it. X really is NOT a CPU hog.Quote:
4) Less CPU usage / more battery life
REALLY doubt it. X already starts pretty fast, the majority of your boot time is loading the kernel and all your services.... oh, and that terrible blob at the front that sucks up 20-ish seconds... the... BIOS.Quote:
5) Faster system boot
So... when it fails you want it to just be completely unusable?Quote:
6) Never boot to console as failover - at least for major consumer graphic chips Intel, NV, AMD.
Because there's only two places you can go.... graphical environment, or text console. If the GE fails and you reject the console, you are forced into limbo where nothing will ever do anything at all, and you'll be forced to SSH in to the machine... assuming that the network is working. That sound like a good plan to you? Didn't think so...
GPL is what helps deal with monopolization (though doesn't necessarily prevent it -- see TiVo, though no longer a monopoly, which is why GPLv3 came about), not open source... because open source code can be distributed with an insane license like... you can look, but you can't touch.
Given a little creativity, I'm sure you can think of some way to build a monopoly based even on GPLv3 software.
A VESA failsafe mode might be possible, but any modern desktop environment will choke under such circumstances. It's not a technical problem, but rather something not really worth doing, as fixing X configuration and the such is ultimately done from a terminal, whether a vt or an xterm.Quote:
No, I am suggesting that Windows way of doing things (in this minor case of course) is correct: if driver/config is bad, use some default VGA mode and let user have access to GUI settings, Internet (to reinstall driver), etc.
I use E16 - and about 2s after pushing enter from startx (I boot to console) I have an Eterm loaded. E17 doesn't take much longer. So I don't think Wayland will be some magic bullet there.
I'm also sure that Wayland will grow somewhat as it's developed (important features added, those few-but-important use cases to take care, etc) so we'll see how it stacks up after some maturity. If I'm not mistaken, X has different core goals as well, so an apples-to-apples comparison may not even be possible.
So will we lose the ability to do:
If yes then I'd like to stick to xserver...
To clarify my position - I think Wayland is the future for linux, but linux still needs the console for handling problems with graphics.