Feeds

Mono man accuses Mac Gtk+ fans of jeopardizing Linux desktop

Trading hard ISV gains for the easy compile

The essential guide to IT transformation

Miguel de Icaza has criticized plans for the next GNU Gnome cross-platform environment that risks damaging the Linux desktop ISV ecosystem by focusing on the Mac.

De Icaza, leading the Mono and Moonlight cross-platform .NET projects at Novell, has warned a "new crop" of developers pushing plans for Gtk+ 3 risk "throwing away years of work" on Gtk+. They're also failing to recognize the value of having an ISV ecosystem working to put Gnome on Linux. Gtk+ is the tool set for building the Gnome graphical user interface, with version three the next planned major update.

According to de Icaza, developers working for Gtk+ specialist Imendio pushing the proposal have "given up on the Linux/Gnome desktop." Having switched to Apple's OS X as their main desktop, they are focused on source code compiling to Macs with some changes, instead.

OS X has seen growing uptake among developers, and Apple has enjoyed a resurgence as a laptop and desktop system at Windows Vista's expense. Linux on the desktop remains, as ever, stuck somewhere in the distant future.

De Icaza is the biggest and highest profile voice so far to complain publicly about the proposed toolkit changes, here and here.

He expressed concerns following recent Gnome developer and user conferences in Germany and Turkey, where Imendio has presented its proposal (warning: PDF) to the community.

Imendio has advocated breaking the Gtk application programming and application binary interfaces every five years, removing "deprecated" code each five years starting with GTK+ 3.0, in what appears to be an attempt to reduce the size of Gnome, and hiding public structured fields - a move that could potentially allow for easier versioning while maintaining binary compatibility.

While de Icaza has said he's not against breaking the API, he's concerned the Imendio team has not provided a roadmap to justify breakage beyond simply talking about new - but unspecified - future features. He also expressed concern about what appeared to be a lack of participation in Gtk+ discussions by users and developers working with Gtk+. That includes his employer Novell, Red Hat, Adobe Systems and VMware, among others.

De Icaza has called for a clear roadmap over a "wait and see" approach with input from others, working code before breaking the API, and a clear transition from the current 2.x generation of Gtk+ to version 3.0.®

5 things you didn’t know about cloud backup

More from The Register

next story
Microsoft boots 1,500 dodgy apps from the Windows Store
DEVELOPERS! DEVELOPERS! DEVELOPERS! Naughty, misleading developers!
Apple promises to lift Curse of the Drained iPhone 5 Battery
Have you tried turning it off and...? Never mind, here's a replacement
Mozilla's 'Tiles' ads debut in new Firefox nightlies
You can try turning them off and on again
Linux turns 23 and Linus Torvalds celebrates as only he can
No, not with swearing, but by controlling the release cycle
Scratched PC-dispatch patch patched, hatched in batch rematch
Windows security update fixed after triggering blue screens (and screams) of death
prev story

Whitepapers

Endpoint data privacy in the cloud is easier than you think
Innovations in encryption and storage resolve issues of data privacy and key requirements for companies to look for in a solution.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Advanced data protection for your virtualized environments
Find a natural fit for optimizing protection for the often resource-constrained data protection process found in virtual environments.
Boost IT visibility and business value
How building a great service catalog relieves pressure points and demonstrates the value of IT service management.
Next gen security for virtualised datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.