Originally posted by Ericg
View Post
More Mir Talking Points Come Out Of Canonical
Collapse
X
-
Originally posted by bwat47 View PostCanonical is just becoming a vampire at this point.
You managed to break the spell to find out the real thing.
Comment
-
-
Originally posted by bwat47 View PostCanonical has a great touch when it comes to UI's, but they don't really have a ton of programming expertise, and the wayland team is far more experienced in creating a display server than canonical's team.
Comment
-
-
Originally posted by finalzone View PostCanonical is a vampire from the beginning. Much like Dracula, the company successfully charmed majority of people to join the club then sneakily bite them.
I just retried Debian "stable" this morning, and it would hang on shutdown, take forever to boot up, and was in no way more stable or compelling than the much more bleeding-edge Ubuntu 12.04. Then there's the Arch-tards who suggest that Arch LInux somehow should be the dominant Linux distro, even though it's just a toy that is likely to fail to install, and even if it does install, it will pretty much break on every update. I still don't understand the alleged appeal of Arch, but I'm sure some knowledgeable Arch-tard can properly explain that the "I fixed it myself elitism" of Arch trumps Ubuntu's "just works for everybody".
Comment
-
-
And regarding ubuntu's laughable claim of having mir and unity-next in an LTS by "2014", let me remind you when in 2010 they commited to having unity on wayland "within a year"
Only they never did a lick of work on wayland, and never once have even contacted wayland developers, they just expected wayland to do all of the work for them apparently?
Comment
-
-
Originally posted by Figueiredo View Posti wonder what kind of video hardware accelation is planned on wayland/mir. the over reliance on community projects tends to lead to the current mess we have with vdpau/va-api/xvba. i hope someone is sensible enough to correct this, either on wayland or mir camp
I believe that now with OpenCL being more mature and widely used plus being available to FOSS drivers (r600g for example), the best method for the future would be to have software codecs ported to OpenCL. That way the hardware video acceleration would become universal, independent of special hardware or non-free software...
Comment
-
-
Originally posted by Figueiredo View Posti wonder what kind of video hardware accelation is planned on wayland/mir. the over reliance on community projects tends to lead to the current mess we have with vdpau/va-api/xvba. i hope someone is sensible enough to correct this, either on wayland or mir camp
Comment
-
-
Originally posted by pythonista View PostOr maybe it has something to do with the fact that Ubuntu generally "just works", and the other distros, even the "stable" distros generally look, feel, and act like somebody's hobby rather than a polished product? I'm sure Canonical has a lot more cred in making usable Linux distros than you do.
Comment
-
-
Originally posted by TemplarGR View PostThe same as we have now more or less. All APIs ported to Wayland... For the first couple of years...
I believe that now with OpenCL being more mature and widely used plus being available to FOSS drivers (r600g for example), the best method for the future would be to have software codecs ported to OpenCL. That way the hardware video acceleration would become universal, independent of special hardware or non-free software...
It makes sense that canonical also adopts the same API as android in order to leverage its driver stack, thus the display server should also support this API.
I don't know if any of the above has had any weight on the decision to develop mir, but one thing is true. Wayland is intel's project, and canonical is seeking to support a miriad of ARM SoCs, so it makes sense that they do not adopt a DS controlled by competitors. By developing it in house they can have a common ground. What do you guys think?
Comment
-
Comment