Ubuntu Still Aims For Wayland in Quantal Quetzal

jones_supa writes "While there's still more than one month until the Ubuntu 12.10 feature freeze, Ubuntu developers continue to work towards their tight schedule of having Wayland serve as the compositor for the Quantal Quetzal release due out in October. Canonical's intends to provide smooth transitions from boot to shutdown. Wayland is also used for session switching and other operations, avoiding traditional VT switching, providing a consistent monitor layout, using the greeter as the lock screen, ensuring that locked sessions are actually secure from displaying, and showing the greeter while the session loads. Phoronix remains skeptical about Ubuntu making the deadline."

Comments

Ubuntu to developers: "pound sand"

[xxxJonBoyxxx]

>> Will applications need to be rewritten or modified to work on Wayland? Yes. (From TFA.)

As a developer, I'm about to get off the Ubuntu train. Every major release recently has required tweaking the UI (e.g., tray icon behavior changes). I'm not really looking forward to another migration, especially when there are Red Hat and SUSE users (who tend to buy more) who are looking for things too.

Re:Ubuntu to developers: "pound sand"

[DeathToBill]

Although the more detailed answer is that GTK/Qt apps will need recompiling with an updated library. If you use X11 directly, then you have more work - except that you can also run an X server within Wayland to support native X11 clients.

I've been impressed for some time with how well the Wayland developers have thought about backwards compatibility. X11 needs replacing; complaining that its different to X11 doesn't help solve the problems.

Re:Ubuntu to developers: "pound sand"

[Anonymous Coward]

>> Will applications need to be rewritten or modified to work on Wayland? Yes. (From TFA.)

As a developer, I'm about to get off the Ubuntu train. Every major release recently has required tweaking the UI (e.g., tray icon behavior changes). I'm not really looking forward to another migration, especially when there are Red Hat and SUSE users (who tend to buy more) who are looking for things too.

No/Not-many (From TFA.)
The Ubuntu plan is for Wayland to be a system compositor, not a full X replacement. Most applications stay the same running under X. Just patches to X and the DM to get them working with Wayland.

X on Wayland is targeted as running at the same speed (or being more responsive) as just X alone.

A later (unplanned) release to Ubuntu may likely take the step of replacing X applications with ones running on Wayland but X will still run on top when needed.

Re:Ubuntu to developers: "pound sand"

[babai101]

All of the X apps will remain compatible as they will also run an Xserver instance on top of wayland, it will not be that much PITA for the devs.

Re:Ubuntu to developers: "pound sand"

[Anonymous Coward]

run an Xserver instance on top of wayland,

Which completely breaks the totally seamless integration of remote and local X apps (both 2D and 3D) that we have today.

Re:Ubuntu to developers: "pound sand"

[LordLimecat]

Ubuntu is the best thing to happen to Linux for all of us who dont use Linux. Its users have been faithfully beta testing for everyone else for the last 6 years :P

(For the record, if I was to switch my primary desktop back to Linux, theres a good chance it would be Ubuntu-- life is an adventure)

Re:Ubuntu to developers: "pound sand"

[Anonymous Coward]

Will applications need to be rewritten or modified to work on Wayland? Yes.

That's the cost of quitting X11.

TFA also says it will be running an X11 server inside of it to allow X11 applications to keep working.

Re:Ubuntu to developers: "pound sand"

[Dog-Cow]

How is that even remotely (pun not really intended) true?

Re:Ubuntu to developers: "pound sand"

[Anonymous Coward]

Please explain to me how the addition of another abstraction layer and the loss of hardware acceleration (neither ATI nor nVidia even care about wayland) is resulting in a net speedup...

Re:Ubuntu to developers: "pound sand"

[snadrus]

Sure. X11 needs replacing because its hardware acceleration is worse than Wayland. X11 is actually many programs acting like layers: window mgr, compositor, greeter, locker, etc will be only 1 under Wayland. And still the design is simpler than any one. It's not that the code is being added, but that a no-longer-useful X11-style abstraction is being let-go.

Re:Ubuntu to developers: "pound sand"

[GameboyRMH]

Can't blame you, Ubuntu just can't stop jumping sharks...if only they could have stuck to being a normal fucking desktop distro, not only would Ubuntu be much more popular, but desktop Linux would be as well. When they moved the window control buttons to the left they had already gone off the deep end.

Re:Ubuntu to developers: "pound sand"

[devent]

X11 needs to be replaced? Like my roof needs to be replaced because it works and have no holes in it? But it is old, I think about 15 years, so yeah it needs to be replaced.

X11 is old, but it works. I can have multiple monitors just fine, 3D effects are working fast, games are working. Also, it is supported by all hardware vendors like AMD, Nvidia, Intel. Also I have network transparency with no additional costs. Multi-User works just fine with very easy Ctrl+Alt+F1 up to F12. I don't know why you want something else. In KDE there is also a user switcher GUI way. Boot is smooth in Fedora 14, 15 and 16.

As long as there are no drivers from AMD, NVidia and Intel, Wayland will be a wet dream of a few developers. I do not need to go back to the time where the only graphics mode was Framebuffer. My impression is from the Ubuntu developers that they like some kids who are just pushing things like they want without any though about anything. Just to be different or "cool".

First the totally unnecessary changes in Gnome with the Close/Minimize buttons; then the not usable Unity; and now the Wayland, which will be usable only after more 5 years in development and testing.

Re:Ubuntu to developers: "pound sand"

[Anonymous Coward]

Also, it is supported by all hardware vendors like AMD, Nvidia, Intel.

This. You need to be modded up. The only graphics vendor on board with Wayland is Intel.

Re:Ubuntu to developers: "pound sand"

[DeathToBill]

X11 is more like a roof that was originally a 40-foot timber yacht. You've turned it upside down and fixed it to the tops of the walls. Gradually, over the years, you've patched in the holes until it only leaks when the wind is in the West. You've figured out how to get a flue up through the thing. You've nailed a TV antenna to it, and sealed around the cable with silicone. When you put it there you never bothered to take the decks out, so it's almost impossible to get into and work on and the structural elements, optimised rather for the sea than for housing, make it not very useful for storage. You still have to repaint it with pretty expensive paint every five years or so, else it starts to rot, and for some reason it attracts lots of confused-looking seagulls.

Anyway, look at all the features! It's got a winged keel, a 200hp diesel engine, and a gorgeous timber and brass wheel. All the fittings are marine-grade stainless, the rigging was all almost brand-new when you installed the thing and in her day she'd do 27kt reaching across a good wind. Don't actually use much of that any more, of course, but still...

Technically the keel still violates local planning ordinance, and technically it still smells quite a bit of fish. But it's been there for 15 years and it works. There's no need to replace it.

What's that love? You want to build an extension? Ah.

Re:Ubuntu to developers: "pound sand"

[DeathToBill]

And, in case you missed some of the metaphor there, the basic problem with X11 as a display system for desktop systems today is that none of the apps written for it actually use X11. Your multiple monitors work because of Xrandr - which isn't part of X11. Your 3D effects work by bypassing the X server and making OpenGL calls - not part of X11. It's supported by all the hardware vendors - and most of that support is in kernel drivers, not in the X server itself. VT switching works... more... or... less... until you'd actually like to switch VT before you get back from your coffee break, or your X server doesn't recover correctly. And, in case you missed it, they're not provided by X11. And I'm not sure what boot times have to do with it?

Your apps draw using Cairo or similar, not X11. They draw onto a buffer provided by the compositing extension, not X11. The buffer gets put into video memory by the compositor, not X11.

So why exactly are we keeping X11 hanging around? Why not get rid of it and halve the size of the display server code base, making it much easier to program against in the process? Why are we carting around a heuge amount of code that is of no modern relevance except to be able to claim that it is an X server? The maintenance burden of the current X server is too much and any thought of adding new capabilities horrific.

Otherwise, your arguments amount to, "No-one supports it yet so it's a waste of time." Good on Canonical for pushing it - if anyone has a vague chance of getting vendors to support it, it seems they might.

Re:Ubuntu to developers: "pound sand"

[Hatta]

Although the more detailed answer is that GTK/Qt apps will need recompiling with an updated library. If you use X11 directly, then you have more work - except that you can also run an X server within Wayland to support native X11 clients.

So what's to happen to our decades worth of work in innovative and configurable window managers? Am I expected to run an X server on top of Wayland just so I can keep the Fluxbox config I've grown accustomed to?

Choice of window manager is one of the best reasons to use a UNIX desktop. As I understand it, Wayland eliminates this choice entirely.

X11 needs replacing

Citation needed.

Re:Ubuntu to developers: "pound sand"

[Hatta]

Why not get rid of it and halve the size of the display server code base, making it much easier to program against in the process?

Can you do this without sacrificing functionality? If so, do it. If not, you're writing Wayland.

Re:Ubuntu to developers: "pound sand"

[Anonymous Coward]

network transparency. Without this, wayland can go diaf.

Re:Ubuntu to developers: "pound sand"

[nko321]

You can get an X server for Windows. Last I checked (years ago), Mac OS X was distributed with an X server on the install CD. I'm guessing that providing an X server in Wayland can't be hard... though admittedly, I've read no articles.

Re:Ubuntu to developers: "pound sand"

[jedidiah]

Even if I were OK with the MacOS style approach to dealing with remote desktop requirements, I would still be faced with the problem of my hardware vendor not supporting Wayland. Until that happens, Wayland a complete non-starter.

That driver might not "use X" but I still benefit greatly from it.

Re:Ubuntu to developers: "pound sand"

[serviscope_minor]

Have you ever tried them? They're shit, basically.

Native windows don't get X11 support, so can't be remoted, etc.

X11 apps don't integrate properly so things like drag and drop, and even copy/paste with something other than text between X and native programs doesn't work.

Oh, and you can't use any of the excellent window managers for X to manage your native windows.

Re:Ubuntu to developers: "pound sand"

[jedidiah]

Wayland apps are like Mac apps. They have no native remote desktop capability. You have to use a 3rd party hack like VNC to get such a feature.

I've seen how VNC runs on a Mac. Not impressed.

Running X on a Mac won't let me run iTunes across the network. The same is true of Windows.

Re:Ubuntu to developers: "pound sand"

[allo]

i am using ubuntu on the desktop, and are experimenting with distros on the notebook.
The latest one i installed there is the current fedora. Its a real nice distro.

Ah, and just for the record: of course with KDE both machines, because unity and gnome3 are both a mess.

Re:Ubuntu to developers: "pound sand"

[Hatta]

From the FAQ: "The Wayland architecture integrates the display server, window manager and compositor into one process."

The Wayland window manager will be built in. If you want to change your window manager, you have to change the display system itself.

Particularly egregious is the choice to have Wayland clients provide window decorations. That means that no matter what window manager you have compiled into Wayland, you can't centrally control the appearance of your desktop.

What happens if I want to use a Wayland distribution that provides a tiling window manager, but my apps are coded with window decorations? What happens if I want to use Fluxbox's built in window tabbing, but none of the clients support that?

Re:Ubuntu to developers: "pound sand"

[Anonymous Coward]

Welcome to *nix. You must be new here.

I rather like that the window manager, greeter, and locker are separate processes. I can replace them. I can mix and match according to my taste. I could even write my own if I wanted. This is the Unix way.

Example: you probably use some ubuntu-y, gnomey, kde kind of bullshit. That's fine for you but I have different tastes. So I use xdm to log in, wmaker to manage windows, and xscreensaver to lock my screen. Result: my X11 install is several hundred megabytes smaller than yours. But if I want your setup it's just a small apt-get away. This diversity, choice, and flexibility are why I like the *nix desktop in the first place.

But if I read you correctly, you want it to be all 1 big monolithic process? What is it, you're concerned about context switches between these processes on today's hardware? What the hell planet are you from? The X design has worked well for decades on much less powerful hardware than I have in my pocket today. X works fine on all of my devices, just like it did in the 90s, just like it does on my Nokia N900 running at 600mhz. I will be sticking with X for the time being.

Re:Ubuntu to developers: "pound sand"

[Medievalist]

When they moved the window control buttons to the left they had already gone off the deep end.

Man, I have to agree; that does seem to have been the shark-jump moment, doesn't it? Up until then it seems like Canonical had good solid technical or ergonomic reasons for nearly everything they did.

Re:Ubuntu to developers: "pound sand"

[GameboyRMH]

There were little hints that they were losing focus before that - replacing the old app manager GUI with the new Software Center garbage that only let you perform one operation at a time is one that stands out - but that was the first big thing they did horribly wrong and it's all been downhill from there.

Re:Ubuntu to developers: "pound sand"

[BlackSupra]

Great analogy!

Re:Ubuntu to developers: "pound sand"

[Anonymous Coward]

X11 isn't really the problem; the X.Org Foundation is. They have stopped listening to both the application developers and the end users. They seem to have the same problems as the Firefox development team, a few people in controlling positions with stronger wills than brains.

Re:Ubuntu to developers: "pound sand"

[Anonymous Coward]

"Your multiple monitors work because of Xrandr"
Thats is so odd! Because I use several monitor and don't use Xrandr. I must live in an alternate universe!

Re:Ubuntu to developers: "pound sand"

[Anonymous Coward]

The hardware vendors hardly support X now. I suspect if there were something better to come along, they might be more willing to write drivers.

Re:Ubuntu to developers: "pound sand"

[hairyfeet]

But Ubuntu is for home users, how many home users are running remote desktops? You've got all this stuff that frankly isn't need for the ones the OS is being pushed for, and which makes them system more brittle (see the classic rant from thom at OSNews about how X crashed when doing simple tasks for a loooong list of people having trouble with it in the home user space) so why not simply let X be for servers and Wayland be for home users? Choice is good, right?

Re:Ubuntu to developers: "pound sand"

[hairyfeet]

I'll get hate for pointing this out but moving the buttons without any real reason is a classic case of cargo cult usability where you change something to mimic something else without understanding the WHY it is the way it is. We are seeing the same thing in windows with the upcoming windows 8, where someone at MSFT said " Nobody buys our cell phones, people buy our desktops, if we make them both alike people will buy both!" without even bothering to find out WHY cell phones are designed the way they are (hint, its the screen size) and instead simply trying to mimic the look.

Re:Ubuntu to developers: "pound sand"

[Hatta]

But Ubuntu is for home users, how many home users are running remote desktops?

How many home users are using the command line? Why don't we rip that out too?

You've got all this stuff that frankly isn't need for the ones the OS is being pushed for, and which makes them system more brittle

What evidence is there that network transparency causes X to be "brittle"?

see the classic rant from thom at OSNews about how X crashed when doing simple tasks for a loooong list of people having trouble with it in the home user space

Sounds like a driver problem, not an X problem. He has a point in that X should be able to handle driver problems more gracefully, but I don't see what this has to do with network transparency. Can't we have both network transparency, server side window decorations, and robustness against driver faults?

why not simply let X be for servers and Wayland be for home users? Choice is good, right?

Fragmentation is bad for choice. If I want to use a certain app, I have to use the display platform that app is written for. And there is no bright line between server software and home software, so anyone who isn't an average user(and on average, almost everyone is not average) is going to be locked out of using some software.

Re:Ubuntu to developers: "pound sand"

[Dr_Barnowl]

I detect a note of sarcasm....

The way I see it, is .. what's the first thing you do when you close an app? Open another one.

In both old GNOME 2 and Unity, the button to open a new app is top left of the screen. So when you close an app with a top-left button, your pointer is now very close to where it needs to be to open a new one.

Windows puts the button to close an app, and the button to open one in opposite corners. Think of the extra mouse miles! I'm not sure what OS X does but it looks like you have to at least cross the vertical distance of the screen. Maybe that's why the fad for losing vertical resolution has come about..

Re:Ubuntu to developers: "pound sand"

[Dr_Barnowl]

Yeah, and not being able to install Synaptic to get those advanced features back is a real bummer. Oh, wait...

They made a choice to save the disk space so they could put in a more noob-friendly package manager. Which lets you buy stuff. And fund the development of the OS which the rest of us freetards get for nothing. Whereas for those of us that miss Synaptic, we have to *endure* typing one command. Or installing it with the Software Centre, if we like irony. That sure is 30 seconds I'll never get back...

Re:Ubuntu to developers: "pound sand"

[Anonymous Coward]

...perfect. Bravo, sir.

Re:Ubuntu to developers: "pound sand"

[Medievalist]

The Dvorak keyboard has not yet triumphed over QWERTY, so I think moving well-known buttons for efficiency is pretty close to a dead argument, at least outside the Apple fanbase.

In my case, the first thing I do when I close an app is close another one. And then, when all twenty or thirty SSH sessions are closed, I hit ctl-alt-delete, click shutdown and go get a beer. But that's obviously just one person's use case. Some people like cupcakes better - but I, for one, care less for them.

Re:Ubuntu to developers: "pound sand"

[lennier]

Ubuntu is the best thing to happen to Linux for all of us who dont use Linux. Its users have been faithfully beta testing for everyone else for the last 6 years :P

Just so. Except for about the last 3 years, we've been nagging Canonical as a beta group saying "hey, these changes you're making aren't working, nobody likes them, it was better in the previous release, pls fix" and they all come back with "WONTFIX. Ever. Your brain is wrong. I am as a god among developers! I went into SPACE! Muhahaha! Sincerely, M. Shuttleworth."

Re:Ubuntu to developers: "pound sand"

[lennier]

In both old GNOME 2 and Unity, the button to open a new app is top left of the screen. So when you close an app with a top-left button, your pointer is now very close to where it needs to be to open a new one.

In other words, the difference between clicking "Open New App" and "Close this other unrelated open window and destroy all my unsaved data in it" is about three pixels, or a half-millisecond twitch in your fine motor control finger muscles. That's not a feature.

Re:Ubuntu to developers: "pound sand"

[HuguesT]

Interesting analogy, but false.

X11 is more like a concrete-film roof: a brilliantly engineered, but difficult technology. It is also expensive as hell to build, impossible to work over, imposes the size of the house that can go under it rather than the other way around, it also really ugly, and installing the satellite antenna on top was hard and dangerous work. However, come hail or stone or even a small meteorite, this roof will withstand it all.

I'm on OSX for various reasons, but I find that my X11 server is always running. Why? because various pieces of software require it. Most crucially, distant access to Linux and BSD compute servers. NX compresses the protocol, and there is no other game in town at any price.

Re:Ubuntu to developers: "pound sand"

[Anonymous Coward]

why not simply let X be for servers and Wayland be for home users?

(a) Because you're completely ignoring the possibility of anything that is neither a server nor a home user. I get most use out of X11's network transparency at work, where the computer on my desk there is not a server. (But even at home, I rely on X11 network transparency, and also the ability to run multiple X11 servers in parallel, pretty much every day.)

(b) Because the goal of Wayland is to replace X11, not to complement it. It's bad enough that certain programs (*cough*GNOME*cough*) are now being written specifically for Linux kernels and can no longer be run on BSD systems; it will be a thousand times worse when programs are specifically being written for Ubuntu and will no longer run on Debian GNU/Linux.

Choice is good, right?

Choice is good for surface things: how I launch applications, how I switch between applications, what the window decorations look like.

Choice is absolutely terrible for fundamental system-level things like how programs talk to graphics hardware.

Re:Ubuntu to developers: "pound sand"

[Anonymous Coward]

Ubuntu is the best thing to happen to Linux for all of us who dont use Linux.

Indeed: Ubuntu is taking Linux and carefully removing all the Linux from it, so that people who don't want to use Linux will finally be able to use Linux without having to use Linux.

Except they don't want to use Linux in the first place, so they still won't. If software makers go along with Ubuntu's plan, those of us who did want to use Linux will be left without any Linux to use -- and it still won't be the year of Linux on the desktop.

What exactly is the point of this, again?

Re:Ubuntu to developers: "pound sand"

[M1FCJ]

But Ubuntu is for home users, how many home users are running remote desktops?

How many home users are using the command line? Why don't we rip that out too?

Don't give the bloody idiots any ideas! They might act on it!

Re:Ubuntu to developers: "pound sand"

[M1FCJ]

and Fedora is different in which way... I have two words. Gnome 3.

Re:Ubuntu to developers: "pound sand"

[M1FCJ]

I don't know, using the good old TWM all I had to do was click on the screen and then select xterm and that was that. I could also browse through the options but never had the urge to drag my trackball around the desk to get to the top (or the bottom) left (or right) corner and it always worked fine. Try it one day, you might like it.

Re:Ubuntu to developers: "pound sand"

[GameboyRMH]

I'm not talking about Synaptic, I'm talking about the old applications manager. You used to access it by going to Applications -> Add/Remove Applications. The package name was gnome-app-install.

Re:Ubuntu to developers: "pound sand"

[markjhood2003]

I've been reading all the comments, and it wasn't until I read the parent here that it finally hit me: Wayland integrates the window manager.

This is an amazing leap backward. And on top of that, clients must provide their own window decorations? I can't even imagine what this will do to UI consistency, usability, and appearance.

Re:Ubuntu to developers: "pound sand"

[hairyfeet]

Uhhh...yes please? frankly CLI has become the all purpose crutch in Linux for several years now and needs to go the way of disco. Can't design a GUI worth shit? CLI. Can't build a driver worth a shit? Well a CLI fix will patch that up! Sound problems, network problems, get thrown into single user mode because the driver took a shit? CLI CLI aaaand..CLI.

You could completely remove CLI from Windows and OSX and I bet my last dollar so few people would notice that it wouldn't even make page 3, why? because they do not NEED CLI just to use the damned machine, that's why! There is a REASON why Android doesn't come with CLI you know, its not needed.

The fact that your OS can't even function without a 1970s throwback UI says more about the OS than it does the users friend. CLI is only good for TWO things, neither of which is useful to the average home user. 1.-Scripting, and 2.-Repeating the same action over and over. Do you honestly think users are using WGET to fetch web pages and send them to an email daemon with scripts like RMS?

Either join the 21st century with the rest of us or don't bitch when nobody uses your OS, it is THAT simple. When people would rather steal the other guy's product, last numbers i saw had it in the millions BTW, than take your OS for 100% free? Well if that don't smack you upside the head with the cluebat than nothing will. pretending the users are gonna "embrace the POWER of CLI" like its the damned force is simply batshit and is about as likely to happen is my flying south for the winter by flapping my arms really hard. Accept and either move up or accept last place, your call. but until you get with the 21st century you might as well quit that "year of the Linux desktop" crap because it ain't EVER gonna happen.

Re:Ubuntu to developers: "pound sand"

[Anonymous Coward]

also the ability to run multiple X11 servers in parallel, pretty much every day

I call bullshit. You can't run multiple X server at the same time because they step on each other everywhere because they all expect to be the only X server running, and there's no easy way to securely hand off devices between X servers (or at least it hasn't been coded yet, even though they have been making strides to get there).

Re:Ubuntu to developers: "pound sand"

[Anonymous Coward]

Sadly, TFA is misleading, or at least is misleading as presented in the post. Native Wayland applications will, indeed, need changes.

On the other hand, we're not aiming to have native Wayland applications running; we're aiming to wedge a Wayland compositor under the existing X server. As far as devs are concerned, nothing changes. As far as users are concerned, nothing changes - except that login / logout / lock screen transitions get nicer.

Of course we're not asking developers to rewrite all their apps. Whenever you think “Are the Ubuntu developers insane? That's clearly stupid!” there's at least a reasonable chance that we're not doing what you think we're doing. By and large we're not insane :).

Re:Ubuntu to developers: "pound sand"

[unixisc]

At this point, both Qt5 and Unity are being written to include Wayland support. Why would they bother if Wayland already has and only allows one Window manager? Or is there something I'm missing?

I know what X looks like when run just by itself. What does Wayland look like?

Re:Ubuntu to developers: "pound sand"

[RogerWilco]

Over here in radio astronomy, there actually are quite a few people who still use Linux or the X11 in OSX to run old unix software. I mean stuff like Miriad, built on the original Xaw/Athena in the middle of the eighties.
I don't know their code in detail, so I can't say if it does bypass some of the X11 functions, but given that is was developed mostly the X window system reached version 11, I think it's pretty basic X.

There's also AIPS, which is even older. I don't think it knows about X, it uses a serial stream of bytes, where each byte is a pixel, to display images on "AIPSTV". This is a program that still thinks in input/output/program tapes and has no concept of a file system beyond "tape library".

What I learned when I ventured into radio astronomy, is that a lot of the software in use is still seventies and eighties FORTRAN code. Only recently, with the newer ALMA and LOFAR telescopes coming online, did more modern packages like CASA (1991) gain any traction.

Yes 2 decades old is considered "new" in radio astronomy.

http://www.star.bris.ac.uk/mark/AIPS.html

Re:Ubuntu to developers: "pound sand"

[RogerWilco]

Ad that's why so many find it hard to replicate the success of Apple, they don't understand that Apple has a very good reason for everything they do, even if it sometimes isn't the best idea. Even in the old MacOS the UI design was very good. I remember the first time I sat behind a Mac and was more productive within 15 minutes than the WinNT system I was used to.

Technology and design wise Apple is one of the best. What most people don't like them for, is the fierce way they defend their image and brand. That's where they get really aggressive and a lot of people don't like that.

MS tries with Metro and the ribbon and such, but I don't find it nearly as good as the UI designs that Apple puts out.

Re:Ubuntu to developers: "pound sand"

[Barefoot Monkey]

From the FAQ: "The Wayland architecture integrates the display server, window manager and compositor into one process."

From there it continues:

You can think of Wayland as a toolkit for creating clients and compositors. It is not a specific single compositor or window manager. If you want a different window manager, you can write a new one.

This may sound like a lot of work, but one of the key points about Wayland is that the boilerplate code to a Wayland compositor is comparable or less than the X boilerplate involved in becoming an X window manager and compositor. Bringing up EGL and GLES2 on the Linux KMS framebuffer and reading input from evdev can be done in less that a thousand lines of code. The Wayland server side library provides the protocol implementation and makes it easy to put the pieces together.

So basically you can use any window manager provided that the manager is written to support Wayland, just as you can use any window manager on X provided that it supports X.

Re:Ubuntu to developers: "pound sand"

[tehcyder]

Yes 2 decades old is considered "new" in radio astronomy.

So what? Actual scientists care about getting accurate results, not being on the right side in some fashion war.

Re:Ubuntu to developers: "pound sand"

[ancienthart]

X11 isn't really the problem; the X.Org Foundation is. They have stopped listening to both the application developers and the end users. They seem to have the same problems as the Firefox development team, a few people in controlling positions with stronger wills than brains.

And the same went for the Gimp team until about 3-4 years ago. I'm glad that they were able to get someone who was willing to restart work on GEGL, because I'm actually enjoying the latest gimp releases again.

Re:Ubuntu to developers: "pound sand"

[Hatta]

Sure, all it takes is a recompile. And you still can't set your window decorations with your window manager, which is traditionally half the job a window manager does. That's a dramatic loss in flexability.

Re:Ubuntu to developers: "pound sand"

[Hatta]

The CLI is, and will always be the best way to interact with computers. Why? Because people have evolved to interact with language. CLIs are fundamentally more expressive than any GUI could ever be.

You can have your toaster OS.

Re:Ubuntu to developers: "pound sand"

[Barefoot Monkey]

Can you confirm that's actually the case? I don't know much about Wayland's technical details, but it's such a dramatic loss in flexibility that I'm inclined to suspect this being a complete misunderstanding. I can't see how code that runs on the compositing and window-management layer would be unable to add decoration unless it is restricted to an extremely limiting API (hopefully not what is happening), and even if that were so then wouldn't it be possible to have a decorator using the same reparenting technique that window managers use on X? And wouldn't it be possible to have window managers as precompiled shared objects which could be swapped during runtime?

I guess I should look into Wayland and try to answer those questions for myself. I'd hate to be unable to change window managers on the fly or have apps needing to decorate their own windows.

Re:Ubuntu to developers: "pound sand"

[Wolfrider]

--I'm just curious, is this true for Cygwin as well?

Re:Ubuntu to developers: "pound sand"

[DeathToBill]

God, don't I know it - still supporting people writing new code in *Fortran 77* FFS. In Bristol, as it turns out.

But that's a reason for backwards compatibility, not to refuse to change. Wayland explicitly supports existing X clients by running an X server, either rootless or windowed, as a Wayland client.

What's the problem here?

Re:Ubuntu to developers: "pound sand"

[DeathToBill]

Yes yes yes. Because you can write a far simpler X server as a Wayland client. It doesn't have to deal with anything to do with drivers or modes or depths - all it has to do is receive X11 traffic and translate it into drawing calls.

Re:Ubuntu to developers: "pound sand"

[DeathToBill]

So we'll never try anything new ever again because no-one supports it yet?

Re:Ubuntu to developers: "pound sand"

[hairyfeet]

I hate to break the news to ya, but lets gets some facts straight, mmmkay? First of all CLI doesn't give you mystical gonad powers, second of all CLI is a GUI not any kind of mystical I/O, its just a very VERY primitive GUI, finally here is a nice article that points out better than I ever could why your CLI is a pile of old cat turds not that you'll read it.

In the end, know what it comes down to REALLY, I mean what is really at the heart of it all? Losers. CLI has become the haven of the maladjusted loser, because it gives them the illusion, and that's all it is, merely an illusion, of being better/smarter/more leet than someone else. And THAT is why you desperately hang onto a GUI everyone else abandoned over 20 years ago, not because it makes ANYTHING better, but precisely because it does not. Linux is the bizzaro-world where the more fiddly and PITA you can possibly make it the better because it "proves" that you MUST be smarter/better/more leet by virtue of making the damnd thing work. Well to stick that final needle in your bubble copypasta into a CLI doesn't make you leet, it makes you a script kiddie.

So enjoy the 1970s Disco Stu, the rest of us will laugh our collective asses off and enjoy our nice GUIs and smirk.

Re:Ubuntu to developers: "pound sand"

[badkarmadayaccount]

The head of the Wayland project is also lead developer of X11, on last year's linux.conf.au talks in Brisbane he detailed his reasons. I agree with Ubuntu's move, I don't agree with most everything they've done the last 5 years.

Re:Ubuntu to developers: "pound sand"

[badkarmadayaccount]

The apps use a toolkit like Qt, which usually sets decorations, and can be configured like the wm. IOW, just edit a different conf file, or equivalent. If the distro does it's job, the user won't notice the difference. What worries me is porting X11 wms. I hope a code generator is in the works.

I have long dreamt of the day

[kiriath]

That X would be replaced... and now after all this time? I'm not sure if I'm happy about it =\ It is very interesting to see that there is an effort in this area though, to be quite honest this is the first I am hearing of Wayland. Ubuntu seems to favor having one good release, and one less stable release. You have to get your bug fixing done somehow right?

Re:I have long dreamt of the day

[Qwavel]

I have no comment on 'wayland good' versus 'wayland bad', but it is certainly a known quantity and it has been waiting in the wings to replace X for a while.

As you said, the dream of replacing X has been around for a very long time. No one has done it because it is a ton of work and because the changes are bound to piss off some developers and users (see "pound sand" post above).

I'm impressed that the Ubuntu folks are going to take this on and I wish them well. If they succeed then the rest of the distro's will probably follow suite.

Re:I have long dreamt of the day

[kriston]

I agree. Wayland needs to happen. We've wasted so much time, effort, and knowledge keeping X Windows up and running. I sometimes think about how much further along desktop Linux might be if we threw off the shackles of X Windows years ago. There's a reason Android and MacOS do not use X Windows.

Re:I have long dreamt of the day

[Anonymous Coward]

The Ubuntu folks aren't developing Wayland. Wayland is being developed pretty much entirely by Intel employees. Ubuntu is just planning to integrate it.

Re:I have long dreamt of the day

[Anonymous Coward]

There is no such things as "xwindows" there is the "X Window System"

Android uses the framebuffer which sucks performance wise compared to X

The XiG implimentation of X with open group X11R6 (It is provided with XiG CDE and you can compile it really easily with icc) is ridiculously fast.

Xorg is a pretty crap implementation of X (As are most of the vendor ones Xsun / IBM's / HP's)

X itself cannot be that crap or the situation that exists whereby the old r200 ati drivers are (An order of magnitude) faster under XiG X than under Windows.

For full screen opengl X is bypassed cannot really think of much else that really needs the performance. (Don't care about wobbly windows or any of that dumb stuff). I use a few urxvt's / the odd uxterm and a browser.

Re:I have long dreamt of the day

[serviscope_minor]

That's an awful lot of hyperbole in one post with no actual information.

The thing that would be best would be X12, not scrapping X11 completely. There's lots of good and useful things in X, which Wayland doesn't have.

Oh, and by the way, please, if you want OSX or Android, you know where to buy them so go and do so. Stop trying to turn my very nice desktop system into an inferior commercial alternative.

Re:I have long dreamt of the day

[Anonymous Coward]

That's an awful lot of hyperbole in one post with no actual information.

*Any*one who says this has simply not been paying attention for very long, if at all.

X has been an albatross for almost 25 years now. Everyone who's ever attempted to do anything remotely GUI related knows it.

Re:I have long dreamt of the day

[markjhood2003]

Android doesn't use X11 because it's intended to run on low-power, memory-constrained devices.

MacOS doesn't use X11 because it's a consumer OS. Consumers typically don't set up networks of desktop machines in their homes and don't expect to be able to run native applications on remote machines while displaying and interacting with them on their local desktops.

X11 is incredibly useful for engineers and technical people who use multiple Unix and Linux hosts to get their work done. Any other environment feels like working in a closet. X11 is complicated because the requirements are complicated. That's no reason to throw out 30 years of development and refinement.

I guess the inevitable conclusion is that Ubuntu and Wayland developers don't care about engineers, professionals, and dedicated hackers. Good luck competing with Apple and Microsoft! In the meantime your core base will move on.

Re:I have long dreamt of the day

[ChunderDownunder]

There's a reason Android and MacOS do not use X Windows.

Well in the case of Android, Wayland is coming!

This implementation doesn't use share any Xorg legacy but rather cobbles together an implementation based on the graphics APIs exposed by the Android SDK.

An eventual goal might be to replace the display technology - Google proprietary (aosp) SurfaceFlinger with a Wayland compositor. Thus with, say, CM13 your tablet would be able to run Android apps seamlessly alongside KDE Plasma apps. On the desktop, Android apps would thus interact with Unity on Ubuntu Wistful Wombat. ;-)

Re:I have long dreamt of the day

[gnapster]

Everyone who's ever attempted to do anything remotely GUI related knows it.

On the other hand, anyone who's attempted to use any GUI, remotely, swears by it.

Re:I have long dreamt of the day

[Anonymous Coward]

You must be new to open source...

Re:I have long dreamt of the day

[Wolfrider]

Actually I swear by Nomachine NX - it has the best display speed EVAR for remote X connections.

It has sadly fallen out of current development for Freebsd, however - or I would have it installed on my ZFS backup server. :(

would have got first post....

[sce7mjm]

but i'm still waiting for x to start...

Re:would have got first post....

[Anonymous Coward]

Should have used Lynx...though it probably won't handle the wonky Slashdot code.

Re:would have got first post....

[Osgeld]

links2 -g works fine with slashdot and no X though you might want to load GPM beforehand cause tabbing though a page sucks

wayland is a bad choice

[Anonymous Coward]

Ubuntu is sparking a new 'unix war', dividing the linux ecosystem. It first pushed hard for its own Unity now with Wayland that breaks all current X apps. Theyr'e only in it for themselves.

Without X we will lose network transparency among many other great features. Let's not even mention the lack of gpu support to say the least.

Re:wayland is a bad choice

[Anonymous Coward]

I seriously doubt it will fracture linux any more than it already is. X will function as an add-on to wayland, so older apps and apps that need some specific X functionality will still be supported.

Re:wayland is a bad choice

[Anonymous Coward]

It isn't Linux most of us are worried about. The Linux people can do whatever they want to themselves. It's the consequences to the other UNIX like operating systems.

Re:wayland is a bad choice

[vlm]

Without X we will lose network transparency among many other great features. Let's not even mention the lack of gpu support to say the least.

VDPAU? They don't mention it, so I assume its going bye bye. Its kind of funny in that everything I use X for is everything Wayland opposes.

Just this weekend I was ssh -X into my mythtv backend to run the config program to add another capture card running X over the network, so my binary only nvidia cards using VDPAU have more to look at. I never use stupid animations and other 3-d foolishness on my desktop because I'm unimpressed; its the 2010's version of the 1980's demand that all desktop publishing projects must use a minimum of 50 different ugly fonts to show off that you can do it. I prefer my content to be my primary interest, not my window animations. Of course all of that is impossible over wayland. Thanks guys for exactly what I don't need! Maybe you could make it eink and touch screen only, just to annoy me further?

Re:wayland is a bad choice

[Anonymous Coward]

X will function as an add-on to wayland,

Yes, but this breaks the current seamless integration of remote and local apps that we have today. Presently, this works even for OpenGL based applications (although obviously slower over a network - but they run).

Seamless remote/local app integration is a cornerstone of Unix-based systems going back to at least the 1980's. Breaking this is unacceptable.

Re:wayland is a bad choice

[Anonymous Coward]

Unity is just gnome-shell, and wayland will be backwards compatible with X.
Parent should be modded -1 Troll

Re:wayland is a bad choice

[Dog-Cow]

Unity is not gnome-shell.

Wayland is not compatible with X.

Any other crap you care to spew?

Re:wayland is a bad choice

[lindi]

We don't currently have seamless integration of remote and local apps. For example, there is no audio or freedesktop.org notifications for remote applications. I personally use xpra to get this seamless integration. Even though the name has "x" in it is not fundamentally tied to X protocols and will probably be easy to port to wayland. The data transmitted over network is compressed bitmap.

Re:wayland is a bad choice

[unixisc]

I dunno about GNOME3, but Wayland is certainly being embraced by Qt5 and is a target for KDE5, so it's not true that it's an Ubuntu only initiative. What I am curious about is whether there are any plans to get Wayland into the FreeBSD family of unixes - like FreeBSD, PC-BSD, DragonFly BSD, et al? Or into Minix?

Re:wayland is a bad choice

[Anonymous Coward]

Troll much?

How about people with local home networks of 2 or 3 machines? I use it all the damn time - like every single day. I run apps from a big powerful central server and display them over "ssh -X" to my low power laptop.

I know you're just trolling, but people need to realize that people DO use "ssh -X" all the time. There are plenty of other repliers to this thread who have said they do as well.

Re:wayland is a bad choice

[Anonymous Coward]

Wow, man, you're really on fire today.

Re:wayland is a bad choice

[Anonymous Coward]

You could, you know... just not use it. Of course complaining like a little shit is so much more satisfying.

He's not complaining about Wayland existing. He is complaining about having it forced down his throat by Ubuntu.

Since it goes against your views, he's a complaining "little shit"? Is he supposed to take it lying down and let things progress the way he doesn't like? Sounds a little hypocritical. It is like telling GNU to quit complaining and if they don't like commercial software then don't use it. No need to advocate more free software. Of course ridiculing people is so much easier than responding to their comments rationally and taking their opinions seriously.

I think you should have been the one to keep one's thoughts to himself. At least do like everyone else and provide information that may eliminate some of the GP's fears.

Re:wayland is a bad choice

[Anonymous Coward]

You have absolutely no clue what you are talking about. Do you honestly think analysis of large (say 1 petabyte) dataset is going to be done on your lap/desk top? Do you honestly think that a comparison of multiple large datasets can be done with your lap/desk top? Try running IDV/NCL/R/MET on three WRF data sets with anything under 24cpus and 48gb of memory. Go back to something hard for you like creating new themes for KDE.

Re:wayland is a bad choice

[Anonymous Coward]

Yes, but this breaks the current seamless integration of remote and local apps that we have today.

Sort of. The Wayland devs say that the right place for this is "in the widget toolkits" - aka, QT, GTK, and so on. But that of course means we will end up with 3 or 4 different and probably incompatible solutions for network transparency, where today we have one.

X11 has a lot of problems, but Wayland is going to have its own.

Re:wayland is a bad choice

[Anonymous Coward]

Wayland is compatible with X; it was one of the primary design considerations, and a prominently mentioned feature on the wayland.org website. It's done by running a nested X server.

Re:wayland is a bad choice

[Anonymous Coward]

They aren't removing X. X can still run in wayland just like X can still run on OS X.

Re:wayland is a bad choice

[Gordonjcp]

Does anyone in the real world actually care about network transparency?

Re:wayland is a bad choice

[jedidiah]

> It's a dead, dead, and dead feature

I seriously have to wonder if any of you people have jobs or if you're just unemployed and live in your mother's basement. If you had been in a Windows or Unix shop in the last 10 years you would have seen examples of both X and RDP.

If anything, the world is catching up to where Unix used to be. The demand for remote desktop functionality is actually INCREASING rather than decreasing.

Re:wayland is a bad choice

[serviscope_minor]

Does anyone in the real world actually care about network transparency?

You are part of the problem.

The linux ecosystem used ot target niches well, and not unnecessarily restrict actions of people who have unusual needs.

Now it's grown we get too many people who (like you) assume that if you don't personally do something, or if ti's only done by a relatively small fraction of the ecosystem, then it's unimportant.

I use remote X often. I also use NFS home directories often, even though gnome and firefox seem determined to break that as much as possible.

Re:wayland is a bad choice

[Anonymous Coward]

Try running IDV/NCL/R/MET on three WRF data sets with anything under 24cpus and 48gb of memory.

And everyone should be clunking along with the ancient X11 just that we could support some extremely special setups like yours? The general benefits that Wayland offers are much, much more important.

Re:wayland is a bad choice

[allo]

wayland can run on a xserver, and a xserver can be a wayland client. so you're wrong.

Re:wayland is a bad choice

[thetoadwarrior]

So Gnome was bad for being released after KDE? One of the great things about open source is that you can go off and do you own thing and someone doesn't like it they can go elsewhere.

I don't know why some people are so afraid of choice and change.

Re:wayland is a bad choice

[shutdown -p now]

I think GP's point is that RDP remoting architecture (which is perfectly doable on Weyland) is better than X11 model.

Re:wayland is a bad choice

[shutdown -p now]

Now it's grown we get too many people who (like you) assume that if you don't personally do something, or if ti's only done by a relatively small fraction of the ecosystem, then it's unimportant.

Those who believe that it's important (for them) can go ahead and further maintain X11 and develop apps for it. That's what FOSS is all about, no?

Re:wayland is a bad choice

[Anonymous Coward]

Right, because developing and deploying Wayland on Linux with the option of running full-blown X on top immediately prohibits non-Linux Unix-like operating systems from compiling, installing, installing by default, using, and continuing the development of X.

What are you so worried about if you're not running Ubuntu?

Re:wayland is a bad choice

[Anonymous Coward]

Actually, the data transmitted over the network varies based on how you tell XPRA to handle that. It can do X forwarding, VNC, and RDP.

Re:wayland is a bad choice

[spitzak]

I think you are confusing what will be done by the widget toolkits. They will draw the window borders (just like the draw the buttons and scrollbars and text fields and a hundred other things that are MUCH harder than window borders).

Remoting will be done by a remoting wayland server. It will send the window images over the network to a remote display.

Re:wayland is a bad choice

[makomk]

Not just VDPAU. The entire closed source NVIDIA driver isn't usable with Wayland and probably never will be. Wayland requires developers to use the same KMS framework as the open source drivers (impossible for closed source drivers due to licensing issues), the same DRI2 buffer management and command submission code (effectively impossible because NVIDIA's driver codebase apparenly doesn't work in the way DRI2 assumes it does), and even that might not be enough.

Re:wayland is a bad choice

[Gordonjcp]

So, use X then. Most people (myself included) don't want to know how the stuff gets onto the screen, and don't see the attraction in being able to run xclock on a computer in Venezuela and have the display pop up on their local screen.

I don't know if you remember what X was like before Xorg? Or indeed, even earlier than that, when (in the early 90s) you had to sit down with the workshop manual for your graphics card to work out exactly what to poke into the registers so you could get a display *at all*, never mind avoiding modes like 749x376 at 35Hz. All that is gone now, and good riddance!

Re:wayland is a bad choice

[lennier]

So Gnome was bad for being released after KDE?

No, Gnome managed to be bad all on it's own.

Re:wayland is a bad choice

[M1FCJ]

Go on... Tell me, how is it any better than seamless integration of a single app using a method which worked 25 years ago and still functions perfectly? Here, $dayjob is spent on doing SSH tunnels for X and then running some X11 apps. $hobbytime spent on doing more or less the same with the home server & the laptop. VNC or NX are workarounds for high latency low bandwidth networks.

Re:wayland is a bad choice

[shutdown -p now]

My understanding is that modern (i.e. Gtk & Qt) apps actually don't use the original method anymore - they effectively exchange composed bitmaps for entire top-level windows on the wire - and because X11 was not really meant to work that way, it ends up being slower than VNC, much less RDP. So it's more like taking a method which "still works" by not using 95% of the original method, and stripping that 95%.

Re:wayland is a bad choice

[Anonymous Coward]

It's true that they exchange images on the wire, but they also utilize the XDamage extension to X, so they only have to transmit the parts of the bitmap that have changed, greatly reducing the amount of information necessary to draw the window.

Re:wayland is a bad choice

[shutdown -p now]

It's true that they exchange images on the wire, but they also utilize the XDamage extension to X, so they only have to transmit the parts of the bitmap that have changed, greatly reducing the amount of information necessary to draw the window.

Well, that's kind of an obvious optimization in any such protocol - RDP does the same exact thing (no idea about VNC, I haven't used it much). That's still not incompatible with Weyland design, though.

Re:wayland is a bad choice

[serviscope_minor]

I don't know if you remember what X was like before Xorg?

Yes, I do.

you had to sit down with the workshop manual for your graphics card to work out exactly what to poke into the registers so you could get a display *at all*, never mind avoiding modes like 749x376 at 35Hz.

You're confusing the XFree86 implementation with X11. On an SGI or whatever, you know where it was vendor supported, you plugged in everything and it just worked out of the box.

All that is gone now, and good riddance!

Exactly. So, whjat's that got to do with Wayland?

Re:wayland is a bad choice

[serviscope_minor]

That's what FOSS is all about, no?

No.

You seem to be confusing one of the main benefits of OSS (you can fork if you have to) wiht the idea that it's fine for people to needlessly mess things up. Su're they're free to, and I'm free to fork, but OSS isn't about people screwing up. That's patently ridiculous.

Re:wayland is a bad choice

[lindi]

I think you are talking about winswitch now. I don't think xpra has VNC support.

Trust

[Anonymous Coward]

Who in their right mind would trust the Weyland-Yutani Corporation given what they did to the colonists on LV-426?

Re:Trust

[lennier]

Who in their right mind would trust the Weyland-Yutani Corporation given what they did to the colonists on LV-426?

Exactly! The Hadley's Hope debacle demonstrates that you might not always need a fully network-transparent protocol with the ability to remote-administer a site from orbit - but when you need it, you really really need it.

Unsurprising

[greg1104]

Is there anyone who still thinks the Ubuntu release team prioritizes either usability or low number of bugs now? That's a serious question; I have no idea why this is considered a novel or even notable thing at this point. New Ubuntu release, leading edge software that's not ready for prime time is included, the release is at best beta quality software by any reasonable standard. Same story in every release going back to at least the 8.04 PulseAudio debacle.

Re:Unsurprising

[vlm]

Maybe its trying to be modern art? Not supposed to be useful, or appealing, or beautiful, or traditional, or deeply thought provoking, just intended to momentarily inflame some passions or inspirations as people walk by on their way to doing real work on Mint and Debian and android and osx etc? A feeling, rather than a thought? Like gastrointestinal pain feeling vs the thought of refactoring a data parsing and importation routine? Of course those two are probably more closely related than you'd wish, but the point stands?

There's nothing inherently wrong about any work of art. You can be wrong about trying to "use it" for certain tasks, or maybe wrong to use it at all to do anything. But as a piece of art it can be interesting to look at, as a ... escapist form of fine art, before returning to the real world to do real stuff with real tools.

I don't particularly like Picasso's work. That it exists has no impact on the paper in my real world life, my junkmail, my reports, my old fashioned printed books...

Re:Unsurprising

[DoofusOfDeath]

Well there is this constant tension when developing software in a competitive market. You want to release stuff that's as refined as possible, but you might lose users when competitors' products evolve faster than yours. So it's a constant attempt to balance innovation and refinement.

That being said, I do think Ubuntu has gotten the balance wrong over the past few years. At least speaking for myself, the lack of polish (especially desktop environments and graphics drivers) has cause me more distress than the distress I would have felt from slightly more stale packages.

Re:Unsurprising

[CapineiroCapaz]

Who is forcing you to upgrade from 12.04 LTS? It will receive security fixes for years.

Re:Unsurprising

[greg1104]

Wait, you think I installed the steaming pile that is 12.04? That's pretty funny. I limped along with 10.04 until Debian Squeeze was released last year, and that was it for Ubuntu on my systems. I wanted no parts of Unity in 2011, same as I don't want Wayland in 2012.

Regardless, the "LTS" in Ubuntu's release titles is a joke. None of the bugs I ran into for 10.04 "LTS" were resolved via any means except "fixed in version ". When Ubuntu has a large and active backporting team worrying about their stable releases, such as RedHat's, then they can credibly use the LTS description.

Re:Unsurprising

[Anonymous Coward]

If you need to upgrade your apps, such as to obtain some needed feature (e.g, we need some new stuff coming online in Blender), getting new apps working with increasingly old versions of Linux quickly becomes an impossible nightmare. They aren't in the repos, they no longer build from source on that crufty OS - it's an unreasonable proposition.

Re:Unsurprising

[Anonymous Coward]

None of the bugs I ran into for 10.04 "LTS" were resolved via any means except "fixed in version ".

This is the problem with LTS releases in a nutshell. They don't actually fix bugs in the LTS releases. They just let you know that it was fixed for the most recent non-LTS version.

Re:Unsurprising

[JonySuede]

I don't particularly like Picasso's work. That it exists has no impact on the paper in my real world life, my junkmail, my reports, my old fashioned printed books...

Cubist spam is a life changing event, I pity you as you missed one of the best things that life has to offer!

Re:Unsurprising

[Zaiff Urgulbunger]

Who is forcing you to upgrade from 12.04 LTS? It will receive security fixes for years.

I'm stranded on 10.10 whilst I try to get 12.04 working... but I'm still getting random crashes with Unity 3D vs. nVidia. No idea if Canonical ever intend to upgrade "nvidia-current" (295.40)... so I've manually removed it and installed "nvidia-current-updates" (295.49), but I've still had a crash* so it seems the next best option available to me is the X-Updates PPA. So much for 12.04 being an LTS release though. :/

* by crash, I mean I get kicked out to the login screen.

Developers won't meet fictional deadline?

[Anonymous Coward]

I read the article and the Ubuntu Wayland wiki. The Ubuntu developers have not set any deadline, they don't appear to have set a specific goal, they're just continuing their work on Wayland as usual. The article appears to have just pulled the release target out of the author's arse and then claimed the developers won't make it in time. From the linked page:

"When will Wayland become the default on Ubuntu?
This has not been decided. This decision will be made at a future Ubuntu Developer Summit (UDS)."

So apparently the developers won't reach their goal that they haven't set. How is this a story?

Re:Developers won't meet fictional deadline?

[Anonymous Coward]

Quantal Quetzal is quantal. That's why.

Re:Developers won't meet fictional deadline?

[daver00]

I dunno, it sparked a pretty interesting flame war here on slashdot?

Huh?

[Impy the Impiuos Imp]

> Ubuntu Still Aims For Wayland In Quantal Quetzal

Blort?

Quantal Quetzal Quisach Haderach

[Picass0]

You know what I hate about Ubuntu? Sandworms.

Re:Quantal Quetzal Quisach Haderach

[Thud457]

You know what I hate about Ubuntu? Sandworms.

Beetlejuice BEETLEJUICE BEETLEJ mmph!



really /.? that's some inept markup handling there...

Re:Quantal Quetzal Quisach Haderach

[Anonymous Coward]

It's spelled "Kwisatz Haderach".

Though, since this *is* Ubuntu, I guess you could say something like "Quantal Quetzal Qizarate." ...

(The source must flow!)

Re:Quantal Quetzal Quisach Haderach

[Picass0]

I googled it. Blame google.

Bling

[spivster]

I've tried several releases of Ubuntu over the years, only to give up in frustration at all the configuration needed just to (for example) get wireless to work. Finally, with Precise, Ubuntu "just works" (pretty much) right out of the box. Per TFA, Quantal will rely on fallbacks because AMD Catalyst and NVIDIA binary Linux graphics drivers won't work with Wayland. Huh? Why shoot themselves in the foot when they've finally gotten things right, just for something that's primarily cosmetic?

Re:Bling

[CanHasDIY]

I've tried several releases of Ubuntu over the years, only to give up in frustration at all the configuration needed just to (for example) get wireless to work. Finally, with Precise, Ubuntu "just works" (pretty much) right out of the box.

Yea, unless you have a Broadcom wireless card, like I do...

Know what really sucks about that? The wireless was working fine prior to the Precise upgrade.

Looks like one step forward, two steps back to me.

End of network display?

[Compaqt]

That would be sad.

But beyond that: there's one big deficiency of current X applications--if the X server dies, so do all graphical programs.

That's quite surprising when you think about it.

After all the graphical programs are X clients. Why would a client up and die just because some server died?

Does your browser die when a webserver dies?

And please, no pretending that X on Linux doesn't crash. It does, and this is the 4th time I've restarted this laptop today. Hanging hard with VirtualBox.

To sum: If the graphics server crashes, I'd like to see it automatically restart with Upstart, and then the clients automatically reconnect.

Re:End of network display?

[Anonymous Coward]

Because then anyone with the access and know-how to crash your X server could effectively hijack your session. It is safer and more secure for X clients to assume that a new session is... well... a new session.

Re:End of network display?

[csubi]

X seemed pretty stable for me over the last 5?6?7 years, it was not the bottleneck / lowest common denominator for the usability of the distros I used over the years.

Does your browser die when a webserver dies?

Just don't start your webserver from a terminal you opened while logged in to X.

You know, CTRL+SHFT+_1-6_, log in and start your webserver. Or have it started at boot time. Or put it into background.

Re:End of network display?

[Anonymous Coward]

Let's not forget, network transparency is useful when two people need to use an application that you only have one hardware-tied licence for. (Obviously only one person using it at a time.)

Re:End of network display?

[Anonymous Coward]

I can't think of a reason why widget toolkits couldn't do this. I think they can (and mostly do) maintain all the information about their widgets and windows they need to reconnect to the X server and recreate all the resources (windows, pixmaps, etc.). They just don't.

Re:End of network display?

[vlm]

To sum: If the graphics server crashes, I'd like to see it automatically restart with Upstart, and then the clients automatically reconnect.

I encourage my competitors to implement this, etc etc. You know what would be hilarious? Your buggy hardware (I haven't had a X crash in, I don't even know, certainly more than a decade) combined with root logged in and doing some admin GUI thing. X crashes. Logs itself back in. Before the user gets to interact, the GUI admin thing crashes X again. Repeat infinitely. Oh no problemo just log in as root to break that loop... errr... thats not gonna work because its root who's stuck in the loop. Wipe the hard drive and reinstall?

In ye dark ages of firefox I have run into this, where bringing up some cruddy coded web page full of cruft crashed FF (which admittedly should have failed gracefully, but still, cruft is cruft) and then on restart FF asks if I wanna restore my session. Oh heck no, that's just gonna crash FF again!

On the other hand, given basically bug free client and server software, you've just described the behavior of NFS, AFS, probably a couple other networked filesystems. I've never had to reboot a client because of a server problem in NFS or AFS. The server comes back online and all is well as if nothing happened.

Re:End of network display?

[Anonymous Coward]

I can't think of a reason why widget toolkits couldn't do this.

There are many, many widget toolkits, from the "heavy hitters" like QT to weird one-off toolkits specific to some app. They will NOT all do this, so it doesn't matter if they can. We will be losing network transparency, a thing many of us NEED.

Re:End of network display?

[Anonymous Coward]

The Wayland folks say, "You can still run an X server app in Wayland".

Of course, this completely misses the point that this DOES break network transparency of apps.

Re:End of network display?

[TheSpoom]

And please, no pretending that X on Linux doesn't crash. It does, and this is the 4th time I've restarted this laptop today. Hanging hard with VirtualBox.

Not arguing that at all, but I do have a bit of an issue with the inference that it crashes frequently. I haven't seen X crash on my laptop in several months. VirtualBox provides a rather unique environment.

I'd definitely like to see windows reconnect to X automatically though instead of just dying.

Re:End of network display?

[Dog-Cow]

Will Ubuntu prevent you from running an X server?

Of course being logical would require some facility, which you obviously lack. So I guess I forgive you.

Re:End of network display?

[Dog-Cow]

Today, no non-X app is network transparent. Tomorrow, no non-X app will be network transparent.

If nothing is changing, how can something break?

Idiot.

Re:End of network display?

[danomac]

I haven't had X crash in more than two years now. I blame nVidia for the crashes I had before that, though.

Re:End of network display?

[Anonymous Coward]

You mean, like they prevented me from running gnome 2? quite possible...

Re:End of network display?

[Anonymous Coward]

I encourage my competitors to implement this, etc etc. You know what would be hilarious? Your buggy hardware (I haven't had a X crash in, I don't even know, certainly more than a decade) combined with root logged in and doing some admin GUI thing. X crashes. Logs itself back in. Before the user gets to interact, the GUI admin thing crashes X again. Repeat infinitely. Oh no problemo just log in as root to break that loop... errr... thats not gonna work because its root who's stuck in the loop. Wipe the hard drive and reinstall?

This is already a solved problem: if the X server fails to start n times in a row (3, I think), then it stops trying.

In ye dark ages of firefox I have run into this, where bringing up some cruddy coded web page full of cruft crashed FF (which admittedly should have failed gracefully, but still, cruft is cruft) and then on restart FF asks if I wanna restore my session. Oh heck no, that's just gonna crash FF again!

Which is why session restore on modern browsers either allows you to choose which pages to restore (Firefox) or at least doesn't load pages that were loaded just before the crash unless you click a button. No reason you couldn't do the same with X clients.

Re:End of network display?

[Anonymous Coward]

Will Ubuntu prevent you from running an X server?
Of course being logical would require some facility, which you obviously lack. So I guess I forgive you.

No, but that does not provide the abilities we have today, any more than running an X server under Win7 provides them just because you can display an X app under Windows that way.

But seeing that would require the ability to think logically, which you obviously lack. So I guess I forgive you.

Re:End of network display?

[theCoder]

Running an X server only fixes part of the problem. Sure, today, most applications are X clients, and thus running an X server on Wayland will allow for network transparency. But what happens in a few years when many applications start becoming only Wayland clients? I won't be able to ssh somewhere and run the Wayland applications, no matter what server (Wayland and/or X) I'm running locally. And even if someone comes up with a way of forwarding Wayland traffic, what happens when I'm sitting at a machine that only has X installed?

Re:End of network display?

[firewrought]

Today, no non-X app is network transparent. Tomorrow, no non-X app will be network transparent.

If nothing is changing, how can something break?

Idiot.

You know what he means. Tomorrow (if Wayland becomes ascendent), the previously X-based API's you use for drawing a GUI will migrate to Wayland and your app will have to either give up network transparency or forgo the latest version (which might be fine at first, but will eventually force you to confront some form of version/dependency/compiler/forking hell). What's "breaking" is the ease of future development...

Of course, I think defenders of X are pretty slow to acknowledge the problems with how X handles network transparency. It's useful to an extent, but the way Microsoft did it with RDP is way more user-friendly.

Re:End of network display?

[devent]

It's always nice to say "xxxx don't work, don't pretend it works, because it crashes yyy times/day for me". For everyone that starts a discussion like this, there are 100 others for which the xxxx just works and they do their work and are quite.

It would be nice if you share your hardware configuration, or if you open a bug report. Because for me X just works, and it just works for at least 2 years (since I started using Linux) with very different laptops and PCs. I can't recall anytime where X crashed.

There were some issues with Wine after a game; there were some issues with suspend or hibernate. But that is certainly not X11 fault. I never saw that X11 just crashed in a normal usage.

Re:End of network display?

[Anonymous Coward]

Why all the hostility? Are you a waveband developer, ubuntu fanboy, or both?

Calling people names may make you feel superior and get you mod points from fellow fanboys, but it really isn't contributing anything positive to the conversation. Instead it is making you look like a child and conveys very little information that would give someone a positive opinion about wayland.

Re:End of network display?

[Hatta]

And please, no pretending that X on Linux doesn't crash. It does, and this is the 4th time I've restarted this laptop today. Hanging hard with VirtualBox.

That's not X hanging, that's VirtualBox hanging.

Re:End of network display?

[Hatta]

How does such a deliberately obtuse post get modded insightful?

Re:End of network display?

[jedidiah]

And please, no pretending that X on Linux doesn't crash. It does, and this is the 4th time I've restarted this laptop today. Hanging hard with VirtualBox.

You're talking about an app that comes with it's own kernel modules. It's own kernel modules are probably what's causing the problem.

Although I've run vobx for months and months at a time myself with no trouble.

Re:End of network display?

[jedidiah]

Nope. You're the idiot.

Today all of our apps are network transparent.

Tomorrow they will all be recompiled for Wayland and not be network transparent anymore.

You idiots trying to re-invent the Mac should actually use one sometime.

Re:End of network display?

[Anonymous Coward]

And please, no pretending that X on Linux doesn't crash. It does, and this is the 4th time I've restarted this laptop today. Hanging hard with VirtualBox.

Fair enough. I won't pretend. I don't need to. Because it doesn't crash much for me, and that's in reality.

No, seriously. I can't honestly recall the last time X crashed on me. And I throw binary blob drivers at it, I switch video modes every now and then for games, I have an odd setup where I need to disable Nvidia's Optimus stuff, and it just. Won't. Die.

So please, stop pretending that everybody has the same problems you do. Your solipsism stopped being adorable when you were a toddler.

Re:End of network display?

[AvitarX]

I hope this forces the more popular toolkits to add network transparency.

The pieces are there I suspect, I've seen some pretty impressive things done with GTK back-ends (one that makes it a character interface for consoles (a side project never part of the main), and another that makes it a browser app and network transparent (more like a single Window VNC).

There's also a QT one (I think) that uses a console frame-buffer rather than X.

The toolkit should be in a better place to do the transparency efficiently too.

Re:End of network display?

[lennier]

After all the graphical programs are X clients. Why would a client up and die just because some server died?

This! I've wondered exactly this since about 1997, when I first got into Linux. Decoupling the X Server and clients from running in the same session... since it's network transparent and all and was designed for the server being even on a completely different machine... seemed like the obvious thing to do and it boggled me that none of the mainstream desktop environments ever did it.

I even managed to install a whole second X instance on Ubuntu once, just so that I could run Wine and Dosbox games which occasionally crashed and left the GUI in an unstable state, and then I could restart the X server without losing my main workspace. But it seemed like a ridiculous workaround for something which has inexplicably never been implemented despite being "one of the main advantages of X".

Re:End of network display?

[Anonymous Coward]

good job turning a bug into a feature, you should work at microsoft.

Re:End of network display?

[Yenya]

Today all of our apps are network transparent.

Sadly, this is not true anymore. Many apps today depend on things like D-Bus or PulseAudio, which cannot be easily forwarded through the X protocol connection. Add a "run only a single instance of $app no matter what" mentality to the mix, and you are screwed: the $app started on a remote machine detects that another instance (on a completely different machine but the same display) is running, and tries to forward its own command line arguments to the previously running instance. But arguments like filenames are depended on the X client machine. Oops.

Re:End of network display?

[Anonymous Coward]

You probably mean Qt, not QT.

QT is QuickTime.

Re:End of network display?

[diego.viola]

Nobody is preventing us to implement network transparency in a compositor or whatever.

simple question about Wayland

[Anonymous Coward]

Can someone answer this simple question about Wayland?

If I'm on such a Wayland-based system and I have a bash session in a terminal window. Does this continue to work?

[bash prompt]: ssh -X remotehost SomeProgram

Will SomeProgram's GUI be displayed on my local Wayland display, just as with X today, even if SomeProgram uses 3D via OpenGL, just as works today in X.org? And will this work without having to embed everything in some X-server-window type thing like the kludge that Windows uses to display X programs? That is, will SomeProgram appear natively on my desktop just as today?

If not, then this is breaking a fundamental aspect of the Unix architecture going back decades, and should in no way be the default for any mainstream operating system.

If it does work, hey, great.

Re:simple question about Wayland

[Bitsy Boffin]

It does not work. Last I heard the answer was "use VNC" or some such nonsense.

Replacing X is one thing, replacing it with an inferior product however is ludicrous. Ludicrous is unfortunately something that Ubuntu is quite adept at :-(

Re:simple question about Wayland

[Anonymous Coward]

Thanks for the answer Bitsy Boffin. That really sucks - it was what I was afraid of.

We depend on this feature in a production environment, so we will need to transition to a non-Wayland based distro :-(.

Re:simple question about Wayland

[Anonymous Coward]

Someone should mod this up. It really needs to be widely understood that Wayland breaks this.

Re:simple question about Wayland

[TheRaven64]

It will work if SomeProgram is an X program, just as it does on OS X or Windows if you have an X server installed. It won't work if SomeProgram is a Wayland program. Wayland eliminates a number of process boundaries in X, moving the window and compositing managers into the main executable. This is done for performance reasons, presumably by people who have never profiled an X server and therefore not noticed that these round trips are not a bottleneck in modern systems, and at the expense of stability (if your compositing manager crashes in Wayland, your display server also dies, with X11 it can be restarted, usually without any data loss).

Re:simple question about Wayland

[Anonymous Coward]

It does not work. Last I heard the answer was "use VNC" or some such nonsense.

I've been tracking this too, and that's the last thing I heard out of Wayland. No, it doesn't work, but you can try this unusable kludge. VNC has its uses, but a bitmap-level app display is in no way a replacement for a protocol-level one as we have today. I use VNC, but it's not even remotely a replacement.

Say this to the Wayland people, pointing out the problems with such a VNC solution, and their answer is something like, "LALALALA can't hear you!"

Re:simple question about Wayland

[Anonymous Coward]

OS X or Windows if you have an X server installed.

I'm going to argue it *doesn't* work under Windows, even with an X server installed. Sure, you can run an X based program by running an X server on your Windows desktop, but that's not the same thing. I know, because I do it all the time. The same will be true in Wayland: you'll be able to run an X server on top of it, but that won't provide the same abilities that we have today. Your analogy to the "X server under Windows" is a good one, but I don't think it shows what you think it shows.

Re:simple question about Wayland

[Anonymous Coward]

You are acting like a child. STFU.

Re:simple question about Wayland

[Anonymous Coward]

Wanna see an idiot? Look in a mirror, if you happen to know what that is.

Re:simple question about Wayland

[Hatta]

It won't work if SomeProgram is a Wayland program.

That's the problem. If Wayland becomes the default, we can't count on being able to forward arbitrary apps over the network. That's far too big a price to pay for anything Wayland could possibly offer.

Re:simple question about Wayland

[serviscope_minor]

This is done for performance reasons, presumably by people who have never profiled an X server and therefore not noticed that these round trips are not a bottleneck in modern systems

This. 1000 times this!

Ping times via the TCP/IP stack are 70micro seconds on an old, slow machine. Via unix domain sockets, they are very much less.

The entire exercise of wayland is what happens when you mix bored developers + ooo shiny + premature optimization.

Re:simple question about Wayland

[spitzak]

You are going to get flooded with idiots who will say "no". That is wrong.

When you run the program, the environment will be different and this will change the code in the library that talks to wayland so that it sends the window images (compressed) over the network to a client on your local machine, which will then tell the local wayland server to display them.

This is EXACTLY how X works. When you run "ssh -X" the ONLY thing it does is set $DISPLAY to a different value. The xlib library knows how to interpret this environment variable and send all the communication back to the x server on your local machine. About the only difference is that instead of a thread in the x server, it is likely a different process for the wayland server. You should realize there is no magic, there is a huge block of code in that xlib library RUNNING ON YOUR REMOTE MACHINE. Same with wayland.

In addition wayland should be much much much faster for any modern program (such as your OpenGL example) that wants to render an image and then display it. Any program using antialiased fonts is pretty much going to require less communication to send an image of the window over the network than to send the data it needs to get a remote drawing. People really use VNC and virtual gl because it is faster than remote X.

Re:simple question about Wayland

[Anonymous Coward]

sends the window images (compressed) over the network...
This is EXACTLY how X works.

I'm afraid you don't know what you're talking about. X does not send "compressed window images" over the network. That approach turns out to be spectacularly bad, and is why VNC sucks (though it has the advantage of running on pretty much anything).

Wayland will NOT be replacing X11 in 12.10

[Anonymous Coward]

Canonical has plans to include Wayland as a technical preview in 12.10, not as a replacement for X11. This means that they have to actually get it working at a basic level before putting it in the repositories. While Canonical is pushing Wayland, they've already said that it's still several years away from becoming a viable replacement for X11. This is just Canonical trying to push forward the development of a peice of software they believe in.

Re:Wayland will NOT be replacing X11 in 12.10

[msobkow]

Personally I still don't understand what need there is to replace X. Instead of replacing X entirely, how about just fixing the few remaining bugs that are affecting people and causing server crashes? It would seem to be a lot less work to do so than to start from scratch with a new bug^H^H^H^code base.

is X old? Sure. But it was well designed for what it was intended to do, and as I'm not one of those people affected by server crashes, I'm perfectly happy with it.

Will it even work with common setups?

[Anonymous Coward]

Will it work with my system that has two nVidia cards running a quad monitor setup?

Will I be able to use the nVidia driver with full acceleration for all my high powered video cards? Especially OpenGL and OpenCL/CUDA support is very important for the work I do. That Manuto (nouveau) boy-band crap isn't going to cut it.

I can tell you right now that my setup doesn't work in Unity, nor GNOME 3. Hell, it barely works in X.org at all and not very well at that (I don't get compositing, OpenGL only works on two of the monitors, etc). I somehow doubt it's going to work in Wayland.

I haven't used Windows as my primary OS in more than 15 years, maybe I need to take a look at it again. I do know multi-monitor support is a hell of a lot better in Windows 7 (and OS X for that matter) than in X.org. X.org sucks so maybe Wayland could fix that, I have my doubts though considering how poorly Unity works for even basic features.

Re:Will it even work with common setups?

[Anonymous Coward]

No, since nvidia won't support it since the *nix customers they actually care about (VFX studios, CAD users, GPU compute customers, etc.) don't use blingy desktops.

not supported

[Anonymous Coward]

wayland is not supported by nvidia and amd/ati

Wayland doesn't break X

[k(wi)r(kipedia)]

Ubuntu is sparking a new 'unix war', dividing the linux ecosystem. It first pushed hard for its own Unity now with Wayland that breaks all current X apps. Theyr'e only in it for themselves.

Wayland doesn't break X, if by "break" you mean stop something from working. You can run Wayland concurrently with X. All those X-incompatible will simply run under X.

Re:Wayland doesn't break X

[Anonymous Coward]

You can run Wayland concurrently with X.

In a limited sense that is true, although it remains to be seen whether high performance 3D apps will work well that way.

But many things still break. E.g, from my bash window:

ssh -X remote_box
run_app

to display natively on Wayland desktop from my Konsole window. This will break, according to the Wayland people themselves.

Re:Wayland doesn't break X

[0123456]

Wayland doesn't break X, if by "break" you mean stop something from working. You can run Wayland concurrently with X. All those X-incompatible will simply run under X.

But you can't run that Wayland app remotely with the display on another machine. Unless you use a disgusting kludge like VNC.

Re:Wayland doesn't break X

[k(wi)r(kipedia)]

Okay, it's kind of like the difference between vi and emacs. Wayland is kind of like vi and emacs is like the X system. To a vi user, emacs appears to be doing too much. Which is what X is to the typical desktop user. In fact, the ability not to run a Wayland app remotely directly seems like a security feature, one less (admittedly small) path for an attacker to gain control of your system.

Re:Wayland doesn't break X

[ChunderDownunder]

Is there such a thing as a "Wayland app"? My understanding is that the ability to run GUI applications depends on the various toolkits such as GTK+ and Qt being ported to be Wayland native. Such applications thus don't have any direct dependency on X11 nor Wayland.

Rather, the application would load a shared library which selects a display backend seamlessly at runtime. The choice to utilize Wayland, local X or remote could be handled more or less transparently, e.g. as the DISPLAY variable currently does.

X11 support isn't going to disappear overnight from the common toolkits any more than Qt and GTK+ will cease to exist on non Unix platforms. e.g. Gimp and Pidgin run fine on Windows, Qt runs on the Playbook.

Re:Wayland doesn't break X

[ChunderDownunder]

You're invoking -X, which implies an X session. I wouldn't expect it to 'display natively' as Wayland.

However, they do talk about embedding X servers on top of wayland, so wrapping a remote application by spawning a X session on your local Wayland desktop seems feasible.

If the vision is true, such teething problems in backwards compatibility should disappear. Remoting 'Wayland-specific applications' without an X11 fallback is a different matter.

They should start with updating X

[Anonymous Coward]

Ubuntu's X11 package hasn't been updated to the latest version. Before thinking about Wayland, they should at least take properly care of X11.

Re:They should start with updating X

[Anonymous Coward]

Ubuntu is about churn and pushing out new shinies not fixing bugs and other boring stuff.

Re:They should start with updating X

[Anonymous Coward]

If they are planning to replace X11 with wayland... why bother updating X11? That makes less sense.

Why Wayland?

[JDG1980]

I understand that X11 is obsolete crap and has to go, but why are they using Wayland instead of, say, DirectFB? From what I can tell (please correct me if I'm wrong, Linux really isn't my thing) DirectFB is much better supported and a more mature product.

Re:Why Wayland?

[Anonymous Coward]

Because mature software is dumb and doesn't allow the Wayland people all the fun of starting from scratch.

Re:Why Wayland?

[snadrus]

DirectFB has severe limitations that can't be "fixed", and even X11 provides more than it offers: Input handling, multi-monitor, hardware acceleration. Wayland allows zero-copy handoffs of a buffer to the server (through video card memory) which can then use harware acceleration to compose into a final multi-window image. Many toolkits already render buffers on the video card, so keeping the data there results in fewer copies. Even cell-phones have hardware acceleration now, so keeping images in video ram is just logical.

Re:Why Wayland?

[serviscope_minor]

I understand that X11 is obsolete crap and has to go,

Well, you understand wrong, unless you also consider Windows 7 and Lion as obsolete crap which has to go.

Most new code doesn't use the ancient parts of the X protocol, much like most new code on Windows doesn't use the ancient windows APIs or most new code on OSX[*] doesn't use ancient APIs.

Just because the old stuff is in for backwards compatibility doesn't mean you have to use it, or that the new stuff is somehow old. I'd bet you could make most of the old protocol graphics calls return errors and a modern desktop would still work.

Anyone who claims that the old code paths are bloaty is essentially a liar or a fool. They were written in 1987. Basically anything written in 1987 is by modern standards a minute piece of software.

The mix of modern and old APIs going under the name X11R7.??? actually form a pretty good system. Sure there are warts (as there inevitably will be in Wayland as soon as its ont brand new), but Wayland isn't the answer to the warts. It's basically a new system written by people bored of hacking X11 who would rather make something shiny even it discards really useful features,

Actually, if you look at the FUD written by some of the Wayland developers, it is shameful, and done by people who really ought to know better.

Re:Why Wayland?

[RogerWilco]

What I've learned about software developers, is that they much rather develop something new from scratch, often reinventing the wheel, than change an maintain an older stable piece of software.

What is also known from Software Engineering, is that developing something new is relatively easy, maintaining it, is where it gets hard usually.

Linux is just a software developers dream.

Re:Why Wayland?

[diego.viola]

Please quit FUDing.

nVidia/AMD will NOT support wayland

[Anonymous Coward]

Please note: neither nVidia nor AMD has any plans to support their high performance drivers natively under Wayland.

That means you will be limited to low performance Intel graphics, or low performance open source drivers that don't provide many modern OpenGL features.

Wayland is a non-starter if it doesn't have either of the two heavy-hitter graphics makers on board.

Sometimes...

[drjones78]

... I woefully wonder if I'm the only one who has the fastidious feeling that the noritious names for Ubuntu releases are idiosyncratically idiotic and horrendously horrible

Re:Sometimes...

[FranTaylor]

Maybe you'd be better off if you worried about being such a worthless pedant

Re:Sometimes...

[Anonymous Coward]

... I woefully wonder if I'm the only one who has the fastidious feeling that the noritious names for Ubuntu releases are idiosyncratically idiotic and horrendously horrible

Sorry for the confusion. We'll just switch to a far more logical progression of names, like randomly pulling types of cats out of our asses. Lions are intrinsically superior to leopards, right?

Re:Sometimes...

[drjones78]

Such a disconsolate digression! This accused pedant pontificator is really just a jocund jester. Sheesh!

Re:Sometimes...

[lennier]

Unpossible! Ubuntu's clever cryptonyms grant graciously memorable mnemonic nomenclature, nicely.

Still works

[snadrus]

Support arrows go the other way. Wayland uses X11's direct rendering which is works great for ATI in 2.6.38 & for Nouveau (open-source NVidia driver). NVidia's the "worst-supported", but it still runs, just at slightly slower than it should.

Re:Still works

[Anonymous Coward]

Nouveau sucks and they hate bug repports

Re:Still works

[diego.viola]

Wrong. All bugs I've reported to Nouveau developers, they all got fixed, so please quit with your FUD.

yeah right

[FranTaylor]

Steve Ballmer once called Linux a cancer and now Microsoft writes kernel drivers

How is life in your reality where time stands still and nothing ever changes?

Re:yeah right

[Anonymous Coward]

Steve Ballmer once called Linux a cancer and now Microsoft writes kernel drivers

How is life in your reality where time stands still and nothing ever changes?

So... you think that Ballmer changed his mind... ? Hehehe, tha'ts funny, kid.

e world@Tech News

[Anonymous Coward]

Nice article.thank you about informing us.

general knowledge

[Anonymous Coward]

Although the more detailed answer is that GTK/Qt apps will need recompiling with an updated library. If you use X11 directly, then you have more work - except that you can also run an X server within Wayland to support native X11 clients.

I've been impressed for some time with how well the Wayland developers have thought about backwards compatibility. X11 needs replacing; complaining that its different to X11 doesn't help solve the problems.

I suggest you that you should gain vast knowledge on general knowledge topics of the world to get a good job . without general knowledge base skilled, you cannot be able to get your desire job in the modern world

general knowledge

Ubuntu Still A Steaming Pile

[ilikenwf]

Not trolling, but I think that it's interesting that Ubuntu has the same kind of fanboy nature these days that Apple does. In reality, while it does fill the two niches of "I need a linux box setup ASAP," and "I'm a n00b and what is Linux?," Ubuntu as it is sucks.

If you want something that's lightweight, not running 50 daemons from a fresh install, and something that's actually custom as you want it all the way down to the source, is Archlinux, Gentoo, or Slackware not a better option?

Then, even Debian is better than Ubuntu - and it covers both markets of new users and people who just need to get a box up and running quickly.

Ubuntu is really just linux for n00bs and lazy people.

Gotta say...

[datsa]

I love the name.

Desktop Linux

[ceswiedler]

This is what Desktop Linux is. It's companies trying to make a version of Linux which Just Works for people who don't care that it's Linux. That means sacrificing choice in the name of making the product more tailored for the users they're targeting. That's good design.

Your fundamental complaint is that Ubuntu isn't tailoring its product for you. It's a completely free and open product, planned from the start to make Linux more usable by non-technical people. And you're complaining. Despite the fact that there are literally dozens of other Linux distributions which do exactly what you want. Nice.

Re:Desktop Linux

[lennier]

It's a completely free and open product, planned from the start to make Linux more usable by non-technical people. And you're complaining.

Yes, because it doesn't actually work even for that purpose.

It's a noble goal to make computers useful for newbies. Really it is. But doing it wrong doesn't help anybody, and just because you're doing it for free (um, despite the massive amounts of cash flowing into Canonical which must be coming from somewhere) doesn't mean you get to censor valid criticism of what you're doing wrong.

Just to clear things up

[Trogre]

Firstly, Ubuntu aren't forcing Wayland on anyone as it is not the default - it's just there if you want it.

Secondly, Wayland could well become a decent display manager, just as soon as they incorporate network transparency. And not a minute before.

Desktop Linux is Dead

[Anonymous Coward]

GET OVER IT! After all these years, the user base for desktop Linux is only ~ 1%. Linux has a future on the server, but that is command-line only. Linux has a future on mobile, but that is on Andoid which is controlled not by a 'community' but by Google, a multi-national, multi-billion-dollar company that uses the work of the open-source community but contributes only when it suits its interests.

Re:Desktop Linux is Dead

[diego.viola]

Bullshit.

Your brain is what is dead. Moron.

Unity

[Anonymous Coward]

I'm impressed so many of you are ragging on Unity. I think it's a brilliant, intuitive interface. The lens/scope system is amazing and present the possibility for an entirely new level of application and resource integration into the desktop environment.

Call me when your desktop environment lets you access application menus via text. Until then they're all second to Unity. It's really the best DE at the moment. Picture related:

http://i.imgur.com/fkgtd.png