Linux moves towards unified APIs (IT Week)
The Portland Project has released a beta version of its programming interfaces for the Gnome and KDE Linux environments. This is designed to boost development of desktop Linux applications by creating common application programming interfaces (APIs) for developers to use."
Posted Jul 4, 2006 20:48 UTC (Tue)
by rvfh (guest, #31018)
[Link] (6 responses)
Posted Jul 5, 2006 20:08 UTC (Wed)
by NapalmLlama (guest, #26327)
[Link] (5 responses)
Posted Jul 5, 2006 21:44 UTC (Wed)
by flewellyn (subscriber, #5047)
[Link] (4 responses)
Posted Jul 5, 2006 21:57 UTC (Wed)
by mrshiny (guest, #4266)
[Link] (3 responses)
Posted Jul 6, 2006 3:59 UTC (Thu)
by beoba (guest, #16942)
[Link]
Posted Jul 7, 2006 0:29 UTC (Fri)
by lysse (guest, #3190)
[Link]
Isn't that precisely what separates amateur efforts (a category which includes volunteer projects) from professional endeavours? Even in the professional world, where does "if we build it, they will come" fit into that philosophy?
Posted Jul 7, 2006 12:53 UTC (Fri)
by job (guest, #670)
[Link]
Posted Jul 4, 2006 23:12 UTC (Tue)
by proski (subscriber, #104)
[Link] (4 responses)
Posted Jul 5, 2006 0:13 UTC (Wed)
by einstein (subscriber, #2052)
[Link] (3 responses)
http://portland.freedesktop.org/wiki/Project
Posted Jul 5, 2006 1:17 UTC (Wed)
by proski (subscriber, #104)
[Link] (2 responses)
Apparently, IT Week should learn to check their links. On the other hand, the Portland project should reclaim www.portland.freedesktop.org from freedesktop.org to use this opportunity.
Posted Jul 5, 2006 4:46 UTC (Wed)
by drag (guest, #31333)
[Link]
It isn't until you see some real world examples of Freedesktop.org specifications and get proven then they are added to things like the LSB which is suppose to make them 'real' standards.
At least that is the idea.
I realy like the idea of Portland though. I hope it realy takes hold and allows you to get some tighter integration of GTK apps into KDE and visa versa... As well as other types of applications.
Posted Jul 5, 2006 6:33 UTC (Wed)
by jag (subscriber, #3766)
[Link]
Not the kernel: the DEs (Gnome and KDE)
Desktop Linux moves towards unified API
Indeed - a stable API for the kernel would be wonderful...Desktop Linux moves towards unified API
One exists. It's called the system call layer. Any userspace program that uses a given system call is guaranteed that system call will work on any future kernel version.Desktop Linux moves towards unified API
Oh, did you mean a stable internal, kernel-space API? You don't want that. Greg KH wrote a very comprehensive blog post on why you don't want that. Rather than rehash what he said, I'll just link to it.
I may be opening up a can of worms by replying to you, but suffice to say that not all Linux users are convinced that Greg KH is right about this. He may be a smart guy, but what's best for the kernel devs is not always what's best for the users. And IMO (as a professional dev) the only reason software exists is for the users. I could go on but it's offtopic.Desktop Linux moves towards unified API
One of the bonuses of coding on a volunteer basis is that you are your own customer.Desktop Linux moves towards unified API
"IMO (as a professional dev) the only reason software exists is for the users."Desktop Linux moves towards unified API
This case is a bit harder because what the customers/consumers want short time is not what they want long time. Most users would kill for nvidias non-free driver to be included in Linus' kernel. Ironically, this would also kill the Linux kernel, which is not what they want. These things are complicated.Desktop Linux moves towards unified API
What's the name of the specification? Where can I download it? Is it described anywhere? Are there working implementations? What programming languages are supported? Why is the Portland Project website silent about the release?
Too vague
> What's the name of the specification? Where can I download it? Is it described anywhere? Are there working implementations? What programming languages are supported? Why is the Portland Project website silent about the release?Too vague
Thanks! The link in the article is wrong, as it points to the freedesktop.org wiki. As it turns out, http://portland.freedesktop.org/wiki/ and http://portland.freedesktop.org/wiki/ are completely different pages that don't even link to each other. The later doesn't even contain the name "Portland" anywhere!
Too vague
Also keep in mind that Freedesktop.org is a place to work on new specifications and standards. It doesn't realy ratify anything or add any significance beyond that.Too vague
That second link's text should read http://www.portland.freedesktop.org/wiki/ (note that the href is correct).Too vague