Originally posted by Pallidus
View Post
Announcement
Collapse
No announcement yet.
Ubuntu Announces Mir, A X.Org/Wayland Replacement
Collapse
X
-
Originally posted by Pallidus View PostI blame this all on wayland and their snail pace development process
wayland = 5 years bs
mir = 9 months on the making, released in ubuntu 14.04
I hope Wayland team have had a jolt to get their project done and push it's implementation. I also want Mir a success as its goals are what I need.
Comment
-
5 threads and hundreds of posts...
... and not one directed at canonical's choices (single process wm-shell design, programming language, programming method, etc), rather bashing them for the decision itself
it strikes me odd somehow, especially after hearing about this "freedom" thing for a long time now... oh nevermind...
Originally posted by dee. View PostWayland is the right way to do things, and sometimes doing things right takes time. Mir is nothing but vaporware at this point.
but about the former who says Wayland is THE way?
with the most respect for wayland developers and their efforts, but to any problem in sw design, every individual developer may have a different solution and all may be equally valid
the fact that different developers may have different requirements or different approaches, know different languages (and here it's about a C++ monolithic shell+wm+graphic server vs a protocol and a C component for building compositors, with third parties tasked with the latter), follow different methodologies (and ehre it's about test driven development) or have different conceptions, is enough to set the respective solutions apart yet make them equally worthy
the mere fact that Mir is to be developed via TDD can make a HUGE difference development- and possibly functionality-wise, if applied correctly of course
because if applied correctly, it could mean more rapid development times (thus it may be actually possible for an Agiile developed integral solution to be delivered sooner)
because it would mean that the DS's behaviour is already formalized and apriori tested (with corner cases checked, and thus known to work correclty, apriori rather than as afterthought) the moment the code is released - thus Mir would be a formally verified desktop shell (afaik the first ever actually), thus suitable for environments where preverified code is practically mandatory (or the alternative is extensive and expensive auditing before deployment)
with Wayland, if i'm not mistaken, you dont get this - so this alone may make the whole wayland thing unsuitable for those who require, or strive for it
Originally posted by ninez View PostCanonical didn't even try to have any issues they may have had with Wayland addressed.
but if you have to solve a development problem and stumble upon a non viable solution (or one you deem as such anyway), do you bend to adopt it anyway (knowing and accepting you'll have to make compromises) or do you skip on it directly and implement yours without being restricted by others' choices?
if you do the latter, do you think you have to answer anyone about your decisions or not?
Comment
-
Wayland is kinda DOA if they don't have vendor support.
I'm surprised they didn't from the very beginning rope in AMD and NVIDIA and work with them to create a display server that would make their lives easier.
Then again it is an Intel project, so...
Comment
-
"Mir is nothing but vaporware at this point. "
here's the irony: do a search for wayland + vaporware and you will see how many people said the exact same thing about wayland.
here's where I'm coming from:
I hate xorg, tired of the stupidy that is setting up conf files to try different options and xorg needs to die, NAY, should have died already...
enter wayland
for 5 years nothing but promises and "oh it's going to be terrific" " oh it's so great"
bla bla fucking bla
I even remember seeing here and other places that ubuntu 12.04 would be using xwayland/weston what the fuck ever
12.04 didn't, then I heard the same about 12.10 that canonical was desperate to port ubuntu into wayland...
12.10 came and went and now it's 13.04... still no signs of wayland
this is a new fucking world where tech is moving fast, you can't take 5 years to make a gay display manager for fucks sake.
and now these stupid ass wayland devs act all surprised and offended that canonical said 'fuck this' and made their own...
wayland will be ready when 2015? let me fucking lol
it can be the biggest piece of shit ever made, but at least in little more than a years time canonical will release somethingLast edited by Pallidus; 06 March 2013, 12:22 PM.
Comment
-
Originally posted by Pallidus View PostI even remember seeing here and other places that ubuntu 12.04 would be using xwayland/weston what the fuck ever
12.04 didn't, then I heard the same about 12.10 that canonical was desperate to port ubuntu into wayland...
12.10 came and went and now it's 13.04... still no signs of wayland
Don't inverse cause and consequence.
Comment
-
Originally posted by Pallidus View Postthis is a new fucking world where tech is moving fast, you can't take 5 years to make a gay display manager for fucks sake.
Comment
-
Originally posted by johnc View PostWayland is kinda DOA if they don't have vendor support.
I'm surprised they didn't from the very beginning rope in AMD and NVIDIA and work with them to create a display server that would make their lives easier.
Then again it is an Intel project, so...
Comment
-
ok erendorn, using a bit of logic, tell me why that happened?
canonical is not afraid of buggy code so had wayland been anything but a pile of hype and promises I'm sure canonical would have either forked the shit out of it like they did with gnome, or end up using it.
seriously, use logic people:
why would canonical waste resources, time and money, making something if they could have just forked an existing solution?
I believe canonical lacks leadership, management, vision and a business plan but they would have to be text book retard to pull a move like this if wayland was anything but a piece of shit.
Comment
Comment