Slashdot Mirror


Ubuntu's Mir Gets Delayed Again

jones_supa writes "Delays keep piling up for the Mir display server on the Ubuntu desktop. After already being postponed multiple times, Mir might not be enabled by default on the Ubuntu Linux desktop until the 16.04 LTS release — in two years time! This was the estimate by Mark Shuttleworth in a virtual Ubuntu Developer Summit. Using Mir, Mark says, will lead to supporting more hardware, obtaining better performance, and 'do some great things' with the technology. He expects some users will start using Mir on the desktop over the next year. Mir is already packaged as an experimental option, along with an experimental Unity 8 desktop session."

241 comments

  1. This could be good news... by bazmonkey · · Score: 4, Insightful

    If Wayland is able to make decent ground before Mir is ready, there's still hope Ubuntu will drop the whole thing.

    1. Re:This could be good news... by dbIII · · Score: 3, Insightful

      Why?
      I think we need both to compete. Some of the early limitations proposed in Wayland were frankly, utter shit, and it was only pressure to lift their game that led to them being dropped.

    2. Re:This could be good news... by Anonymous Coward · · Score: 1

      Why would that be a good thing?

    3. Re:This could be good news... by phantomfive · · Score: 1, Funny

      Then there are those of us who are hoping that Wayland will get dropped as well.......

      --
      "First they came for the slanderers and i said nothing."
    4. Re:This could be good news... by angryfeet · · Score: 4, Insightful

      But remember Wayland was floundering until just after Mir was announced. Only once all the righteous indignation kicked in did it start going anywhere. Without Shuttleworth we'd all be stuck in the 70's.

    5. Re:This could be good news... by Microlith · · Score: 2

      I think we need both to compete.

      Why? Given they both solve the same problem, but one has wide support and has shipped on devices, what use is the other?

      Some of the early limitations proposed in Wayland were frankly, utter shit, and it was only pressure to lift their game that led to them being dropped.

      Mir did not appear until way, way late in Wayland's game, and it appeared with a lot of terribly uninformed commentary from Canonical regarding how Wayland worked.

    6. Re:This could be good news... by Anonymous Coward · · Score: 0

      Oh, "we" need both now, do we? What have you done with dbIII? Nothing more than X has ever or will ever be needed, according to the real dbIII.

      > Some of the early limitations proposed in Wayland were frankly, utter shit

      And what limitations were those, impostor-dbIII?

    7. Re:This could be good news... by Anonymous Coward · · Score: 0

      Make Mir a cull?

    8. Re:This could be good news... by Anonymous Coward · · Score: 0

      I think we need both to compete.

      I'm not so sure. No company acquires money directly from open source code. So it would be everyone's benefit in the OSS ecosystem (be it service sellers, HW makers or just hackers) to have one solid component than two broken ones. Because then we could concentrate resources on one display server and make it stronger. Especially when Mir and Wayland both do the same thing anyway.

    9. Re:This could be good news... by Alomex · · Score: 1, Flamebait

      And you would be wrong. No commercial implementation of Unix uses X (NextStep, OSX, Android) and even Sun back in the day tried its own alternative (SunNews). Every single person who has gone deep into the bowels of the X beast says it sucks, including the X.org people.

      But a few X fanbois think they know better 'cuz hmm erh.... network transparency!

    10. Re:This could be good news... by davydagger · · Score: 4, Insightful

      ubuntu didn't adopt wayland because they said it lacked too much functionality, so instead of contributing back, like most other companies do, they decided to do what they normally, do, make an incompatible, inhouse version only they use, and then blame everyone else for not marching around them.

      I liked ubuntu early on, because when it was X11 and Gnome 2, they made using linux easy, with using the exact same technologies everyone else running a linux desktop was using. They were using the most mainstream widely supported technologies.

      And thats all I want out of a newbie distro. To take wideley supported, most default software, package it together, with support, make the best sane configs. Find the best GUI config tools, and make a coherent OS family like windows and mac do, for everyone who is non-technical, so they can enjoy what we do, and I have something to recommend to non-techies.

      It would also make my life easier, being I'm the one who generally fixes the computer.

    11. Re:This could be good news... by phantomfive · · Score: 1

      No commercial implementation of Unix uses X (NextStep, OSX, Android) and even Sun back in the day tried its own alternative (SunNews).

      Commercial implementations of Unix suck as a rule, HPUX, AUX, AIX..........so you saying, "X isn't as good because some company chose Y" isn't a valid argument.

      Give me BSD or Linux over any of those.

      --
      "First they came for the slanderers and i said nothing."
    12. Re:This could be good news... by epyT-R · · Score: 1

      Why should we emulate any of those just because they're commercialized?

    13. Re:This could be good news... by invictusvoyd · · Score: 1

      What's the real need for wayland? Does it justify the effort?

    14. Re:This could be good news... by Alomex · · Score: 1

      ... and X.org is commercialized how?

      The one thing they have in common is that they all looked deep into the bowels of the beast and they all rejected. The commercialization thing is a red herring and you know it.

    15. Re:This could be good news... by jones_supa · · Score: 3, Informative

      Much better performance, no tearing problems, smooth compositing and desktop effects, old legacy X11 crap thrown away.

    16. Re:This could be good news... by marcello_dl · · Score: 1

      More precisely, I wish the transition will not fragment the system between a lot of still potentially useful apps that cease working and the new stuff that will take years to mature to the point of old apps. Think about the transition between kde 3 and 4, or end up like people running classic unix apps under OSX.

      Network transparency is a MUST to me, but if it is important for many it should end up getting implemented into any solution eventually.

      --
      ---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
    17. Re:This could be good news... by Anonymous Coward · · Score: 0

      Much better performance: Nonsense. The Wayland architecture is basically the same as X. A message protocol over a UNIX domain socket + some efficient buffer sharing.

      smooth compositing and desktop effects: Can be done with X11 as well (missing improvements seem to come with DRI3 and the present extension)

      old legacy X11 crap thrown away: Other words for: Breaks backwards compatibility.

    18. Re:This could be good news... by dbIII · · Score: 1

      For one thing the initial linux only limitation. If you can't find any more that have been dealt with then you haven't been followign this topic.

    19. Re:This could be good news... by bill_mcgonigle · · Score: 1

      But a few X fanbois think they know better 'cuz hmm erh.... network transparency!

      One way or the other, networked Wayland will get figured out - I don't need X primitives across the wire, I just need to run an app. This can be figured achieved.

      I'm more concerned that security is an afterthought in Wayland, and it'll get bolted on at some point. X's security is enough to make an auditor's skin crawl and Wayland isn't (yet) any better.

      Maybe Wayland will forever be a development idea and somebody will fork it to address practical concerns. It might not even be too early for a fork - for as long as large numbers of people have been expressing concerns about both issues, we (meaning I, casually) haven't heard any recognition from the project that those are important issues and design work is taking those needs into consideration.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    20. Re:This could be good news... by dbIII · · Score: 1

      Considering that to a great extent it is ego driven (not a bad thing in this case), there does need to be something else to raise the bar.
      Consider the breakup of the Internet Explorer team when it was considered to be "good enough" as an example. By current standards IE way back then was of extremely low quality but there was not seen to be any viable competition.

    21. Re:This could be good news... by Anonymous Coward · · Score: 0

      Apparently, Apple succeded with the Mac OS X. At least, that is what I am told as I have not tried it for myself. Sales do back that statement.

    22. Re:This could be good news... by Chrisq · · Score: 1

      But remember Wayland was floundering until just after Mir was announced. Only once all the righteous indignation kicked in did it start going anywhere. Without Shuttleworth we'd all be stuck in the 70's.

      I was going to say the same thing. without competition Wayland would have moved very slowly, if at all.

    23. Re:This could be good news... by dbIII · · Score: 1

      network transparency

      Which is of course why X gets used where it is used in the first place. Wrap your head around X being used on MS Windows guys - once you work out why it is used there you'll stop laughing at network transparency and see why people are using it.

    24. Re:This could be good news... by Alomex · · Score: 4, Interesting

      Commercial implementations of Unix suck as a rule,

      Wrong. OSX doesn't suck, Solaris didn't suck in its time, Android doesn't suck and even your much beloved Linux didn't get to be a real serious operating system until IBM decided to adopt it and spent massive amounts of money bringing it up to enterprise quality.

    25. Re:This could be good news... by Alomex · · Score: 5, Insightful

      Except that most people don't use X network transparency. You can achieve the same effect without it, and this is what most people do, but they don't even know it. They see a remote client and immediately think "it must be network transparency!" If that were the case then surely windows is network transparent since it supports remote desktop.

      As I said, network transparency is the mating call of the X noob.

      Yes, it is a flamebait-ish statement, but it also happens to be the truth.

    26. Re:This could be good news... by Anonymous Coward · · Score: 1

      Except that most people don't use X network transparency.

      Most people don't use anything they can't get with an iPad.

    27. Re:This could be good news... by Anonymous Coward · · Score: 0

      The Wayland developers have already said that Wayland over the network will be something like VNC - i.e. the network transparancy of Windows 95.

      I've used Windows 95 remotely via VNC back in the days, and it sucked. Sending bitmaps, rather than "draw rectangle here" is simply too slow. And Wayland is all about bitmaps (aka. textures).

      And yes, sending bitmaps is still too slow. I have a solitaire game I wrote using SDL, that I keep planning to rewrite using XLib, because SDL also does the bitmap thing. Rewriting it using XLib may make it slower to start up (all 52 card images need to be sent to the server once), but after that, it will be "draw ace of spades here", rather than "draw black pixel here", making it perform a lot better remotely.

    28. Re:This could be good news... by Anonymous Coward · · Score: 5, Informative

      network transparency

      Which is of course why X gets used where it is used in the first place. Wrap your head around X being used on MS Windows guys - once you work out why it is used there you'll stop laughing at network transparency and see why people are using it.

      X is only network transparent if all your apps are from 1995 and are written against Motif. Everything newer than that is not network transparent, it's just shoving uncompressed bitmaps across the network in a highly inefficient wrapper protocol that makes large numbers of inefficient, lag inducing round-trips.

      A rootless VNC-esque protocol (Xpra) is a superior solution in every way.

    29. Re:This could be good news... by Anonymous Coward · · Score: 1

      Linux-only limitation was *never* proposed for Wayland, and Mir has done nothing to change that anyway.

      Wayland is a display server protocol, remember?

      Upstream *Weston* developers are primarily concerned with Linux support, because that is what they choose and/or get paid to do. There is nothing preventing someone from porting it or implementing their own Wayland compositor for their favourite operating system. There never has been. Wayland has always been released under the liberal MIT license, and the Weston compositor has switched to MIT as well.

      > If you can't find any more that have been dealt with then you haven't been followign this topic.

      That's pretty rich, coming from you. You are the nitwit who keeps posting FUD, remember? No, please enlighten us all about the rest of these limitations are. Limitations which you have not completely dreamed up from nothing, would be nice.

    30. Re:This could be good news... by Anonymous Coward · · Score: 0

      So, uh, AIX, HPUX, Solaris etc aren't commercial implementations of Unix now? X has been the standard UI of commercial Unix for decades now, which is why Sun swapped from NeWS to it. Nextstep and its successor MacOS X were outliers, and Android is an embedded OS where the rules have always been different.

    31. Re:This could be good news... by udippel · · Score: 1

      X is only network transparent if all your apps are from 1995 and are written against Motif. Everything newer than that is not network transparent, it's just shoving uncompressed bitmaps across the network in a highly inefficient wrapper protocol that makes large numbers of inefficient, lag inducing round-trips.

      Ooops, this is good for an AC, but bad for the mod who modded up an AC with some unsound feelings.

    32. Re:This could be good news... by Niznaika · · Score: 2

      And then there's this: http://www.openbsdfoundation.o...

    33. Re:This could be good news... by Uecker · · Score: 1

      The shoving uncompressed bitmaps is not really the problem. The round trips come from stupid things like creating a lot of atoms in a synchronous way using xlib. This is not a problem with the X protocol and can be avoided using XCB. There was some momentum to get this fixed, before Linux development was re-focussed for the mobile market (just look who funds what and why). Don't be fooled this is not about your desktop. This is especially not about the traditional UNIX desktop which will simply be discarded along the way because it is not of significant commercial interest to anyone. From my perspective, Wayland and MIR are a both disaster, because I fear that it will set us back a decade by breaking compatibility with diffiicult to re-create special applications coded against POSIX and X.

      The best outcome now would be a split of the Linux community with one part concentrating on a X11/UNIX desktop and API stability. All other players are then free to continue to create incompatible systems to fulfill their mobile ambitions without hurting the ones which would like to have a stabile UNIX-like system.

      PS: xpra is nice, that it breaks the on-the-wire protocol is a big mistake.

    34. Re:This could be good news... by Anonymous Coward · · Score: 0

      Because we all know network transparency is indispensable for a solitaire game...

    35. Re:This could be good news... by udippel · · Score: 1

      Much better performance, no tearing problems, smooth compositing and desktop effects, old legacy X11 crap thrown away.

      Are you repeating here what you read up elsewhere, or have you actually suffered from those? Here, none of that has been visible for the last 5 years. On 'normal' desktop applications, I should add. Okay, maybe some tearing, at times, without Vsync. But is this really worthwhile all the fuss? To me not.

    36. Re:This could be good news... by DrXym · · Score: 2
      Wayland will still be experimental in Fedora 21 and turned on in 22. That means it will have possibly 12 months on Mr but it's still away from any sort of widespread use.

      I don't see Mir as being in much competition though. Canonical have hobbled interest in it due to the restrictive licence and contributors agreement and most people regard it as divisive. I will be interested to see what the gubuntu dist do when GNOME shell is fully Wayland compatible - whether they intend to use it or if they will be constrained by Canonical and leave GNOME using X until they can port it to Mir.

    37. Re:This could be good news... by Anonymous Coward · · Score: 0

      Herp Derp much?

    38. Re:This could be good news... by Electricity+Likes+Me · · Score: 2

      Conversely Microsoft's RDP implementation is pretty much a top of its game remote desktop system.

      Look the reality here is VNC sucked because we don't have fast compression libraries to use with it. That's changed - a lot. We're in an age where mobile devices have H.264 ASICs, and TigerVNC/TurboVNC exist.

      What we're desperately lacking is a desktop UI which lets us seamlessly bring those components together - I want to be able to teleport my app windows across to other desktops and bring them back locally, or send them to other machines. X can't do that - not remotely efficiently.

    39. Re:This could be good news... by Lumpy · · Score: 1, Troll

      In it's time? Solaris is still available and WIDELY USED in industrial and scientific worlds.

      Where are you getting your Unix information because it seems to be pretty messed up.

      --
      Do not look at laser with remaining good eye.
    40. Re:This could be good news... by DrXym · · Score: 1

      And Mir is for Linux too. What's your point? The Linux kernel just happens to provide the event and display hooks that these display server layers need to work efficiently. I'm quite certain that this would not stop Wayland being ported to other kernels or environments should there be reason to. Or just use X. Big deal.

    41. Re:This could be good news... by DrXym · · Score: 1

      It's hard to see why anybody with an interest in Linux would hope it be dropped.

    42. Re:This could be good news... by Lumpy · · Score: 1

      Desktop_effects... those are highly important to getting work done.

      This is the problem nothing is being done for real performance... it's all for glitter and oooh shiny.

      --
      Do not look at laser with remaining good eye.
    43. Re:This could be good news... by RDW · · Score: 2

      And thats all I want out of a newbie distro. To take wideley supported, most default software, package it together, with support, make the best sane configs. Find the best GUI config tools, and make a coherent OS family like windows and mac do, for everyone who is non-technical, so they can enjoy what we do, and I have something to recommend to non-techies.

      Welcome to Mint!

    44. Re:This could be good news... by Anonymous Coward · · Score: 0

      Much better performance

      Any actual real world data (read: benchmarks that show a practically useful improvement) to back that up ? Also, Wayland removes support for 2D acceleration, and existing X applications would have to use an emulation layer, that is, running an instance of X on top of Wayland.

      no tearing problems

      Can be fixed without replacing X, and is a minor issue anyway.

      smooth compositing and desktop effects

      These are generally among the first things I disable when installing a Linux distribution. The fewer useless and performance/reliability crippling gimmicks there are enabled, the better it is for practical usability.

      old legacy X11 crap thrown away.

      In other words: no backward compatibility with existing software. Well, one can always just run the Windows version with Wine (I already do it sometimes, since it can be easier than solving Linux dependency mess). Or just wipe Linux and use Windows instead, where one can actually expect applications to work out of the box, even after a long time.

    45. Re:This could be good news... by Anonymous Coward · · Score: 0

      What's the real need for wayland? Does it justify the effort?

      It does not, but when did that stop FOSS developers from reinventing the wheel and replacing things that work, due to politics, NIH syndrome, egoism, or whatever other stupid reason ? It will result in a few years of mess with bugs and broken applications, and then everything will work more or less like before with X. Fortunately, one can easily avoid the PITA by doing what 95% of other PC users do, and just switch to Windows.

    46. Re:This could be good news... by jones_supa · · Score: 2

      Much better performance

      Any actual real world data (read: benchmarks that show a practically useful improvement) to back that up ? Also, Wayland removes support for 2D acceleration, and existing X applications would have to use an emulation layer, that is, running an instance of X on top of Wayland.

      I do not have. I base that only on what I have heard.

      no tearing problems

      Can be fixed without replacing X, and is a minor issue anyway.

      Not a minor issue at all. Of default Linux installations, only Compiz-based ones can reliably prevent tearing. Mutter tears slightly, but it can be fixed with some configuration. XFCE tears because the default compositor uses XRender (the default compositor can be replaced with Compton to fix the issue). KDE tears by default on some systems unless "full screen repaints" is selected. LXDE does not ship with a compositor and all so it tears greatly. So tearing can be avoided with careful setup with X.org too, but it is not something that "just works". Not a minor issue as you say.

      smooth compositing and desktop effects

      These are generally among the first things I disable when installing a Linux distribution. The fewer useless and performance/reliability crippling gimmicks there are enabled, the better it is for practical usability.

      A little bit of glitter does not hamper usability. It's nice to have zoom animations for window minimize/restore, and a fade out effect for menus. Those run reliably and smoothly on Windows 7/8 even on low end hardware. Put a Linux desktop on a low-end Atom/Bobcat system and the same effects are choppy and take more system resources.

      old legacy X11 crap thrown away.

      In other words: no backward compatibility with existing software. Well, one can always just run the Windows version with Wine (I already do it sometimes, since it can be easier than solving Linux dependency mess). Or just wipe Linux and use Windows instead, where one can actually expect applications to work out of the box, even after a long time.

      That is certainly true, but after the transition phase, I believe we can adapt most open source software to be Wayland-compatible.

    47. Re:This could be good news... by thegarbz · · Score: 4, Informative

      If you think that he's wrong maybe you should look at how any modern X system works. Both X developers and Wayland developers have discussed in detail that there is nothing network transparent about any modern release of X which does any kind of direct rendering or hardware acceleration, something that was introduced around the mid 90s, so the parent's comment is actually right on the mark.

    48. Re:This could be good news... by Bengie · · Score: 1

      Mir is being designed by people who don't fully understand the problem domain or now Wayland works. The lead "devs" of Mir have spouted a lot of factually wrong information based on misunderstandings. I don't know about you, but I don't think it's a good idea to have programmers who don't understand what they're trying to accomplish.

    49. Re:This could be good news... by SkunkPussy · · Score: 1

      Network transparency was conspicuous by its absence for a long time.

      --
      SURELY NOT!!!!!
    50. Re:This could be good news... by Anonymous Coward · · Score: 2, Insightful

      Why? Given they both solve the same problem, but one has wide support and has shipped on devices, what use is the other?

      If this is true then why even have Wayland? It solves pretty much the same problems that X had already solved. We could have simply modified X.

      If Wayland is justified then so is Mir.

    51. Re:This could be good news... by Bengie · · Score: 2

      X developers and Wayland developers

      /agree

      Synonymous terms. X devs are the ones making Wayland. I find it funny and kind of sad that so many people think X is somehow better when it's made by the same people. If those people don't like Wayland, they are free to fork X and maintain it themselves. From what I hear, it is an absolute mess because if has so many conflicting features.

    52. Re:This could be good news... by Bengie · · Score: 3, Informative

      Wayland is a simple abstract layer. You can make your own remote protocol and have receive your draw commands and render it locally. One can fully implement X in Wayland, but one cannot implement Wayland in X. Therefore, Wayland is better. If you need X like functionality, someone could easily create a wrapper, which they already have for X.

    53. Re:This could be good news... by squiggleslash · · Score: 1

      It's hard to see why anyone with an interest in Linux would want us to move away from X11 to an unstable untried display system that will be missing features by design, simply because some X11 developers feel that the core X.org server has a lot of cruft in it.

      Wayland will look elegant to those programmers until the day they start adding the missing features. It'll be far more crufty and inefficient than X.org long before it ends up being feature complete. That's how programming works.

      --
      You are not alone. This is not normal. None of this is normal.
    54. Re:This could be good news... by Bengie · · Score: 2

      Wayland is magnitudes faster. Wayland's protocol just tells the compositor where a memory buffer is and what to do with it, unlike X, which has to sends thousands of draw primitives. It's like comparing Java to C and claiming they're the same because they both use an equal sign for assignment.

    55. Re:This could be good news... by Bengie · · Score: 2

      If you're trying to sell a device that appeals to 80% of people, you best make it look pretty, otherwise they're just going to use iOS. Anyway, your argument is no different than me saying fun and games are all pointless, people should spend their entire life working, then immediately die when they are no longer useful. Life isn't just about getting work done, it's also about the pretty and fun.

    56. Re:This could be good news... by Dcnjoe60 · · Score: 0

      Why? Given they both solve the same problem, but one has wide support and has shipped on devices, what use is the other?

      If this is true then why even have Wayland? It solves pretty much the same problems that X had already solved. We could have simply modified X.

      If Wayland is justified then so is Mir.

      Hell, if that's the approach you want to take, why even have a computer? It solves pretty much the same problems that pencil and paper had already solved. Why have pencil and paper? It pretty much solves the same problems cuniform tablets had already solved.

      I assume you really can see the difference between a new display server and antiquated X, but maybe not. I'll chalk it up to the state of the school system in today's world. Oh, wait, why even bother having a school system? It solves pretty much the same problems that the guild system did.

    57. Re:This could be good news... by Bengie · · Score: 1

      Can be fixed without replacing X, and is a minor issue anyway.

      You lie or are ignorant. Several of the lead devs of X have stated that tearing in X cannot be fixed without completely breaking the protocol. They've been trying to fix this issue since '95. Your basic understanding of this simple concept makes everything you say questionable.

    58. Re:This could be good news... by Dcnjoe60 · · Score: 1

      Why?
      I think we need both to compete. Some of the early limitations proposed in Wayland were frankly, utter shit, and it was only pressure to lift their game that led to them being dropped.

      People seem happy that the upstart/systemd decision has been made. I imagine they will be happy when the Wayland/Mir decision is, too. We don't need both to compete, we already have X for that.

    59. Re:This could be good news... by Anonymous Coward · · Score: 0

      There are a whole set of new users who would probably never need the network transparency and would benefit more from having Wayland. OS X doesn't use X windows natively, yet X is still there when I need it. I don't see Wayland from being any different in this respect. Having said that the only thing I can remotely window with X are the current Unix programs and I can only RDP OS X programs. I see the same thing happening with Wayland. Eventually nothing will support X without at least a recompile or worse not at all.

      Supposedly RDP has a seamless windows mode that allows me to only remote a single application to my remote desktop. I haven't used RDP for this because as far as I know rdesktop doesn't support this mode and the add-on that adds this functionality does not work with Windows 7 or 8 and as far as I can tell only Windows programs support this mode anyway. While X supports seamless mode transparently. I can have X programs from multiple servers on the same desktop without any compatibility issues.

      As I said, network transparency is the mating call of the X noob.

      I think you have that backwards. Some of us have been using X since before a lot of the Wayland proponents were born. They never saw the need for network transparency and see it as a poor excuse for keeping X around. It's the old timers who don't like change.

    60. Re:This could be good news... by Bill_the_Engineer · · Score: 1

      X is only network transparent if all your apps are from 1995 and are written against Motif. Everything newer than that is not network transparent, it's just shoving uncompressed bitmaps across the network in a highly inefficient wrapper protocol that makes large numbers of inefficient, lag inducing round-trips.

      This is why I use NX. It solved that problem for me and I've been using X over a crappy VPN for years without the pain of plain X.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    61. Re:This could be good news... by squiggleslash · · Score: 2, Informative

      That's complete claptrap. Yes, very recent (last 5-10 years) widget toolkits have started to force use of features that result in bitmaps being sent across the network, but that's hardly a reason to throw out X. And it's essentially a lie to pretend it means, somehow, that X11 doesn't have network transparency.

      I find it pretty bad, to be honest, that the same devs who are protesting that X11's network transparency isn't what it could be are:

      1. The devs that did this in the first place, refusing to advance the protocol to include the features that GTK3 et al required.
      2. Apparently think the solution is getting rid of network transparency altogether.

      I'm staggered, to be honest, by the whole thing. I appreciate old code is sometimes awkward to support, but the solution isn't a wholesale replacement of the project. Mozilla's developers may have made many mistakes in their decision to throw out the Netscape code that delayed the release of a great browser for many years, but they were NEVER, NEVER so stupid as to say "Well, we looked at the Netscape source code, and we think the solution is to get rid of HTML. It's too kludgy! I mean, just look at it, it's impossible to add features to it cleanly!"

      If we were talking about a rewrite of X.org, nee XFree86.org, nee X86, that'd be one thing. It's probably necessary by now although I'd still say they need to seriously think in terms of refactoring the project. But throwing out the entire protocol because they refused to add the features necessary to make the protocol efficient? Fuck that.

      --
      You are not alone. This is not normal. None of this is normal.
    62. Re:This could be good news... by dbIII · · Score: 0

      X devs are the ones making Wayland

      Funny how when I questioned that last time the "proof" was a bit of XFree86 code from the 1990s cut and pasted into Wayland by someone other than the author of that earlier code. After that was seen through - silence.

      I'm sick of shit from weird fanboys that have never even tried out the thing they are raving about and know very little about the thing they expect it to replace.

    63. Re:This could be good news... by Ash+Vince · · Score: 1

      Network transparency is a MUST to me, but if it is important for many it should end up getting implemented into any solution eventually.

      I am curious as to why?

      I have seen the amazingly cool things X can do when someone showed them to me a decade or so back, but it has never once been useful to me in the real world.

      When I admin a linux server I do everything on the command line via ssh. This is the whole strength of Linux in that you can do everything without needing a GUI. What I have needed far more is the responsiveness that direct display writes from app to hardware give me when running stuff locally.

      I never seem to have a need to run a GUI on a remove machine but I use them on my local machine every day so it makes perfect sense to make fast local performance a priority at the expense of remote GUI performance that is not used as often.

      --
      I dont read /. to RTFA, I read /. to offend people in ignorance.
    64. Re:This could be good news... by Wootery · · Score: 1

      Or just use X. Big deal.

      Practically speaking, yes, X would probably be a perfectly workable fallback, but it's still a problem if X's 'replacements' don't have good portability.

    65. Re:This could be good news... by dbIII · · Score: 1

      I wish you people would actually learn about your pet topic before jumping in.

    66. Re:This could be good news... by dbIII · · Score: 1

      Using it now.

    67. Re:This could be good news... by Bill_the_Engineer · · Score: 3, Insightful

      Your response is a combination of reductio ad absurdum:

      Hell, if that's the approach you want to take, why even have a computer? It solves pretty much the same problems that pencil and paper had already solved. Why have pencil and paper? It pretty much solves the same problems cuniform tablets had already solved.

      and ad hominem:

      I assume you really can see the difference between a new display server and antiquated X, but maybe not. I'll chalk it up to the state of the school system in today's world.

      It's very weak and emotional filled response. It makes me think you more of a Wayland fanboi who can't handle the competition than someone who has anything important to add to the conversation.

      While I do think it's detracts from the efforts being made by Wayland, I don't see anything wrong with Mir's existence. We always said competition is good. We said this when Linux went against Windows, to justify the multiple desktops available (e.g. Gnome, Qt, XFCE, OpenStep, etc.) and I can see the same argument said for Mir versus Wayland.

      Wayland is competing against X windows. They are offering the promise of improved performance and maintainability by jettisoning the legacy code of X. I don't see Mir any differently. I see what the AC is going for and agree. Wayland may have some of the same programmers of X, but that doesn't necessarily mean X is abandonware.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    68. Re:This could be good news... by Anonymous Coward · · Score: 0

      >h.264
      Lol. 1) Slow as balls to encode. 2) lossy

      https://www.xpra.org/

    69. Re:This could be good news... by Anonymous Coward · · Score: 0

      I run xming on windows specifically to run remote unix matlab sessions (via putty). The unix machine has access to a cluster and is 64b. My desktop is still running 32b matlab and can't deal with some data. Please, enlighten me as to how this is not network transparency.

    70. Re:This could be good news... by VortexCortex · · Score: 1

      X is only network transparent if all your apps are from 1995 and are written against Motif.

      You're a fucking idiot. I was playing an OpenGL game over X from across the network. It was rendering beautifully and responsive... except the audio was coming from the other room where all the game code was running.

    71. Re:This could be good news... by Anonymous Coward · · Score: 0

      > I'm sick of shit from weird fanboys that have never even tried out the thing they are raving about and know very little about the thing they expect it to replace.

      What the fuck does it have to do with you what other developers do with their free time?

    72. Re:This could be good news... by DrXym · · Score: 2
      Well that's a pretty weak argument.

      Linux has always featured choice. Personally I dislike KDE and I am critical of it but I'm not required to use it so I don't. Nor are you required to use Wayland. Stick with X for as long as you like. Gather a core of likeminded people and produce a dist that suits your requirements. I'm sure Amish Linux will be a huge hit.

      And every software is "unstable untried" until it is. I'm quite certain Wayland will have bugs in it and will fail to function in certain configurations. And those bugs will be fixed, either in Wayland itself or in the code it depends on, e.g. Mesa or display drivers. If it bothers you, don't use it until the bugs are fixed.

      And what "missing features" are you talking about? Part of X's problem is it is a veritable kitchen sink of features, most of which are obsolete, inefficient or an impediment to be worked around. And that's the point - Wayland is not attempting to reimplement everything in X. I also hope you're not going to say remoting because that's the compositor's job, not Wayland's and there is a reference remoting implementation in Weston that uses RDP.

      And just "some X11 developers"? The most prominent supporters of Wayland are major X11 developers who know how broken X is. Name any prominent X11 developer who is in favour of maintaining the status quo, who thinks X is perfect in its present form or can be fixed without breaking backwards compatibility or without making a complex tangle of obsolete code and extensions even more complex.

    73. Re:This could be good news... by DrXym · · Score: 1
      I don't see how portability is any better or worse for using Wayland than X. If I were to target a new graphics card or kernel with X then I'd have to port the code to that platform, e.g. write a new backend. X may be more accustomed to doing this but the work still has to be done. Why is this not the same for Wayland?

      It may be that Wayland / Weston targets Linux in the first instance (just as Linux kernel originally targeted x86 processors) but that does not preclude it from other kernels over time. If someone were to try I suspect the problem would lie less in porting Wayland / Weston and more to do with the sorry state of GPU drivers for other kernels. In the meantime, use X. I doubt it's going away any time soon.

    74. Re:This could be good news... by DrXym · · Score: 1

      So enlighten us where I have gone wrong please. And for someone quick to call it "your pet topic", you sure as hell have quite the posting history about it yourself. It's called projection you know.

    75. Re:This could be good news... by DuckDodgers · · Score: 2

      Agreed. Wayland development appeared to accelerate after Ubuntu announced Mir. If the only thing that ever happens because of Mir is that it made the rest of the Linux community unite behind Wayland and speed its adoption, that's still a good thing.

      And Ubuntu started Mir because their engineers seem to believe Mir has fundamental performance advantages over Wayland in resource-constrained environments like phones. It's possible they're completely wrong, but if they're right then we need Mir for Linux on smart phones.

    76. Re:This could be good news... by Bacon+Bits · · Score: 2

      Of course it's still widely used. Windows 2000 is still widely used, too. That doesn't mean both are not past their prime.

      Certainly people use Illumos, too, but since Oracle acquired Sun and all but killed Solaris by making it closed source (or limited access source) and eliminating support for OpenSolaris, there is virtually no redeeming quality to the OS over any other flavor of Unix or Linux (ZFS is all that occurs to me) particularly when Oracle Linux exists. Oracle has a horribly infamous reputation as an ISV -- I think only SCO (now TSC) has a worse reputation -- and choosing to go with them as a vendor seems awfully risky given how they've treated the other Sun assets. I'd be much more comfortable support-wise with a Windows Server system running SQL Server instead of Oracle Solaris running Database.

      --
      The road to tyranny has always been paved with claims of necessity.
    77. Re:This could be good news... by knarf · · Score: 1

      It is not so much that commercial unixes sucked, more that they were encumbered with so many restrictions and limitations that it got plain annoying and hard to use them. From missing tools and compilers to forced kernel rebuilds for the most trivial configuration change, anything to extract just one more license fee from the user. This, combined with the unix wars where players tried to outdo their competitors by doing things their own way made life much harder than needed.

      This is probably one of the biggest contributions Linux made to the unix world. While Linux might not officially be unix, it does away with all these artificial restrictions and offers the same options to everyone everywhere. The differences between Linux distributions are nothing compared to the difference between, say, HPUX and Solaris (or AIX or Irix or Non-Stop OS or AT&T system V, let alone SCO in its many incarnations...)

      --
      --frank[at]unternet.org
    78. Re:This could be good news... by Anonymous Coward · · Score: 2, Informative

      Have you tried using Xpra?. It does exactly that with X. It works great over the internet, and lets you attach and detach X applications across X servers. Basically, it's screen for X.

    79. Re:This could be good news... by Alomex · · Score: 1

      From missing tools and compilers to forced kernel rebuilds for the most trivial configuration change,

      You do realize that this describes Linux circa 1996 much better than Solaris in 1996, which always shipped with a full suite of compilers and developer tools, right? Back then you couldn't load a new driver into Linux without recompiling the kernel.

      That was in fact one of the key selling points of Sun hardware: you get the software for free.

    80. Re:This could be good news... by Anonymous Coward · · Score: 0

      No. The X protocol is still network transparent.

      If the newer toolkits like GTK and QT want to send only uncompressed bitmaps through, that's fine ... it doesn't mean it's not network transparent. It means that the network transparency is less efficient than other remote desktop solutions.

      For those of us who do work remotely, it's why we use xterm rather than terminal. It's why I don't use editors such as kate (which is so shitty it doesn't really even run remotely because it requires a local dbus ???). It's why we prefer the uglier toolkits. It's been this way for a while. You *really* begin to understand the difference if you, like me, have used X sessions over dialup ( and tools such as dxcp ).

    81. Re:This could be good news... by JoeMerchant · · Score: 1

      Competition is always healthy, which is why Windows sucked so badly for so long.

      Also, I can't help every time I see the name "Mir" - didn't that crash and burn years ago after an intentional de-orbit?

    82. Re:This could be good news... by Mashdar · · Score: 1

      gome24ever.

    83. Re:This could be good news... by wed128 · · Score: 1

      https://itunes.apple.com/us/ap...

      There is an x server for the ipad...

    84. Re:This could be good news... by Wdomburg · · Score: 1

      Erm, by 1996 we had Linux 1.2, which had loadable kernel modules and a full development toolchain, and Solaris 2, which included "no C compiler, not even a crippled one" *

      This was typical of Unix distributions of the era. Development tools for pretty much all the major Unix flavors cost hundreds, if not thousands of dollars. User space tools tended to be relatively primitive compared to their GNU equivilents (e.g. tar often supported only the old v7 or ustar variants which imposed path and file type limitations). Daemons that are not considered standard (sshd, ftpd, httpd) were often expensive and usually third party.

      And yes, many commercial Unix variants of the time still required relinking the kernel. OpenServed still required it up until 2005.

      * http://www.science.uva.nl/pub/...

    85. Re:This could be good news... by Microlith · · Score: 1

      if they're right then we need Mir for Linux on smart phones.

      That was one of the claims that Canonical made with no supporting evidence whatsoever. Ironically, Canonical made that claim, but Jolla shipped Wayland on their handset first - and the library that makes it possible to use Android drivers was developed by one of their engineers for use with Wayland.

      Mir may be useful, but Canonical marred its release badly.

    86. Re:This could be good news... by Anonymous Coward · · Score: 0

      You did not get Sun's software "for free", your company was paying a huge maintenance contract for it.

    87. Re:This could be good news... by phantomfive · · Score: 1

      And those bugs will be fixed, either in Wayland itself or in the code it depends on

      I'm not convinced that's true.

      And just "some X11 developers"? The most prominent supporters of Wayland are major X11 developers who know how broken X is.

      Yes, that is the problem. x.org developers aren't known for their project-management skills, and doing a big rewrite of something that basically works is a rookie project-management mistake.

      --
      "First they came for the slanderers and i said nothing."
    88. Re:This could be good news... by phantomfive · · Score: 1

      I never seem to have a need to run a GUI on a remote machine but I use them on my local machine every day

      Plenty of people have the need to use a remote GUI, that's why Microsoft made remote desktop. Usually though, you just need one or two applications, and it's more convenient to have them show up by themselves instead of needing to deal with the entire screen of the other computer.

      Of course, if all you ever do is admin on the command line, you're not going to need that. You probably don't even need a GUI at all on those servers.

      --
      "First they came for the slanderers and i said nothing."
    89. Re:This could be good news... by mx+b · · Score: 1

      I think we need both to compete.

      Why? Given they both solve the same problem, but one has wide support and has shipped on devices, what use is the other?

      "KDE solves the same problem as GNOME, what use is GNOME?"

      "Firefox solves the same problem as Chrome, what use is Chrome?"

      "iOS solves the same problems of a phone OS as Android, what use is Android?"

      We can go on like crazy with this concept. Competition spurs people to do better, even if ultimately one wins out over the other. The challenge is never to let anyone stay dominant for too long, lest people get lazy. Each of my examples above I think was in a bit of a rut until the competitors came along, and now they both push each other along, making everything better. I think we should encourage competition whenever feasible. (Although I am certainly open to the idea being that Canonical/Mir is not a particularly great competitor, but I wouldn't go so far as to make your claim; if another organization came up to make a Wayland competitor, I would be interested to see their ideas and take on the problem and let the best win).

    90. Re:This could be good news... by doti · · Score: 1

      Mint + MATE = heaven

      --
      factor 966971: 966971
    91. Re:This could be good news... by Anonymous Coward · · Score: 0

      While we are on that topic, could you (or someone else) explain how Microsoft's RDP achieves this great performance while VNC does not?

    92. Re:This could be good news... by neuro88 · · Score: 2

      Agreed. Wayland development appeared to accelerate after Ubuntu announced Mir. If the only thing that ever happens because of Mir is that it made the rest of the Linux community unite behind Wayland and speed its adoption, that's still a good thing.

      From what I've heard about the commit statistics, there was no real change in Wayland development itself. Where we're seeing the acceleration is the desktop environments realizing they really needed to start their porting work. THIS is definitely a good thing.

      And Ubuntu started Mir because their engineers seem to believe Mir has fundamental performance advantages over Wayland in resource-constrained environments like phones. It's possible they're completely wrong, but if they're right then we need Mir for Linux on smart phones.

      There seems to be this myth that Wayland doesn't work with Android GPU drivers. Mir's support for Android drivers uses libhybris to achieve this, which is atually Wayland library for allowing Wayland to work with Android GPU drivers.

      And we're starting to this sort of thing a lot. Mir really just isn't too fundamentally different from Wayland. Typically when Mir support is added to something, they've simply taken the Wayland support and have made a relatively small amount of changes (sdl2, xwayland/xmir, etc). I think in the long run, Canonical will partially throw in the towel and Mir will end up being a Wayland compositor that's also capable of running Mir specific (mobile?) apps.

      I don't know that the Mir devs really believed these issues. That's not to say that such claims weren't made (most/all of which were thoroughly debunked the same day they came out), but the real reason for Mir's existence is control for their mobile platform. Wayland is MIT licensed, and Mir is GPLv3 which a CLA. If canonical had been more honest about their reasons for Mir, I think they'd be receiving far less flak for it. No other reason really makes much sense. They're just too similar.

    93. Re:This could be good news... by TangoMargarine · · Score: 1

      We could have simply modified X.

      From what I've heard, there is nothing whatsoever "simple" about modifying X. Something about only 4 or so people on the planet understanding how the mangled internals work...

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
    94. Re:This could be good news... by spitzak · · Score: 1

      No, it is obvious if you follow development mailing lists that the announcement of Mir was a big kick in the pants for the Wayland developers and they started actually working on the real thing. So I think Mir did a good thing.

    95. Re:This could be good news... by TangoMargarine · · Score: 1

      How I wish I hadn't already commented on this article...

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
    96. Re:This could be good news... by TangoMargarine · · Score: 1

      I guess the main question keeping me from moving to Mint right away is...does Mint MATE/Cinnamon support Emerald? I'm not really aware of other easy-to-use themers available for Linux.

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
    97. Re:This could be good news... by Anonymous Coward · · Score: 0

      Our primary app at work is motif-based and heavily used over the local net via X transparency. Except it's not from 1995 it's from 2013-14 and you probably would have to mortgage your house to afford a single license. It may not have the bling, but I'd consider that a good thing. Check out the software which manages supercomputer job handling some time. If it's not motif it's tcl/tk, but who cares the important thing is how well it does it's job, not that it could have a transparent background.

      You are wong and we are proof of that. And there is nothing special or small about our field.

    98. Re:This could be good news... by Anonymous Coward · · Score: 0
    99. Re:This could be good news... by dbIII · · Score: 1

      Wayland initially relied on linux only features. Then it was made more portable.
      Happy?

    100. Re:This could be good news... by dbIII · · Score: 1

      Linux-only limitation was *never* proposed for Wayland

      Wrong. Looks like I can't even complement Wayland for reversing a poor initial choice without someone jumping on me and insisting it was born perfect.

    101. Re:This could be good news... by Dcnjoe60 · · Score: 1

      If you re-read the OP, the premise of that comment was since they both did the same thing why have them both? There are lots of projects that both do the same thing, for instance upstart and systemd. Using that rationale, which ever one shipped first should be the one everybody uses.

      I never said anything against Mir, as a matter of fact, my sarcastic remark was exactly the opposite of what you assume I was saying. In plain english, I was arguing that the OP was wrong and that Wayland and Mir can happily coexist until such time the market decides which is the preferred display manager, again, just like what happened with upstart and systemd.

      Also, unless I misread the OP, the AC wasn't comparing/contrasting Wayland or Mir with X windows, but with each other. Based on that interpretation, I made my comment. In reality, even if the comparison was with X windows, I would feel the same way. Just because something is established doesn't mean people shouldn't look at improving upon it. After all, not many are driving Model T's anymore (although I do drive a 1972 VW).

    102. Re:This could be good news... by dbIII · · Score: 1

      The specific is different to the general. I was replying to a general claim.
      What is it with this topic that brings out the slimy school mass debate tricks? I wrote something which was not even critical of the current state of Wayland and got buried under an avalanche of fanboys that appear to know very little about either Wayland or X.

    103. Re:This could be good news... by Bill_the_Engineer · · Score: 1

      I did. I interpreted as a sarcastic response to Microlith assertion that Mir isn't needed because Wayland already exists and solved the same problem.

      So when I read your sarcastic remark to the sarcastic remark I interpreted that you agreed with Microlith that Mir wasn't needed.

      What sealed the deal for me in the AC remark was "If Wayland is justified then so is Mir."

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    104. Re:This could be good news... by Bill_the_Engineer · · Score: 1

      Double sarcasm can be amusing at times. Enjoy the weekend (if you can).

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    105. Re:This could be good news... by Anonymous Coward · · Score: 0

      Why is this not the same for Wayland?

      I'm sure it is the same. I don't think Wayland is making a goal of being more easily portable than X, and I didn't say anything to the contrary - I said that it's a problem if the ports don't actually exist

      In the meantime, use X. I doubt it's going away any time soon.

      For me the end-user, either should do fine. For me the GUI developer, either should do fine. X11 compatibility is there, and that's assuming your GUI toolkit doesn't already support Wayland. (GTK+ and Qt both support Wayland natively, no X11 necessary).

    106. Re:This could be good news... by Wootery · · Score: 1

      Oops, posted as AC.

    107. Re:This could be good news... by Bengie · · Score: 1

      Funny how when I questioned that last time the "proof" was a bit of XFree86 code from the 1990s cut and pasted into Wayland by someone other than the author of that earlier code. After that was seen through - silence.

      Several of the current Wayland lead devs have been working on X for 15-20 years. But I guess they just "copy and pasted" some code.

    108. Re:This could be good news... by Anonymous Coward · · Score: 0

      You asked for proof Wayland devs are X11 devs, I provided it. Nothing fanboi about it.

      The simple fact is: the current X11 devs are putting their dev time in Wayland instead. If you want to keep X11 alive, feel free to take over maintenance and development, or find a group of people that are still willing to do it.

    109. Re:This could be good news... by Ash+Vince · · Score: 1

      I never seem to have a need to run a GUI on a remote machine but I use them on my local machine every day

      Plenty of people have the need to use a remote GUI, that's why Microsoft made remote desktop. Usually though, you just need one or two applications, and it's more convenient to have them show up by themselves instead of needing to deal with the entire screen of the other computer.

      Of course, if all you ever do is admin on the command line, you're not going to need that. You probably don't even need a GUI at all on those servers.

      I use rdp all the time, I was asking why it was so important to have X and its amazing single app rdp ability over what is provided by windows. I personally have never been in a situation where I the X stuff has ever been an imrovement i couldnt live without over something like Vnc

      --
      I dont read /. to RTFA, I read /. to offend people in ignorance.
    110. Re:This could be good news... by dbIII · · Score: 1

      Plural.

    111. Re:This could be good news... by phantomfive · · Score: 1

      I use rdp all the time, I was asking why it was so important to have X and its amazing single app rdp ability over what is provided by windows. I personally have never been in a situation where I the X stuff has ever been an imrovement

      Oh, because sometimes you only want to use a single app. Then it's great, it's a pain to have to import the entire desktop for a single app.

      --
      "First they came for the slanderers and i said nothing."
    112. Re:This could be good news... by Anonymous Coward · · Score: 0

      Bullshit, you hare brained FUD-artist. Wayland is the display server protocol specification. It was never OS specific.

      Weston is a Linux implementation of a Wayland compositor, however:

      > I think we need both to compete. Some of the early limitations proposed in Wayland were frankly, utter shit, and it was only pressure to lift their game that led to them being dropped.

      Weston being a Linux implementation was never an "early limitation proposed", and it has never "been dropped" due to Mir, either.

      > Happy?

      Seriously, you have no idea what you're talking about. Every time I see you post something on this topic, you just look like a fool. I suggest you save what dignity you have left, and desist. I'll be happy when you stop opening your lie hole.

    113. Re:This could be good news... by Windwraith · · Score: 1

      I use only three desktop effects, but those have been a productivity boost for me.
      First the "show all windows in a mosaic" kind of effect. My workflow can require having a large number of programs, some with multiple instances overlapping on the taskbar, so I activate the effect using a window corner and quickly picking the window I need. By now it's a bit of a reflex move and I can activate real fast.

      Second is making translucent windows. When working with graphics, specially when following a model, it's really handy. Can also serve to make some windows see-through so you can still read stuff going on below while you are fiddling with them.

      And third is live desktop magnifying. Useful for a few specific tasks where bad app coding doesn't allow resizing a display, so I just zoom in for those cases.

      I know my use case is niche at best, because I work with images/sound/models/code/notes all at once, but desktop effects used with some ingenuity can really enhance management of a desktop.
      I also use a few transition effects, but those are actual glitter, although my specific desktop of choice does minimize transitions towards the taskbar and when switching things quickly it provides a visual cue as where to click to reopen it without mentally parsing the taskbar contents.

      Anyway the point is that some can be useful. A desktop cube has the same usefulness as a wallpaper, but a few effects are used to manage things and can be really handy if you integrate them in your workflow.

    114. Re:This could be good news... by sjames · · Score: 1

      Given the (some) Wayland developers refusal to admit that X works over a network, this is a real pot meet kettle situation.

    115. Re:This could be good news... by sjames · · Score: 1

      So the sparkstation I used to work on only pretended to run X? It did a pretty good job of it, it looked and acted just like X and even worked with binaries linked against the X libs.

      I guess the O2 was also only pretending?

    116. Re:This could be good news... by sjames · · Score: 1

      What I don't understand is that since the bviggest single objection to Wayland is network capability and the Wayland team claim it will be easily inmplemented is why don't they go ahead and inplement it and silence about 75% of their critics in one swell foop? It *IS* easily done, right?!?

    117. Re:This could be good news... by sjames · · Score: 1

      So you are re-defining network transparency in a bad attempt at sour grapes?

      Sorry, no. X apps work just fine over the network. They could probably work even better, but denying the existence or utility of the feature isn't a good way to get there and it's devistating to your credibility. That is one reason why Wayland's credibility is in the dumper.

      Xpra is not vnc. Xpra doesn't run on Wayland. It does run on X because X is flexible.

    118. Re:This could be good news... by sjames · · Score: 1

      Try supporting a gui app when you have to make multiple network hops and use a tunnel to get to the machine you're supporting. Or, you might enjoy popping up a console for a virtual machine you have on a server somewhere (oops, you can't! You don't do X over the network!)

      Meanwhile, I hardly ever use a car so I strongly recommend we put yours in the crusher immediately. I won't miss it a bit.

      It's not my fault you don't get the most out of your systems.

    119. Re:This could be good news... by sjames · · Score: 1

      One does hope this mythical implementation for Wayland comes out faster than Duke Nukem Forever did. :-)

    120. Re:This could be good news... by sjames · · Score: 1

      Then perhaps the Wayland community should stop thumping their chests and telling us they intend to cram Wayland down our throats.

    121. Re:This could be good news... by dbIII · · Score: 1

      There was a udev thing. It's fixed now. Why the foaming at the mouth?

    122. Re:This could be good news... by dbIII · · Score: 1

      who thinks X is perfect in its present form

      Meanwhile take a look at all the noise generated when I merely pointed out that Wayland was not perfect on day one and has improved since.

    123. Re:This could be good news... by dbIII · · Score: 1

      Benchmarks please.

    124. Re:This could be good news... by dbIII · · Score: 1

      You've been a bit unreliable here so please supply a quote.

    125. Re:This could be good news... by dbIII · · Score: 1

      How about you turn that boundless energy and motivation into something useful and start developing for Wayland instead of just shouting about it?
      Think of it - you can still be a fanboy but you'll be able to argue from a base of understanding instead of just making silly things up that the developers wound find embarrassing.

    126. Re:This could be good news... by Anonymous Coward · · Score: 0

      If you watched the video, it also mentions Kristian Hogsberg (who started Wayland), so that would make it plural.
      If you want more, there's also Martin Peres, Matt Turner, Egbert Eich, Rob Clark, ...
      You can find their names in the Wayland mailing lists and on the X.org site .

    127. Re:This could be good news... by thegarbz · · Score: 1

      I for one am sick of shit from people who think that because something is new and doesn't have 30 years of coding and developing behind it means it shouldn't be done.

      How do you ever expect a platform to evolve?

      Proof? Google the name Daniel Stone, he's one of several Wayland developers who have been working on X11 and X.Org since the 90s.

    128. Re:This could be good news... by dbIII · · Score: 1

      Still a long long long way from the implication above that nearly all of the X devs are working on Wayland - however I will look those people up. On another story some idiot used "evidence" of some cut and pasted decade old code to give "proof" that Keith Packard was currently working on Wayland.

    129. Re:This could be good news... by dbIII · · Score: 1

      I wish the rabid fanboys here would actually watch that video and take Daniel Stone's advice instead of all the made up rubbish and "X sux" bullshit.

    130. Re:This could be good news... by dbIII · · Score: 1

      I see now where people are taking that "X is not network transparent" line out of context without understanding how silly it is out of context. I'd say almost all commercial applications on X do not use the newer rendering schemes at all, so in office environments where network transparency matters it's still there. Sure - the new gnome3 stuff has it done via a hack but how many people are really using that sort of stuff over a remote link?
      I suggest people watch this and try to understand it instead of just taking away sound bites.

    131. Re:This could be good news... by dbIII · · Score: 1

      It appears you've misunderstood something from a presentation by Mr Stone - perhaps relayed via someone else that didn't understand it. I suggest you look at it (or look at it again) and see what he defines as a "modern X system". Personally I doubt there's much remote access to gnome3 applications. Most applications used in science and engineering with remote access to cluster nodes or compute servers use toolkits he would consider positively ancient. Open/libreoffice doesn't use "modern X" either.

    132. Re:This could be good news... by thegarbz · · Score: 1

      Funny most of this comes directly from a former long time X developer who gave a presentation at our Uni, but what would he know right?

    133. Re:This could be good news... by thegarbz · · Score: 1

      Yeah ok I can see I'm arguing with a brick wall.

      Just because a toolkit has the capability to fall back to a method of rendering which doesn't use such amazing 90s innovations like hardware acceleration doesn't NOT make it "modern".

      I'm out, I've got better things to do than waste my time and you've got very little credibility compared to the X developers who came up with these statements to begin with so there's no point in continuing.

      Have a nice weekend.

    134. Re:This could be good news... by Anonymous Coward · · Score: 0

      While Keith is not developing Wayland as far as I know (he does more management these days), he fully supports the idea of X on top of Wayland, and gave presentations about that.
      X.org and X11 will be around for some time, if only to support legacy software. But the new development seems to focus on Wayland, with or without X running on top.

    135. Re:This could be good news... by dbIII · · Score: 1

      Yeah ok I can see I'm arguing with a brick wall

      Considering the lack of respect you've demonstrated here and even lying you've certainly acted as if you have been. I suggest you take a look at the Wayland video at:
      http://www.youtube.com/watch?v=RIctzAQOe44
      I suggest first you take his advice early in the video about posts like yours and then pay attention to the bits where he is describing X. Then try to understand his aim with Wayland (iphone quality display) and the scale of the problems he mentions instead of blowing them out of proportion.
      Also pay attention to what he means about "modern X" - he means cutting edge - gnome3 etc. Once you understand you'll see how people familiar with the topic can see that you are making things up and that you are doing a gross misservice to both Wayland developers and those that work in the X environment.

      Get it into your head that X and Wayland are different things and Wayland is something other than just a way to make X better. Wayland is a different approach that pushes a lot of things back to the application. His answer at the end: "multiple GPUs - that's a client problem". It covers a different scope to X and I wish you "X sux" fanboys would just talk about something you actually know about Wayland instead of things you don't know about X.
      Another thing - that oft quoted "3 people know about ..." is what is known as a JOKE. Why do we get idiots treating it as a fact?

    136. Re:This could be good news... by dbIII · · Score: 1

      If it's Mr Stone's presentation it appears you have failed to understand what he said, taken things out of context, and taken opinions as facts.

    137. Re:This could be good news... by SlaveToTheGrind · · Score: 1

      Yeah ok I can see I'm arguing with a brick wall.

      Yeah, he's a bitter little troll, this one. Can't be troubled to justify his snippy pronouncements -- the burden is always on you to go read something/think really hard/reeducate yourself to understand why he's correct. If you're bored sometime, you should ask him how he feels about BitCoin and to explain why he feels that way. Bring popcorn. LOL

    138. Re:This could be good news... by Anonymous Coward · · Score: 0

      Because it was *never* an "early limitation proposed" in Wayland. You stupid nitwit.

      It was an implementation detail of their reference compositor, Weston, which was not intended to be a production compositor in the early days.

      Is there finally some faint, dull, flickering of a light bulb, somewhere in that dense fog of a shit hole that is your mind now, or are you still completely oblivious and happy to continue boasting of your willful ignorance?

    139. Re:This could be good news... by Anonymous Coward · · Score: 0

      Wrong, idiot. Wayland is a display server protocol specification.

      Weston is the reference compositor.

      HURRRRRDERRR

    140. Re:This could be good news... by Anonymous Coward · · Score: 0

      You're foaming at the mouth. Just shut your trap for once.

    141. Re:This could be good news... by bill_mcgonigle · · Score: 1

      It *IS* easily done, right?!?

      What are your thoughts on this one?

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    142. Re:This could be good news... by sjames · · Score: 1

      That's a remote desktop. I don't want a window that contains the app's window. I want the app's window sitting on my desktop. I don't particularly want to run a compositor on the server, just the app itself.

    143. Re:This could be good news... by Samizdata · · Score: 1

      As long as it can give me decent video performance on my Intel GMA equipped netbook, I will be happy.

      --
      It's not the years, honey, it's the mileage. - Colonel Henry Walton Jones, Jr., Ph.D.
    144. Re:This could be good news... by Alomex · · Score: 1

      Right, because when I said Sun had tried an alternative to X, I certainly meant to say that X didn't run on Solaris.

      Nor were we aware it ever did run X, but thankfully you came here and told us, so now we know better.

    145. Re:This could be good news... by sjames · · Score: 1

      So in other words, they tried an alternative, and found it inferior. In fact, many tried alternatives that they found inferior to X. But this time they're REALLY going to kick that football!

    146. Re:This could be good news... by Alomex · · Score: 1

      So in other words, they tried an alternative, and found it inferior.

      Because that is the only possible alternative. We all know that if a product fails it's because it was technologically inferior. There are no other known reasons or possible externalities. This is whythe x86 instruction set won: because it was better and all others were found inferior. This is also why Windows won over Mac/Linux/Unix, because these last three were found to be inferior.

      In fact, many tried alternatives that they found inferior to X.

      Except for NextSTEP, Android, OSX and Symbian, which are clearly superior, but hey, who's counting?

    147. Re:This could be good news... by Samizdata · · Score: 1

      And, TigerVNC server (which I REALLY wanted to like) for Windows would crash about 30 seconds into any session.

      --
      It's not the years, honey, it's the mileage. - Colonel Henry Walton Jones, Jr., Ph.D.
    148. Re:This could be good news... by sjames · · Score: 1

      Yeah, that explains why Symbian and NextSTEP are all over the place! Android works well for phones and tablets, but I don't think it's really what we want on the desktop. OSX is fine for OSX, but I've never seen it anywhere else.

      There's a few different they and respective alternatives. All ended up the same way.

      I'm not opposed to a superior solution coming along, especially if it can at least be shimmed to interoperate. I just haven't seen such a solution yet. I have seen a lot that said they were right up to the day they were scrapped.

    149. Re:This could be good news... by complete+loony · · Score: 1

      Doing what you suggest would mean redesigning the network protocol from the ground up right? I mean you're talking about extending X11 so that is has some new features that GTK3 needs. So assume we did that. Now what about all of those Motif features that nobody is using. Do we still maintain them? How do we implement these new extensions and keep the old features in a way that improves the appearance of using the display?

      I mean X11 doesn't have an easy way to ensure your application window appears cleanly on the first screen paint. And it's full of network round trips and has quite a few state bugs. How do you improve motif apps so that they don't look like motif apps?

      There is so much in the X11 protocol that needs to be deprecated, that at this point you might as well throw it all away and build a better network protocol to replace it. Ok, so the Wayland devs aren't trying to design a new network protocol, but they're also not stopping the community from attempting to build one. Why not get all of the Qt, GTK, wxWidgets etc people into a room and hash out a new standard that they can all agree on.

      All the Wayland devs are doing is following the traditional Unix philosophy. Take apart the features of the old monolithic XServer, define the pieces that we need to run a display. Shift features into the kernel that should be in the kernel. Shift the application remoting network protocol up a layer into a client of the compositor.

      Oh, and in case you haven't noticed, there's nothing stopping you from remotely accessing the entire composited desktop via RDP or similar.

      --
      09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
    150. Re:This could be good news... by DuckDodgers · · Score: 1

      I don't understand enough of the technical differences between Mir and Wayland to make a real argument. The only technical post I read about Mir that wasn't too vague to be useful was this one: http://blog.cooperteam.net/201...

      I'm not saying Wayland cannot work well on ARM devices, if the Raspberry Pi can run X than certainly a Nexus 5 can run Wayland. But if that post isn't full of nonsense, then properly configured Mir will work more efficiently than Wayland in an environment like that.

    151. Re:This could be good news... by DuckDodgers · · Score: 1

      I had not seen any assertion that Wayland would not work with Android GPU drivers. I don't understand the architecture of X, Wayland, and Mir. As I just wrote elsewhere, the only not-totally-vague explanation of technical differences between Wayland and Mir that I've seen is this: http://blog.cooperteam.net/201... If the author of that post is correct, then Mir has a resource management advantage over Wayland in resource-constrained environments. That doesn't matter if you're getting a $600 on-contract phone in the first world but it's a very big deal if Canonical is trying to enter the middle and low end first world market or any portion of the third world market with Ubuntu Touch.

      But again, I don't know if the writer is correct about the details - and it's possible Wayland has some other effectively equivalent way of handling resources.

  2. X got from Version 1 to Version 11 in 3 years by Anonymous Coward · · Score: 0

    So, stop slacking, Mir and Wayland!

    1. Re:X got from Version 1 to Version 11 in 3 years by GigaplexNZ · · Score: 4, Insightful

      Version numbers don't mean a whole lot. Google Chrome hasn't changed much in 33 versions.

    2. Re:X got from Version 1 to Version 11 in 3 years by Bacon+Bits · · Score: 1

      Yeah, I tend to look at Chrome's version numbers as Chrome 1.xx. So we're currently at Chrome 1.33. When you realize that, the rapid release schedule make a lot more sense. Google just never plans to increment the true major version number, so they just drop it.

      It's the same with Firefox. It's true major version number is around 7.0, but it's really not far removed to just say that everything after Firefox 3.6 is part of Firefox 4.0, meaning we're on Firefox 4.27 now.

      --
      The road to tyranny has always been paved with claims of necessity.
    3. Re:X got from Version 1 to Version 11 in 3 years by TangoMargarine · · Score: 1

      And has been stuck at 11.x.y.z for the 27 after that...

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
  3. Debian Minimal Install by Anonymous Coward · · Score: 1

    It's simple. Install Debian Minimal and build your system up to what you want it to be.

    Want a desktop or several desktops to switch between?
    Your choice

    Want a window manager or several of them to switch between?
    Your choice

    It's all your choice.

    Show me why I should choose any flavor of Ubuntu when I can use Debian Minimal Install and create my own experiences?

    1. Re:Debian Minimal Install by flyingfsck · · Score: 1

      Ubuntu is for users who don't quite know what they are doing yet. It is somewhat like religion - eventually you grow up and move on.

      --
      Excuse me, but please get off my Pennisetum Clandestinum, eh!
    2. Re:Debian Minimal Install by Anonymous Coward · · Score: 0, Troll

      That's Linux in general. Eventually you realize that Linux isn't worth the trouble and that it isn't fun anymore and that you have better stuff to do in your free time, and so you switch back to Windows.

    3. Re:Debian Minimal Install by kthreadd · · Score: 2

      You are aware of that Ubuntu has the same thing, right? On 12.04 and older you can install it from the alternate CD installer, just select to do a minimal install at the boot screen. Later releases moved it to the server CD install but the result should be the same. It basically installs the ubuntu-minimal meta package and nothing else.

    4. Re:Debian Minimal Install by Anonymous Coward · · Score: 0

      okay so according to you guys, Debian is for homosexual atheists who switch back to Windows?

    5. Re:Debian Minimal Install by Mitchell314 · · Score: 1

      You misspelled BSD; it doesn't have any 'w's in it.

      --
      I read TFA and all I got was this lousy cookie
    6. Re:Debian Minimal Install by Anonymous Coward · · Score: 0

      "You are aware of that Ubuntu has the same thing, right?"

      Yes. And the packages come from Ubuntu repositories. FAIL.

      I want the purity of Debian instead of the mess that I feel Ubuntu has become. I want to use Debian repositories.

    7. Re:Debian Minimal Install by Anonymous Coward · · Score: 0

      Linux Mint is for people who do not know how to use Debian or Ubuntu.

  4. ***by*** 16.04 by Anonymous Coward · · Score: 0

    not wait "until" 16.04, by 16.04 we should definitely be on Mir.. The same way by 16.04 we plan to be on systemd. But much of the switch will happen in 14.10, some more in 15.04, etc....

  5. Re:Oh shiz by Anonymous Coward · · Score: 0

    You are what you eat

  6. tablet and phone by Anonymous Coward · · Score: 2, Informative

    It's already default on the tablet and phone, which is what Shuttleworth is excited about these days. So in that sense, it is already here.

    So wayland is going to have to do a lot more than make decent ground if Ubuntu is to drop Mir. Wayland will need to do everything that Mir and X11 can do, and exceed them, and also be on a mature and well tested code base. Merely being an adequate competitor won't cut it.

    1. Re:tablet and phone by pijokela · · Score: 1

      Do you mean that Mir is already on a phone? Or Wayland?

      I already have Wayland in my Jolla phone running Sailfish OS, so Wayland is just as ready in the mobile world. That is a working device that I bought.

  7. PhD thesis or display server? by dacut · · Score: 5, Interesting

    I've found (as a rule of thumb) that, when asking a grad student "How much time do you think you have left before you can write up your thesis?", if the answer is two or more years out then it really means "I don't know." The student honestly believes this answer, but in reality he/she doesn't know how much he/she doesn't know.

    I'm starting to feel about the same with Mir and Canonical here. Shuttleworth is the tenured but aloof professor who casually coaxes his students (employees) toward completing milestones but without too much urgency. Money's not plentiful, but the professor has enough contacts and contracts to keep his lab going and give a stipend to his students. They put out a few papers (releases) each year, and each time the students think this grand project is "almost done"... only to discover that there's still more left to do.

    There's tremendous value in this kind of exploratory research. I'm just not sure it makes sense to package it up for end users.

    If I were Mark Shuttleworth's technical advisor, I'd suggest examining RedHat's Fedora model. Create a small group called Canonical Labs where stuff like Mir and Unity can flourish, with continuous releases and without the artificial constraint of a set release date. (If this makes the environment too lackadaisical and development isn't progressing fast enough, find some other way to instill discipline and/or motivation; don't make it the threat of moving alpha code to end-users.) When it's stabilized (no longer shuffling menus and window icons around, for example), then integrate it with the main Ubuntu branch. Something a bit more edgy and up-to-date than Debian Stable or RHEL, but not so much that it constantly upends your users.

    1. Re:PhD thesis or display server? by nine-times · · Score: 1

      If I were Mark Shuttleworth's technical advisor, I'd suggest examining RedHat's Fedora model. Create a small group called Canonical Labs where stuff like Mir and Unity can flourish, with continuous releases and without the artificial constraint of a set release date.

      This brings a different kind of problem, which is that there becomes a whole new management level of keeping the two groups in sync. Otherwise, the "Canonical Labs" group might run off and do all kinds of things that are great, but which never get integrated into the main project.

      I'd sooner suggest that they just be more clear in announcing these release dates that they're very tentative estimates of when it'll be included as the default, so that people aren't so damned disappointed. That said, having an unfettered R&D process that can come up with whacky impractical things is also nice.

    2. Re:PhD thesis or display server? by dacut · · Score: 1

      This brings a different kind of problem, which is that there becomes a whole new management level of keeping the two groups in sync. Otherwise, the "Canonical Labs" group might run off and do all kinds of things that are great, but which never get integrated into the main project.

      But PARC was so successful! Oh, wait... ;-)

      Your point is well taken. I believe it's a problem they already have, though: the Mir slip, shipping Unity before it was really ready, etc. Reorganizing -- even if it's done purely in Shuttleworth's mind and not on paper -- would bring these issues to the forefront.

    3. Re:PhD thesis or display server? by nine-times · · Score: 1

      Well I think ultimately what they've been doing is fairly smart. It seems to me that they have a pattern of developing these things as part of the main project, integrating it in as an experimental/optional feature for a while, and then putting it as the default after the kinks have been worked out. I think a lot of the problem is a perception problem-- people see the roadmap and see the experimental state of the upgrade, and are disappointed when it's not ready as quickly as they expected.

      I think if it were a closed-source company with only internal roadmaps, and these things were included in experimental/beta versions that were not released to the public, it would all be normal. It mostly seems problematic because it's FOSS and we get to see the messy behind-the-scenes development.

      Of course, that's just my perception of what's going on, as someone who's interested but not knowledgeable and not a developer.

  8. Re:I don't know why anyone bothers with Linux. by Anonymous Coward · · Score: 0

    Is she hot?

  9. No big deal by Thanosius · · Score: 3, Funny

    Delays just mean they're working on perfecting and producing the best of what they're trying to develop, and that once released it'll be a crowning moment of awesome as a consequence of the delays. Just like Duke Nukem Forever.

    --
    Account abandoned. I can't fucking spell for shit and Slashdot doesn't even allow time-limited edits of posts. Plus you'
  10. Another by Anonymous Coward · · Score: 1

    Hurd vs Linux ? Awesome! Not..

    1. Re:Another by Chrisq · · Score: 2

      Hurd vs Linux ? Awesome! Not..

      At the moment this is looking more like Hurd vs Plan 9. Neither wayland nor Mir have mass appeal or momentum.

    2. Re:Another by Anonymous Coward · · Score: 0

      plan 9 vs HURD vs Stallmans great beard
      Linux wins

    3. Re:Another by TangoMargarine · · Score: 1

      Making fun of HURD plumbs whole new depths of the phrase "beating a dead horse"...HURD is more like the horse that was beaten within a few inches of its life, all of its legs were nonfunctional and its skin was rotting, but it still managed to drag itself across the finish line by its teeth, a mile away and a whole year later, but all the spectators have long since left.

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
  11. Display server is a forced choice by enos · · Score: 1

    This Mir/Weyland/X debate is NOT another KDE v.s. Gnome or Emacs v.s. VI. In those debates every user is able to choose what they prefer.

    The display server choice is made by the software writer, not the end user. If the end user wants to use a particular piece of software, they will have to use the display server that the software requires. There is no choice.

    --
    boldly going forward, 'cause we can't find reverse
    1. Re:Display server is a forced choice by Anonymous Coward · · Score: 0

      According to the GPL reasoning, there is choice. As long as the source code is open, it empowers the user and allows them to make their own choices.. oh wait, not every user can program. Well, there goes that argument.

    2. Re:Display server is a forced choice by petermgreen · · Score: 1

      I'm not convinced of that, there may be a handful of apps that are written directly to target wayland or mir but for the most part I would expect apps to continue to use toolkits like qt and gtk which afaict will support multiple backends.

      Apps that use x directly or use an older/more obscure toolkit that only has an x backend will be supported on mir and wayland through thier x compatibilty layers.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  12. Try harder by dbIII · · Score: 0

    You are really calling the people who have been using X for years "noobs"? How interesting and childish. You've also shown you did not understand my bit on X windows on MS Windows yet replied with an opinion anyway. Since wikipedia exist you have no excuse for such a thing.

    1. Re:Try harder by Alomex · · Score: 2

      Absolutely. I've been using a car for twenty years that doesn't make me an expert mechanic. It's funny that simply because you open a windows manager or write a few function calls for X you consider yourself an expert. on it.

      The people who do know the X innards inside and out, namely X.org, says it sucks and are writing Wayland.i

    2. Re:Try harder by thegarbz · · Score: 4, Insightful

      You are really calling the people who have been using X for years "noobs"?

      Using X does not mean understanding X. Additionally using X does not mean understanding how things have changed under the hood when there's been no visible change in the usability of the system.

      Frankly a lot of X veterans who maybe once used X in a truly network transparent way think that just because their ability to send a window to another X system means it's still network transparent, which is utter rubbish. There's no modern distro which actually implements remote X in any other way than Wayland is proposing to do it, pixels scraping and sending it over the network.

      Yet for some reason some people are still hung up on a feature which they think they use because frankly they don't understand anything, and the most vocal bunch seems to be the ones with the longest beards.

    3. Re:Try harder by SkunkPussy · · Score: 1

      Presumably if you're arguing on slashdot its because you've got quite a long beard yourself.

      --
      SURELY NOT!!!!!
    4. Re:Try harder by dbIII · · Score: 1

      With respect I suggest you look into the subject so you understand enough as to why I am calling out the above fool for the idiot that he is.

    5. Re:Try harder by DrXym · · Score: 2

      Not so much pixel scraping but pixel pushing. Most apps render themselves into a pixmap and push it around the network. They're not using X primitives. They *might* be using XRender primitives or they might not. It's still a large amount of data, and combined with the synchronous nature of X, it's horribly inefficient. A remoting enabled compositor for Wayland could probably work better than X, even for the one thing that people always go on about X being good for.

    6. Re:Try harder by Anonymous Coward · · Score: 0

      What? You've clearly got it wrong. It isn't that X has changed.

      What has changed is that the "modern toolkits" like GTK and QT essentially only deal in bitmaps. That's exactly why I use xterm rather than terminal when remote. Similarly for other apps. For my usage the old ugly looking toolkits that are truly elegant and beautiful because of their low network bandwidth.

    7. Re:Try harder by Uecker · · Score: 1

      You are really calling the people who have been using X for years "noobs"?

      Using X does not mean understanding X. Additionally using X does not mean understanding how things have changed under the hood when there's been no visible change in the usability of the system.

      Nobody complains about changes under the hood if there are no regressions. Don't beat up a stawman.

      Frankly a lot of X veterans who maybe once used X in a truly network transparent way think that just because their ability to send a window to another X system means it's still network transparent, which is utter rubbish.

      I would say this is exactly what network transparency means. That there are optimizations for local clients does not change this a bit. Similar optimizations have been there forever (MIT SHM).

      There's no modern distro which actually implements remote X in any other way than Wayland is proposing to do it, pixels scraping and sending it over the network.

      Well, the design of Wayland is actually not so much different than X. (Still people claim it will magically be much more performant.)

      The problem with Wayland is: It breaks compatibility with X without having any real advantage.

      Yet for some reason some people are still hung up on a feature which they think they use because frankly they don't understand anything, and the most vocal bunch seems to be the ones with the longest beards.

      And the insults don't help your case. You don't have to grow a beard, but a bit of maturity would be nice.

    8. Re:Try harder by Anonymous Coward · · Score: 0

      But even that is greatly aided by the support for network transparency. Tunneling X over SSH (the most common flavor of remote X at this point) was easy to implement because whether connecting to a local or remote X-server, applications expected to make a single connection and shove data over that. As such, SSH could very easily emulate the presence of a X-server by making a socket in /tmp and setting the environment variable to direct X-clients to connect to it. If X had instead had applications opening /dev/fb0 and then drawing pixels, X forwarding over SSH would have been extremely difficult. Even if X's native network support is rarely used nowadays, having that hidden underneath everything continues to pay major dividends.

    9. Re:Try harder by sjames · · Score: 1

      You are the noob if you think pixel scraping is involved. I'll repeat my challenge. If Wayland over the network is so easily done, why not do it and silence about 75% of the critics?

    10. Re:Try harder by sjames · · Score: 1

      And if I had a pegasus I could ride to work in style. Much as my garage seems devoid of pegasi, Wayland seems devoid of remoting enabled compositors.

    11. Re:Try harder by Anonymous Coward · · Score: 0

      And yet the Weston compositor has been demonstrated with both VNC and RDP style remoting. Can I see your weird flying horse now?

    12. Re:Try harder by thegarbz · · Score: 1

      Nobody complains about changes under the hood if there are no regressions. Don't beat up a stawman.

      /

      Regressions are only existent because of the early stages of development compositors are in. As the developers have mentioned over and over again to their finger in eared critics, there's nothing preventing remote applications, and indeed Weston was shown to have some alpha RDP style code in it. Unless you're complaining about the fact that Wayland won't do everything under the sun like X tried to do in which case yes that's a regression, but not one that I would complain about.

      I would say this is exactly what network transparency means. That there are optimizations for local clients does not change this a bit. Similar optimizations have been there forever (MIT SHM).

      No. Just no. The ability to remotely display an app does not make it network transparent. If that's what you think then you should be happy that Wayland will allow the exact same "network transparency" you so hold dear. Network transparency means the app renders in the exact same way regardless of the target, which is just plain false. You call different ways of rendering "optimizations" I call them no longer being network transparent, which is what the Wayland people also mean when they say the protocol isn't network transparent.

      Well, the design of Wayland is actually not so much different than X. (Still people claim it will magically be much more performant.)

      The problem with Wayland is: It breaks compatibility with X without having any real advantage.

      There are plenty of advantages. Currently developers have to implement some insane workarounds to cover some basic use cases of a modern OS. For example, in Linux currently you are unable to use media buttons while the display is locked or the screen saver is on, unless the screen saver is written in a way specific to capture the inputs and pass them up the chain. I.e. with Linux on my laptop I actually need to type in my password to skip to the next song despite the fact I have buttons placed at the front of my laptop which I can use without even opening the screen. It's this kind of crap that holding the system back from common use. Things don't "just work". Things need working around.

      And the insults don't help your case. You don't have to grow a beard, but a bit of maturity would be nice.

      Did not mean to insult. Just trying (and failing) to be clever. But in plain english, the people who are most vocally against Wayland appear to be either people jumping on bandwagons with no clue, or people who have been long time users of Linux who live and breath command lines and remote desktop sessions, who don't understand how much things have changed under the hood despite the fact they can still use the system the same way they always have. A classic example is one of the replies above saying xterm is truly network transparent. Yes it is, it's not the default terminal in any flavour of Linux except for maybe Arch.

      People are stuck in their ways and are worried their world will be turned upside down. What I don't understand the most about this is that this is Linux. Don't like Wayland? Don't use it!.

    13. Re:Try harder by DrXym · · Score: 1

      Weston supports RDP in about 1000 lines of code hooked up to FreeRDP. So yes it does remoting and any other compositor can do it too.

    14. Re:Try harder by thegarbz · · Score: 1

      You're a noob if you don't. Wayland and networking has been done. There was even a slashdot article about it. The critics are just bitching and moaning that the functionality is not defined in the protocol. Well not shit, defining every little thing turned X into the clusterfuck it is today. There's nothing in Wayland that prevents network display of applications.

    15. Re:Try harder by sjames · · Score: 1

      Does it work such that I may ssh to the remote machine somewhere, run a Wayland app on the command line and have it's window appear on my desktop?

    16. Re:Try harder by sjames · · Score: 1

      Does that give me the app window integrated into my local desktop or does it give me the lame extra desktop in a window experience?

    17. Re:Try harder by Uecker · · Score: 1

      As the developers have mentioned over and over again to their finger in eared critics, there's nothing preventing remote applications, and indeed Weston was shown to have some alpha RDP style code in it.

      I would not complain if the Wayland people would just shut up and work on their stuff and once everything is ready *propose* it as an alternative... Instead of declaring it as the future replacement long before even basic functionality it is ready (and I am not talking about network transparency).

      I also don't care what kind of RDP stuff the can possible build into Wayland. I need *compatibility*. The huge advantage of X is that is a standard with a huge number of apps, and a protocol which is currently spoken by every Linux and UNIX machine. A switch to Wayland (or MIR) will damage this ecosystem. Linux/Wayland will be different to Linux/X similar to how Android is different. Breaking API compatiblity on the Linux desktop is just insanely stupid. And this is exactly what Wayland is about.

      I would say this is exactly what network transparency means. That there are optimizations for local clients does not change this a bit. Similar optimizations have been there forever (MIT SHM).

      No. Just no. The ability to remotely display an app does not make it network transparent. If that's what you think then you should be happy that Wayland will allow the exact same "network transparency" you so hold dear.

      Network transparency means the app renders in the exact same way regardless of the target, which is just plain false.

      Please define "exact same way". Currently, almost all applications (not just xterm, also all others: I commonly use: eog, gnome-terminal, nautilus, evince, gitk....) work just fine over the network. And as far as I see they render in exactly same way (using the X render extension). So please clarify what you mean by "not network transparent". Are you talking about OpenGL applications? Those would render differently (GLX for remote and direct rendering locally), but I think this is handled transparently to the application by the mesa library.

      ...media buttons...

      The media buttons seems the only real argument that comes up. But it is hard to believe that you have to throw out a decade of API compatibility to fix this minor issue. The way that Wayland seems to fix this is to have special support for screen savers. Certainly, one could have a special functonality in X as well.

  13. Re:I don't know why anyone bothers with Linux. by udippel · · Score: 1

    Is she hot?

    Marrying Windows 8 precludes the need of an answer ... .

  14. Werevapour by Anonymous Coward · · Score: 0

    Mir is half a meerkat that turns into vapour at full moon.

  15. wrong by Spiked_Three · · Score: 1

    Yeah, really, why limit it to commercial version of Unix that suck. I haven't seen any that doesn't suck.

    And on topic, so this new server is buggier than the current xerver? How can that be, the current version has to be one of the buggiest pieces of distributed code I have ever seen.

    People moved in hordes to RDP as a protocol because X sucks so bad on a LAN. But the desktop will not run on RDP, unless you switch to XFCE. Is it just me, or does XFCE look like something from the 50s?

    With all the talk about open source responsiveness to fixing issues, this is state of the art.

    --
    slashdot troll = you make a compelling argument I do not like the implications of.
    1. Re:wrong by SkunkPussy · · Score: 1

      > People moved in hordes to RDP as a protocol because X sucks so bad on a LAN

      That doesn't add up - VNC has been around since forever so people would have moved to that for the same reasons that they might move to RDP. (RDP is a bit better than VNC but that's not really relevant).

      My experience of X on a lan is quite good - I use remote gvim all the time. X over the internet isn't so good. I have occasionally ran remote gvim sessions over the internet in the past but forgoing a GUI and running vim over SSH is preferable in that case.

      --
      SURELY NOT!!!!!
    2. Re:wrong by Viol8 · · Score: 1

      "Yeah, really, why limit it to commercial version of Unix that suck. I haven't seen any that doesn't suck."

      You haven't seen many then. Almost all the commercial unix's still around (AIX, HP-UX, Solaris) IMO are better for heavy iron back end use when compared to Linux. No one gives a shit if they don't support the latest flavour-of-the-month graphics doodles on the desktop , thats not what they're designed for. If you want fancy graphics by a Mac, but don't expect to run a bank on it.

      "because X sucks so bad on a LAN"

      Whatever. This tedious argument is so old and disproved I'm amazed anyone still dishes it up in a serious debate.

    3. Re:wrong by Spiked_Three · · Score: 1

      gvim, lol. seriously dude, I do NOT want to argue with you.

      --
      slashdot troll = you make a compelling argument I do not like the implications of.
    4. Re:wrong by Spiked_Three · · Score: 1
      --
      slashdot troll = you make a compelling argument I do not like the implications of.
    5. Re:wrong by Rob+Y. · · Score: 1

      I agree. We use AIX at work. No X or GUI of any kind, but the systems are rock-solid and essentially never need to be rebooted - even for fairly serious filesystem changes. My only complaint about AIX vs Linux for our server-based apps is that it's harder to find pre-built binaries when I want to incorporate a new open source library into our system. Sometimes it's hard even to get the code to build with the standard 'configure - make' process (though I've always been able to get it to work eventually). In any case, I assume that's just a function of mindshare, not technology.

      --
      Posted from my Android phone. Oh, I can change this? There, that's better...
    6. Re:wrong by DuckDodgers · · Score: 2

      What makes the commercial Unix's better for heavy iron back use? (That's a genuine question, not a challenge.) I understand that earlier versions of the Linux kernel didn't do multi-threading in an efficient way - too much locking, and they lacked asynchronous IO and a few other similar technologies that made them inefficient for huge multi-threaded tasks. But my understand is that these days, it can keep up with just about anything for efficiency and stability.

    7. Re:wrong by Viol8 · · Score: 1

      Scalability (CPUs and petabyte storage ability), reliability, proper containers, kernel tuned to the specific hardware, better system management apps

    8. Re:wrong by DuckDodgers · · Score: 2

      Most of the supercomputers in the world are built using Linux. Are you saying that Linux is used in those machines strictly because of commercial Unix licensing costs?

  16. Who modded this crap up? by Viol8 · · Score: 1

    "There's no modern distro which actually implements remote X in any other way than Wayland is proposing to do it, pixels scraping and sending it over the network."

    Utter utter utter crap. If you open a standard X app - eg xterm - on a remote server it will use the standard X protocol, it will NOT do remote desktop style pixel scraping. If you don't believe me check it out with tcpdump.

    "Yet for some reason some people are still hung up on a feature which they think they use because frankly they don't understand anything"

    As you're proving - its the ones who make the biggest noises who usually understand the least.

    1. Re:Who modded this crap up? by Kjella · · Score: 2

      There's no modern distro which actually implements remote X in any other way than Wayland is proposing to do it, pixels scraping and sending it over the network.

      Utter utter utter crap. If you open a standard X app - eg xterm - on a remote server it will use the standard X protocol, it will NOT do remote desktop style pixel scraping. If you don't believe me check it out with tcpdump.

      You're of course technically correct, as long as you run a plain X application. Which is xterm and.... what? Nothing that uses KDE, Gnome, wxWidgets or any other form of toolkit from the last 15 years at least. If you talk about remoting anything that actually looks like a GUI there's a 99.99% chance it won't be network transparent, but if you cover your ears and chant "xterm" real loud you can ignore that. And if xterm is all you need you might as well use plain SSH, it's basically SSH with a server drawn border instead of a client drawn one.

      --
      Live today, because you never know what tomorrow brings
    2. Re:Who modded this crap up? by Anonymous Coward · · Score: 0

      >>modern distro

      > standard X app

      > xterm

      There's your problem.

    3. Re:Who modded this crap up? by Uecker · · Score: 1

      Modern applications will use the X Rendering extension. The Rendering extension was designed more than 10 years ago to replace the outdated rendering model of X. It was insprired by the network transparent windowing of plan 9 and specifically introduced with network transparency in mind.

      http://keithp.com/~keithp/talk...
      (see the conclusion)

    4. Re:Who modded this crap up? by Anonymous Coward · · Score: 0

      Nedit and plenty of other good tools.

      And for the modern toolkits there is 'ssh -CX', which works fine.

      Your 'fuck beta' sig is entertaingly ironic.

    5. Re:Who modded this crap up? by sjames · · Score: 1

      Considering that the machine I run them from does not have an X server of it's own running, the apps are necessarily network transparent. There's no other X than my desktop for them to work with.

      There exist OPTIONAL protocols that the apps MAY use if the X server happens to be local, but OPTIONAL means they don't have to use them. Funny that the apps using all of the toolkits you mention all work just like xterm over the network.

    6. Re:Who modded this crap up? by thegarbz · · Score: 1

      So xterm is your terminal of choice? For most users it's not. xterm is the terminal I run when I debug to see if my window system is working.

      Then I revert to the countless faster, more capable, prettier terminals which support such amazing technical advancements like antialiasing, multi-windowing and don't make me feel like I've taken a time machine back to the early 90s.

      You are of course correct. xterm is network transparent. None the less it's one of the few apps "in use" that still is, and I put the words "in use" in quotes due to the technicality that SOME people MAY still use it sometimes.

    7. Re:Who modded this crap up? by thegarbz · · Score: 1

      No your apps are capable of running over the network, that does not make them network transparent. You have just produced a perfect example of the ignorance between the terms.

      Your programs will actually fallback to a different way of rendering as a result of not running locally. That is the prime example of not being network transparent.

    8. Re:Who modded this crap up? by sjames · · Score: 1

      Actually, from the use case standpoint it's an entirely worthless distinction. It's a distinction mostly used by Wayland cheerleaders as an out when they get caught lieing their asses off about use over the network.

      Plenty of people have made it perfectly clear what they were talking about. You know damned well what they mean.

  17. Re:I don't know why anyone bothers with Linux. by hawkinspeter · · Score: 1

    And people wonder why inbreeding is bad?

    --
    You're a temporary arrangement of matter sliding towards oblivion in a cold, uncaring universe
  18. All This Infighting... by Anonymous Coward · · Score: 0

    is ridiculous. Listen... Arguing on the Internet is like running in the special olympics -- even if you win, you're still retarded.

  19. Why so much FUD about X? by dbIII · · Score: 1

    So says the fool putting himself up as an "expert" that has never heard of X windows being used on MS Windows. A large chunk of the engineering, design, SFX and geophysical sectors run the way and linux made it's way onto the engineering office workstation mostly to replace MS Windows machines mainly running X.
    How did you manage to not notice anything as major as that when you were become enough of an expert to shout us all down?

    What motivates such fanboys to be so aggressive about a topic that they know so little about and should care so little about?

    1. Re:Why so much FUD about X? by Anonymous Coward · · Score: 0

      "expert" that has never heard of X windows being used on MS Windows

      Are you on drugs? because otherwise I don't see how you could come up with this conclusion. FWIW, I've been running an X server over windows since the mid-90s.

    2. Re:Why so much FUD about X? by dbIII · · Score: 1

      Alomex above made that mistake.

    3. Re:Why so much FUD about X? by sjames · · Score: 1

      I can confirm this. I support several clusters for engineering firms. They run X and putty on Windows to connect to the master node and run X applications that display on their desktop machines.

  20. And I'll still be running MATE by TheSpoom · · Score: 1

    So get off my lawn!

    --
    It's better to vote for what you want and not get it than to vote for what you don't want and get it.
    - E. Debs
  21. Experimental by Nick · · Score: 1

    "Mir is already packaged as an experimental option, along with an experimental Unity 8 desktop session." Good God. The Ubuntu desktop always has been and always will be an experimental mess. I can't ever remember being more scared to reboot my workstation after a kernel update with the likely possibility of having restore my video driver and settings. My old 386 with 4 (!) mb ram, running twm has less issues.

    --
    Fuck Ajit Pai
  22. I've been paying attention - why don't you? by dbIII · · Score: 1

    It came up in an interview and was not seen as a big deal because it was linux only by design and not about "bending over backwards for fringe platforms".
    https://archive.fosdem.org/201...
    Then the developer pool expanded and the design changed - and FYI, policy went from "no compositor but Weston" to "reference compositor". The monolithic design was supposed to be a major feature initially, everyone was supposed to use Weston if they wanted to use Wayland at all. The project is improving, IMHO partly because they now have to be better than what Mir says it's going to be.
    It's an example of progress. I really don't get why there is so much hate being spread around here that I can't even point out something good about Wayland without people insisting that I should be saying it started as perfect.

    1. Re:I've been paying attention - why don't you? by Anonymous Coward · · Score: 0

      No, they were always separate, that's why the projects even had separate names and licensing in the beginning.

      And you're just making things up to suit your wrong position now. The policy in fact went from reference compositor to compositor usable by others with its plugin architecture. Nobody *EVER* was mandating "no compositor but Weston".

      So, shut your trap and stop spewing stupid, transparent FUD.