Pular para o conteúdo principal

Canonical axing X Windows: What will it mean for the next version of Ubuntu?

Canonical axing X Windows: What will it mean for the next version of Ubuntu?: "

In yet another recent announcement that had the Linux community looking like the proverbial “deer in headlights,” Canonical has announced that in an iteration of Ubuntu it might very well drop X Windows in favor of Wayland. This comes on the heels of Mark Shuttleworth’s recent announcement that 11.04 would see Ubuntu leave behind the GNOME Shell in favor of Ubuntu Unity. That was a tiny drop in the bucket compared to this latest consideration.


Think about it - X Windows. How long has X Windows driven the desktop for Linux? Maybe since Linux had a desktop? This is HUGE! The very thought of a Linux without X Windows is staggering considering that nearly every application will have to be rewritten. Is the next announcement to be that Canonical is no longer going to ship with current Linux applications, but is instead going to develop applications on their own?



  • Ubuntu Web browser.

  • Ubuntu Email client.

  • Ubuntu Graphics editor.

  • Ubuntu Office suite.

  • Ubuntu Shell.


The list goes on and on and on.


I could understand Shuttleworth’s previous announcement. He’s obviously making a grab for an interface that will be more in line with the future of the desktops - specifically multi-touch and tablet PCs. That’s all good. I respect that. But Wayland in favor of X Windows?


“What is Wayland?” you ask?


Wayland is a display server for Linux desktops that was created by one of Intel’s open source technologists. Wayland’s stated goal is ”every frame is perfect, by which I mean that applications will be able to control the rendering enough that we’ll never see tearing, lag, redrawing or flicker”. But if you dig further, you find that Wayland is actually “a protocol for a compositor to talk to its clients as well as a C library implementation of that protocol. The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a Wayland client itself. The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers.”


The key in the above text (taken from the Wayland web site) is compositor. If the Unity/Ubuntu marriage is going to be as much of a success as Shuttleworth needs it to be, it is going to need a strong compositor built in to the system. The last thing this marriage needs is to require a third party compositor. That would blow the lid off Shuttleworth’s plan for ease of support for manufacturers. With a compositor built into the X Server, things ease up quite a bit on the technical support front.


Remember, one of the reasons Shuttleworth made the move to Unity was so that PC manufacturers like Dell would have an easier time supporting Linux. With a similar desktop interface across the board, companies wouldn’t have to worry about GNOME, KDE, Enlightenment, etc. Instead there would be Unity and that’s it.


Note: There is a poll embedded within this post, please visit the site to participate in this post's poll.

I suspect that Shuttleworth has some grand plans with Wayland that will unfold for the average eye in the months leading up to the release of 11.04.


My initial reaction from this announcement was quite the eye-opening shock. After all, X Windows has been the driving force behind the Linux desktop since Linux had a desktop. But it has been my opinion that Mark Shuttleworth has had the Midas Touch with Linux and you can’t shun his ideas until they are proven wrong (if ever they are).


Canonical has made some seriously bold steps in recent weeks. These bold steps will hopefully take Linux (at least Ubuntu Linux) to heights it has never seen before. I applaud Shuttleworth for these actions. Whether you like them or not, they speak volumes for the dedication that Canonical has for the Linux operating system.





"

Comentários

Postagens mais visitadas deste blog

Improve Windows Security By Closing Open Ports

Improve Windows Security By Closing Open Ports : " A standard Windows operating system has a number of ports open after installation. Some of these ports are needed for the system to function properly while others might not. These ports can pose a security risk as every open port on a system might be an entry point for a malicious user. A port basically allows communication to or from the device. Characteristics are a port number, an IP address and a protocol type. This article will give you the tools at hand to identify and evaluate the open ports on your Windows system to make a decision in the end whether they can or should be closed or left open. Software programs and tools that we will use: CurrPorts : Available for 32-bit and 64-bit editions of Windows. It is a port monitor that displays all open ports on a computer system. We will use it to identify the ports and the programs that are using them. Windows Task Manager: Also used to identify the programs and link some p

Diagnosing a Blue Screen of Death Error in Windows

Diagnosing a Blue Screen of Death Error in Windows : For many years now the famous Blue Screen of Death (BSoD) has been the ultimate indication that something disastrous has happened to make your computer die, but how useful is the information in the BSoD and the respective crash dump file that Windows produces? The best article I ever found explaining the BSoD in depth is here on the Microsoft website, however it’s quite technical and doesn’t discuss how to actually troubleshoot a problem. The crash dump file is just technical details of what was being held in the computer’s memory at the time of the crash, and this will include details on every driver and service that was loaded, and every piece of software that was running. The most useful pieces of information are to be found on the BSoD itself and are highlighted on the screenshot below. These are the BSoD error name, the stop error code and the name of the driver or service that has failed (this last one might not always appea

Use BGInfo to Build a Database of System Information of Your Network Computers

Use BGInfo to Build a Database of System Information of Your Network Computers : " One of the more popular tools of the Sysinternals suite among system administrators is BGInfo which tacks real-time system information to your desktop wallpaper when you first login. For obvious reasons, having information such as system memory, available hard drive space and system up time (among others) right in front of you is very convenient when you are managing several systems. A little known feature about this handy utility is the ability to have system information automatically saved to a SQL database or some other data file. With a few minutes of setup work you can easily configure BGInfo to record system information of all your network computers in a centralized storage location. You can then use this data to monitor or report on these systems however you see fit. BGInfo Setup If you are familiar with BGInfo, you can skip this section. However, if you have never used this tool, it takes ju