Originally posted by Alex Sarmiento
View Post
1. is not childish is technically efficient, Mir is ubuntu specific for now and is under heavy development which make it very stupid to support it at this stage and a maintenance hell in the middle term[read and try to understand blog post].
2. KDE policy of non distro specific patch have more time than canonical in existance but somehow you assume martin created it out of his ass to troll ubuntu
3. KDE expressed it will support X11 and Wayland way before Mir was even an idea and they still do, so no problem here.
4. Qt5 have to support Mir before KDE even think about it and as far as i know there is only an lighthouse skeleton code and headers in an ubuntu bazaar repo somewhere but digia hasn't expressed any kind of Mir support up to date[at the very least it missed the Qt5.1 release and prolly Qt5.2].
i understand every wannabe smart ass that follow ubuntu religion think Mir will cure cancer and bring world peace or at very least make you feel you actually are a techie but Mir is very basic code right now with 0 support outside canonical scope[unity / "android drivers" libhubris is not from canonical] and is in fact very far behind in features to Wayland[could change in time], so until the protocol stabilize and Mir sees a first stable release forget about support outside canonical scope.
as an interesting note, if martin tomorrow decide to support Mir whatever it takes in kwin he will fail cuz Mir miss so many features right now that is technically impossible to make KDE/Kwin work with it[check their in code in the repo and you will understand why], their unity "next" demos are not the real thing but very basic render demos with fixed images and fake data to make it look pretty[is simpler that wayland demos but is better presented i give you that one]
About Performance:
1. Kwin is the most advanced compositor for X11 in existance hands down[tiled compositing, advanced shader support, color management, many features, Xrender fallback, GLes, EGL, Future GL3+ improvements]
2. Kwin sometimes suffer from being too far ahead cuz if you hit a render path bug/cpu fallback [nVidia is famous for those / FGLRX <-- total nightmare] it may require sometime to fix them at driver level
3. non-technical folks tend to blame kwin for it but almost 99% of the cases those slowdowns are driver faults[outdated in case of ubuntu unless you get them through PPA] or crappy patches in KDE [ubuntu have many slips here]
4. Best KDE experience come from Mesa drivers and distros like Slackware/Gentoo/Arch if you prefer binary distros OpenSuse/Debian unstable is very well maintained but ubuntu KDE is a luck thing maybe it works maybe is horrible
5. In Ubuntu sometimes is better to remove the whole kde-desktop packages and compile from sources and if you use blob drivers get an updated PPA for them[the same applies for Gnome 3]
Comment