Home Business IT Open Source Torvalds pours scorn on De Icaza's desktop claims
Torvalds pours scorn on De Icaza's desktop claims Featured

Prior to this post, senior kernel developer Alan Cox responded to another part of De Icaza's post which ran this way: "The second dimension to the problem is that no two Linux distributions agreed on which core components the system should use."

"That made me laugh," Cox wrote on Ramkrishna's G+ page. "There was KDE and Miguel then came along and created the very confusion he's ranting about. He was also core to ramming CORBA down peoples throats which then had to be extracted slowly back out of the resulting mess that blighted Gnome 2.x and occupied vast amounts of developer time.

"He's dead right about the way the Gnome people keep breaking their compatibility every (sic) time not just with the apps but with the UI, with the config (which is still worse now than in Gnome 1.x !) and so on.

"However it's not an Open Source disease its certain projects like Gnome disease - my 3.6rc kernel will still run a Rogue binary built in 1992. X is back compatible to apps far older than Linux.

"As for his ranting about the audio I blame Lennart Poettering... - the kernel audio hasn't broken compatibility, it even has OSS compat layers back to the beginning of Linux audio support. Actually blaming Pulseaudio is mean too (but it's fun blaming Lennart and that's what he exists for) - it also has compat stuff designed to make ancient apps just work...

"Gnome isn't really a desktop anyway - it's a research project."

De Icaza made a couple of posts on Ramkrishna's page, reiterating the views in his blog post.

 

WEBINAR 7th May 11am - WOW 802.11

Learn how Ruckus Redefines High-Speed, High Capacity Wi-Fi with Industry’s First 802.11ac Wave 2 Access Point

THIS IS ONE NOT TO MISS SO REGISTER NOW

DON'T MISS OUT - REGISTER NOW!

FREE WHITEPAPER - RISKS OF MOVING DATABASES TO VMWARE

VMware changed the rules about the server resources required to keep a database responding

It's now more difficult for DBAs to see interaction between the database and server resources

This whitepaper highlights the key differences between performance management between physical and virtual servers, and maps out the five most common trouble spots when moving production databases to VMware

1. Innacurate metrics
2. Dynamic resource allocation
3. No control over Host Resources
4. Limited DBA visibility
5. Mutual ignorance

Don't move your database to VMware before learning about these potential risks, download this FREE Whitepaper now!

DOWNLOAD!

Sam Varghese

website statistics

A professional journalist with decades of experience, Sam for nine years used DOS and then Windows, which led him to start experimenting with GNU/Linux in 1998. Since then he has written widely about the use of both free and open source software, and the people behind the code. His personal blog is titled Irregular Expression.

Connect