Slashdot Mirror
Preview of Ubuntu's Unity Interface
itwbennett writes "In late October we learned that starting with the next release (11.04), Ubuntu would use Unity instead of GNOME as its default desktop interface. Now we know a bit more about what that will (and won't) mean for users. The move to Unity doesn't mean that Ubuntu is abandoning GNOME. It also doesn't mean that users will be forced to use Unity; they'll still be able to revert to the old GNOME interface. What it does mean, mainly, is that users will be presented with a simple interface — probably too simple for nuts and bolts types. The more 'radical shift' will be switching Ubuntu's base graphics system from the X Window System to Wayland. There users can expect that it will take some time before things are in working order. 'In other words,' says Steven Vaughan-Nichols who reviewed Unity for ITworld, 'Wayland will be an option, and one that only people who don't mind having their desktops blow up on a regular basis should fool with, in Ubuntu 11.04. By Ubuntu 11.10, it will be workable, and come the spring release two years from now, Ubuntu 12.04, we should, if all goes well, see a stable Wayland-based Unity desktop.'"
Text is useless. I want screenshots!
I'm sorry, how is this possibly a "preview" when there is not one screen shot? One link goes to an older /. article, the other goes to an all text article.
Can you please stop naming things that don't have photos like they do have photos?
If "weird" includes Ubuntu's adoption of Wayland, I have bad news: Fedora is also dumping X for Wayland (eventually).
The problem with PulseAudio is not that it wasn't finished or well tested, the problem is the implementation sucks (ie. bad programmers wrote it).
I have never understood why they didn't just go back to OSS. OSS has made extensive improvements in the latest versions and can do everything ALSA/PulseAudio/whatever can do plus a lot more. On top of that everything works with OSS because it's the original Linux sound API.
They are duplicating the KDE 4.0 roll out plan?? *ducks*
Is it completely impossible to get something similar into Wayland?
Every time I've seen someone ask the Wayland devs how they plan to support remote rendering, their response seems to be 'we don't. go away'.
X will still run fine, even under Wayland, so relax.
Sigh, we're not talking about running X and rendering on a Wayland desktop, we're talking about running Wayland apps and rendering on a remote desktop, the way you currently can with X. The biggest single advantage of X over Windows, which the Wayland developers seem quite happy to throw away in the quest for 'The Shiny'.
Given a choice between fancier compositing effects and being able to run any program on any machine while rendering on any other machine, I'll take the latter any day.
Ubuntu was working towards a so-called "10 second" boot. What happened to that? They give up? *MAYBE*, if I'm in a generous mood, they quickened boot by 30'ish percent during their efforts. But it still takes like 40'ish second or more until a usable desktop. That's a long way off from their stated goal. People seem to have forgotten about this.
The Unity namespace is already occupied by http://www.unity3d.com/ a great game engine for iOS and android and support multitouch and so on. Canonical is just going to make it a PITA for one or both sets of developers searching for "unity opengl" "unity GUI" "unity multitouch" "unity android."
Are there any Wayland native apps yet? Without those, all you have is a pretty interface and nothing to do with it. Sure, you can provide backwards compatibility by running an X server on top of Wayland, but then what was the point of dumping X.org?
The X11R6 protocol has been around for a long time, because it's good at what it does. By dumping the X protocol along with the X.org server they're throwing the baby out with the bathwater.
Give me Classic Slashdot or give me death!
From the Wayland FAQ
https://groups.google.com/group/wayland-display-server/web/frequently-askeds-questions
You do realize that Windows doesn't support X11 (at least it's apps won't act as clients - there are servers) and many, many, MANY admins get by just fine with RDP right?
X11 isn't the absolutely only way to do remote access.
"People who think they know everything are very annoying to those of us who do."-Mark Twain
So if I use this unity 3d engine on ubuntu unity using VMware unity, do I get a trilogy?
Wayland developers include several lead X.org developers,[9] who feel that a cleaner new design and protocol is more maintainable for the future.[14] One of them has envisaged providing remote access to a Wayland application by either 'pixel-scraping' (as in VNC and SPICE) or getting it to send a "rendering command stream" across the network (like RDP).[15] It is anticipated that X11 applications will be supported by an X server running as an application on Wayland.
Hopefully they go the RDP-like route, which im my opinion is vastly superior over the way X11 does it.
With such gems in TFA as
By focusing on Unity (on Wayland or X) for Ubuntu, Canonical has essentially forked its own Linux distribution.
you arent missing much (what does that even mean???? They cant "fork" their own distro...).
Perhaps the author typed "borked" and the editor "corrected" it.
XML is a known as a key material required to create SMD: Software of Mass Destruction
I can't get PulseAudio working in any way shape or form. Perfect setup doesn't work, no fresh Ubuntu installs work. I'd guess that it was hardware related, but the hardware is question is an old SB Live (maybe early Audigy) card. It worked fine for years under Gentoo and pre-PA Ubuntu releases. It works fine when I boot into windows for an occasional game. It works fine once I purge PulseAudio and go back to Alsa.
Every new Ubuntu release I try to fight with PA for a couple of days. When it's clear it's not going to work, I purge it, and all is well. (Outside of a few flash issues, of course.)
I understand what PulseAudio is supposed to do - I've had it semi-working at times. It's a great, great idea. It's badly needed for Linux. I just wish it goddamned worked for me! Best I've done so far is have everything work, except sounds queued up in the pipeline, and trickled out tens of seconds to minutes after they were called. Before PA crashed and died. I have to agree with the AC you replied to: "Man, the hours upon hours I've lost on Pulseaudio. Insanity."
Velociraptor = Distiraptor / Timeraptor
The desktop sits atop the OS. It's not a different OS, but a different GUI.
Unlike Windows or Mac, you can actually have several different GUIs installed, and even switch between them at will.
End the FUD
Ubuntu lets you choose too. If you want off the roller coaster and just want a stable system based on proven technology, install an LTS and wait for the next LTS. Easy.
DRM: Terminator crops for your mind!
Maybe the point is, Ubuntu has abandoned "works out of the box" -- not that that ever happened. Most of us who want to use Ubuntu really want to use Windows 7, when it works, or Mac OS, when it works. It's a pity to trade on the reputation of Torvald's kernel, when we'll have to skip 11.04 and 11.10 on the recommendation of Canonical, and 12.04 on the principle that it's probably just another beta. Is that two years before Ubuntu is Ubuntu Again? I pity the support community, who is growing up and has to get on with its careers.
``Tension, apprehension & dissension have begun!'' - Duffy Wyg&, in Alfred Bester's _The Demolished Man_
Confusing? X is the server, and handles connections to it telling it what to display. Like httpd (apache) is a server and handles a Web client telling it what Web page to send down the pipe. People weren't confused running the Tetrinet server, seeing the clients connect to them and output images to the screen; but they're confused running the X server, seeing the clients connect?
It is confusing because while it makes sense from point of view of the X protocol, from the point of view of the user, the "server" appears to be the client and the "client" appears to be the server. If I connect to server and request an image - in the http protocol, I connect to a server(apache), and it shows content on the client(browser). However if I am doing the same thing using X, it appears as if I connect to server(remote system), and request to show an image, and it shows content on client(my display or X-Server). What is actually happening is that the remote server's program is the client that requests to display things on the server - but that is not what the user sees. Thus the confusion of so many people, which is understandable as it is not the most logical thing unless you understand the X protocol.
-Em
RelevantElephants: A Somatic WebComic...
That's an interesting opinion.
Perhaps it's rooted in a confusion in the use of "Operating System," or perhaps from your misunderstanding of what an OS is in general, or how the OS and UI interact. Surely, one can roll the UI into the "OS," but particularly in this case, the underlying mechanics aren't changing (there's still a GNU kernel in there), but the discussed changes are in layers between, which can be replaced if you don't like the changes.
The flexibility you chide is a strength not a weakness. When users are faced with Linux distros, they aren't experiencing the Linux OS, but the desktop interface atop the OS. When approaching a PC running Linux, they're faced often with Gnome or KDE or one of the others, probably tweaked with their distro's defaults or the previous user's preferences or tinkerings.
Further, except for us nuts-and-bolts users, few users even get into the UI they're presented with (beyond changing the background or adding widgets) after they've figured out how the launching mechanism works. Most of them are familiar and concerned with the applications they run (word processor, web browser, e-mail client). Those, for the most part, don't change when the underlying desktop changes (that is, switching from Gnome to KDE) any more than they do when applying different themes (colors, borders, fonts).
If you've ever written GUI software, you'd know that your fear-based misrepresentation (or perhaps another misunderstanding) of this is also unwarranted. Few people write application software directly to the UI (Gnome/KDE/etc), or even to the graphics layer beneath that (X/Wayland/whatever), but instead use an abstraction layer (QT, for example), for exactly the reason of removing the concern of which desktop UI it sits atop.
Underneath all of that, the OS, in this case GNU Linux, is the same.
End the FUD
You seriously changed from free software to payware, from the open space of Ubuntu to the walled garden of Apple, from getting updates every 6 months to having to buy updates every so many years, from having full control over your machine and software to being beholden to Apple's CEO's every whim?
Amazing... just... amazing.
May I suggest renting a computer after that Apple machine has bitten the dust? That way you have even less control over your machine while you pay even more. It must sound like data heaven to you.
--frank[at]unternet.org