This is an old revision of this page, as edited by 59.182.254.31 (talk) at 11:07, 12 July 2014 (→Controversies: Accidental revert reversed.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 11:07, 12 July 2014 by 59.182.254.31 (talk) (→Controversies: Accidental revert reversed.)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
Lennart Poettering | |
---|---|
Poettering in December 2012 | |
Born | Guatemala City |
Nationality | German |
Occupation | Software engineer |
Employer | Red Hat |
Known for | Avahi, PulseAudio, systemd |
Website | 0pointer |
Lennart Poettering is a German computer programmer best known for his work on some highly controversial free and open source software including PulseAudio, a sound server, the systemd replacement for the System V init daemon, and Avahi, an implementation of the zeroconf protocol for network device discovery.
Life and career
Poettering was born in Guatemala City but grew up in Rio de Janeiro, Brazil, and Hamburg, Germany. Poettering currently works for Red Hat. Poettering is a long term contributor of the GNOME project, a GNOME Foundation member and a regular speaker at the GUADEC conference.
Lennart Poettering is a hobbyist photographer with a special interest in travel pictures, usually taken during extended trips near the conferences where he is invited. He has created a collection of more than a hundred stitched panoramas.
Since 2003, Poettering has worked in more than 40 software projects, mainly written in C and related to solution stacks in areas like multimedia (PulseAudio), networking, telephony and system startup (systemd) on Linux.
Poettering is a key developer of kdbus, a Linux kernel-based re-implementation of D-Bus, a topic which was publicly presented, by himself, for the first time during Linux.conf.au 2014.
A medium term goal that Lennart is working on seems to be "Sandboxed Applications for GNOME/Linux".
Poettering recommends reading The Linux Programming Interface but ignoring the POSIX-specific parts.
Controversies
Poettering is known for having controversial technical and architectural positions regarding the linux ecosystem.
For instance, Poettering, who is the main developer of PulseAudio, praised the Windows and MacOS audio stacks as "more advanced".
On the question of why the Linux desktop hasn't been adopted by the mainstream users yet, Poettering voiced the opinion that "Linux is still too fragmented... needs to be streamlined...",.
Poettering has also advocated speeding up Linux development at the expense of breaking compatibility with POSIX and other unices like the BSDs, Poettering took this decision because of his experience in writing some other low-level components in the desktop stack. He even goes further with this provocative invitation to other developers to do the same.
References
- "LPC: Linux audio: it's a mess". Lwn.net. Archived from the original on 2009-10-18. Retrieved 2009-07-03.
- Michael Larabel (2010-08-23). "An Update On The SystemD System & Session Manager". Phoronix. Retrieved 2013-01-29.
- "Using Avahi The 'Right Way'", linux.conf.au 2007
- linux.conf.au profile
- 2011 FOSDEM interview
- "glib main loop".
- "GNOME 3.0 Is Out!".
- "GNOME Foundation Members". Retrieved 2013-01-26.
- http://0pointer.de/photos/
- http://0pointer.de/static/panoramas.cgi
- Personal Blog, retrieved 2013-01-26
- https://lca2014.linux.org.au/schedule/30120/view_talk?day=None
- "GNOME developers plan "Linux apps"". Heinz Heise. 2013-02-06.
- "Sandboxed Applications for GNOME" (pdf). 2013-05-24.
- "Apps for GNOME desktops". LWN.net. 2013-08-07.
- "GNOME Wiki: Sandboxing".
- ^ "Un entretien avec Lennart Poettering". 2011-07-06. Retrieved 2013-01-26.
Both Windows and MacOS have much better integrated audio stacks than we have. We have a couple of unique features they can't match, like networking support, lower latency behavior, or float-less audio pipelines, but in general the CoreAudio stack is definitely more advanced than ours. The distance, however, is much smaller than it used to be. The Windows stack is much less suitable as a benchmark, and we are matching its features much better than CoreAudio's, but there's no doubt that it is probably still a better integrated audio hacking experience to develop for Windows.
- ^ "Interview: Lennart Poettering - Lennart Poettering will give a talk about "Systemd: beyond init" at FOSDEM 2011". fosdem.org. 2011. Retrieved 2014-06-16.
Many of my previous projects (including PulseAudio and Avahi) have been written to be portable. Being relieved from the chains that the requirement for portability puts on you is quite liberating. While ensuring portability when working on high-level applications is not necessarily a difficult job it becomes increasingly more difficult if the stuff you work on is a system component (which systemd, PulseAudio and Avahi are).
- ^ "Interview: Lennart Poettering - Lennart Poettering will give a talk about "Systemd: beyond init" at FOSDEM 2011". fosdem.org. 2011. Retrieved 2014-06-16.
In fact, the way I see things the Linux API has been taking the role of the POSIX API and Linux is the focal point of all Free Software development. Due to that I can only recommend developers to try to hack with only Linux in mind and experience the freedom and the opportunities this offers you. So, get yourself a copy of The Linux Programming Interface, ignore everything it says about POSIX compatibility and hack away your amazing Linux software. It's quite relieving!
- "Un entretien avec Lennart Poettering". 2011-07-06. Retrieved 2013-01-26.
I think we weren't innovative enough in the interface, and we didn't have a convincing message and clear platform. If you accept MacOS as benchmark for user interfaces, then we weren't really matching it, at best copying it. I think this is changing now, with GNOME 3 which is a big step forward as an interface for Linux and for the first time is something that has been strictly designed under UI design guidelines. So we now have a better interface, leaves the message and the clear platform. Linux is still too fragmented, and a developer targeting Linux will have to choose from a variety of APIs, a bazaar of somewhat matching but mostly just chaotic choices that will work on some systems but not on others. I think it would be in our greatest interest to streamline the platform top to bottom, and thus have a clear message what the Linux OS is. And of course, I believe my work in cleaning up the lower levels of our userspace stack is helping to work in that direction. Getting a clear message out what Linux is supposed to be is definitely a social issue, but to make that happen the Linux platform needs to be streamlined first, and that's a technical task, and not done yet.
- "Choosing between portability and innovation". lwn.net. 2011-03-02.
POSIX is really an encapsulation of some choices that various Unix systems made along the way, rather than a body of text that got standardized and then implemented. According to Poettering, Linux should use its position as "market leader" (in the market of free Unix-like operating systems) and try out some new things. If developers don't force themselves into the constraints of the POSIX API, they could develop some really innovative software, like systemd shows. When these new developments happen to turn out really interesting, other operating systems could eventually adopt them as well.
- "FOSDEM 2011 interview". 2011-02-06.
Not having to care about portability has two big advantages: we can make maximum use of what the modern Linux kernel offers these days without headaches -- Linux is one of the most powerful kernels in existence, but many of its features have not been used by the previous solutions. And secondly, it greatly simplifies our code and makes it shorter: since we never need to abstract OS interfaces the amount of glue code is minimal, and hence what we gain is a smaller chance to create bugs, a smaller chance of confusing the reader of the code (hence better maintainability) and a smaller footprint.
External links
This biographical article relating to a computer specialist is a stub. You can help Misplaced Pages by expanding it. |