Slashdot Mirror
Interview With Jordan Hubbard
Jeremy Andrews writes: "KernelTrap has interviewed kernel hacker and guru Jordan Hubbard, one of the creators of FreeBSD and currently a manager of Apple's Darwin project. With just a high school education, Jordan has offered some impressive contributions to the world of computing.
In this interview, Jordan talks about his current involvement with Darwin, as well as his past efforts with FreeBSD and 386BSD. He also reflects on his recent decision to step down from the core FreeBSD team."
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It's when you get distracted by the politickers that they sideline you. The tireless work that you perform keeping the system clean and building is what provides the platform for the obsessives and the prima donnas to have their moments in the sun. In the end, we need you all; in order to go forwards we must first avoid going backwards.
To the paranoid conspiracy theorists - yes, I work for Apple too. No, my resignation wasn't on Steve's direct orders, or in any way related to work I'm doing, may do, may not do, or indeed what was in the tea I had at lunchtime today. It's about real problems that the project faces, real problems that the project has brought upon itself. You can't escape them by inventing excuses about outside influence, the problem stems from within.
To the politically obsessed - give it a break, if you can. No, the project isn't a lemonade stand anymore, but it's not a world-spanning corporate juggernaut either and some of the more grandiose visions going around are in need of a solid dose of reality. Keep it simple, stupid.
To the grandstanders, the prima donnas, and anyone that thinks that they can hold the project to ransom for their own agenda - give it a break, if you can. When the current core were elected, we took a conscious stand against vigorous sanctions, and some of you have exploited that. A new core is going to have to decide whether to repeat this mistake or get tough. I hope they learn from our errors.
Future
I started work on FreeBSD because it was fun. If I'm going to continue, it has to be fun again. There are things I still feel obligated to do, and with any luck I'll find the time to meet those obligations.
However I don't feel an obligation to get involved in the political mess the project is in right now. I tried, I burnt out. I don't feel that my efforts were worthwhile. So I won't be standing for election, I won't be shouting from the sidelines, and I probably won't vote in the next round of ballots.
You could say I'm packing up my toys. I'm not going home just yet, but I'm not going to play unless you can work out how to make the project somewhere fun to be again.
= Mike
--
So why now? Why did *BSD fail? Once you get past the fact that *BSD is fragmented between a myriad of incompatible kernels, there is the historical record of failure and of failed operating systems. *BSD experienced moderate success about 15 years ago in academic circles. Since then it has been in steady decline. We all know *BSD keeps losing market share but why? Is it the problematic personalities of many of the key players? Or is it larger than their troubled personalities?
The record is clear on one thing: no operating system has ever come back from the grave. Efforts to resuscitate *BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful *BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for *BSD.
Netcraft officially confirms: *BSD is dying
Yet another crippling bombshell hit the beleaguered *BSD community when recently IDC confirmed that *BSD accounts for less than a fraction of 1 percent of all servers. Coming on the heels of the latest Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as further exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. FreeBSD is the most endangered of them all, having lost 93% of its core developers.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and *BSD's long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dbblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
By Chinese Karma Whore, Version 1.0
Everyone knows bout BSD's failure and imminent demise. As we pore over the history of BS, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to avoid so as to save Linux from a similarly grisly fate.
Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.
These early triumphs would soon be forgotten in a series of internal conflicts that would mar BSD's progress. In 1992, AT&T filed suit against Berkeley Software, claiming that proprietary code agreements had been haphazardly violated. In the same year, BSD filed countersuit, reciprocating bad intentions and fueling internal rivalry. While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.
As personal rivalries took precedence over a quality product, BSD's codebase became worse and worse. As we all know, incompatibilities between each BSD distribution make code sharing an arduous task. Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.
Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach. As argued by Eric Raymond in his watershed essay, The Cathedral and the Bazaar, rapid, decentralized development models are inherently superior to slow, centralized ones in software development. BSD developers never heeded Mr. Raymond's lesson and insisted that centralized models lead to 'cleaner code.' Don't believe their hype - BSD's development model has significantly impaired its progress. Any achievements that BSD managed to make were nullified by the BSD license, which allows corporations and coders alike to reap profits without reciprocating the goodwill of open-source. Fortunately, Linux is not prone to this exploitation, as it is licensed under the GPL.
The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become bureaucratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.
begin 644 bsd-is-dying.txtJ oMr7VNbEUO43n64BjP aNdQapZN1cUm 64BmOL-kP4ZiN m-WPqpWQqVZ2 64BjPKppPaZoS G-rO4Ji657Ze EZB2643XMqxpP bFn64NjQW-gZ QaBZPbEUPqMUM Klg65BZQbNZU R4VZ64lVR4JnR 0-CNLFXQa3ao NLAUR4VVR0+eE ZB264VVQm-gn 64tZRrAUQqJmR aJn65Fj657Zg P0-VP4xiNmsU8 Y7HF0-dQm-Xm Qa3t90-VQm-aO LFoOKtbP5YUY 64lVQrEUKrBVP K3b9aBjPJoUh Q57ZO4JiQqZqN G-iNLFrPr7fY 65Fj647Z642UG r7ZQqhdPW-P2 7rAUNbJoRL7Z9 W-IO4IUO43ie EZB264NVMqJn6 42UMalZMKgUo 647Z643iSG-aR LFpQaIUMLEUd Qm-YSKZiNmsUJ 4VdPaRn643m2 9W--Qm-hMKtt6 4xa65Jn643md PbJZQm-oPm-gP rBZ64pVQahZZ 642UQaZqNL6UP qMUMaljPqEib NL7ZN0-jNW-oO 4Jh643gP0kUZ 64FZRaJgPr-ZQ bAi1EcB0YlZg Pqxf643o65FcN G-iRKpWNL7nn R43oNLAUR4VVR 0-oO4JmNG-V6 PrQUPK3iSG-pQ qJmQm-jNW-Ci 63FcNG-iRKpWN L6UPqMUHr-Zi 63JnNKtZR0-dQ m-mPrJbO4lta Pr7Z65FcNL7Z6 43mNG-VMaxpm QmsUEZB29oxH6 5-jQrFn64xio O4IURaxgRKpZ6 4xa62tZR27Hm NG-VMaxpR0+rA 1+URLBZQbAUZ 65-pR0-4QaJZE ZB2643o643WU PK3mOqJo9W-IO 4JmNKNjQaIUo 61oUAnMoA1+UF b7ZNI7HF0-pd R4UUR4VZ64tpP K7ZQW-jNW-4p NG-oPm-oO4IUR 57jRK7gNLAUV P4Jn643iN0-nP m-jPWkUFb7ZV PaEURq3n65FVO qJi64xqNL6Um PrJWP4JY62xH9 W-CPrQUEZB2U R5JmPaJY64xqN L6UR4wUSKJoB 0Y3gP0-hMKdjQ W-nRL7qNLZng SG-YNKBgOKtZN 0-dPW-hML7ff 643iN0-dR5AUP 4xiNm-oNL7hm SG-YOKoi62Za6 0d0IoEUOLAUW NG-VPKxiNm-DI m-cPq7WSKZnU R4wUN4JXMLYi6 2tjR4VdPaQUV RaIUOLEUMLEUR 4VdQm-kPqZiV P0-kRL7kPrBZQ mkU8Y7HF0-dY SKZiNm+B0W+B
hGLEUOLAUPaxr64xaNaZXOK3g60oUHa
h8Y7HF0-dQm-YSKZiNm+B0ZZZR0-VPaxoO4J
hP4kUO4Zo65FcNG-WNKlZMKRpNL7ZN0+eEZB
hMqJiR4lt62Z2Em-XPqtaOL7hNKEUR4VVR0+
hNLBn65FcMKsUMG-aQa3XR4ZjPW-jNW+l65-
hQbAi62BjPKZiNm-jPW-oO4IUO4JZP5AUPqM
hR0-nRL7qNLYURqVdMqUUQ4lVOKtgSG-nR43
hPrBo64pjQaIUPK3mOqJo65BcML7Z90-oO4Z
hOKtaPr7XNG-rO43o65RZ7rNZ64hiPrRi643
hPqlgML-nOKtb64Zi64BjPL-gNLFZ64FdQq3
hNLVZPL-gOKNdNKEUMbYUNa3dP4ZiNm-YNK3
hOKsUR4VZ657ZMqJiR0-HSLAUEKFhOKsUMqx
hOKtb65FZQrEi1EcB0ZZjRG-YPqsbR0-iNKJ
hMKpYNLBo9aBjPJoUR4wUQ57ZN4ZXR0+eEZB
hN0-rQaZoOKtb64Zn64xi65FcNG-rMKlgCW+
hNbJoRL7Z9W-7PW-aMKBo65FcNL7Z65RjPWR
hMKlg64NjQW+eEZB2647ZMq3pQqIU8Y7HF0-
hNG-gPqxfOKtb65NZQbYUMa3Y64NjQW+eEZB
hNG-VP57ZMKFt643rML7Z90+eEZB264BjPbF
hR0-nO43mNGsUIaJY64ZiOm-aP4xrQm-gOKh
h62NmNKJ0IoEUOLAUR4VZ64pjQrEUNKtYMKt
hO43qOKtb64ljQrEUCHAZ64xa64ZoQm-XPr7
hR0Rn64hZNL+UR4wUR4VZ64NVMrFn643iN0-
h9W+B0Uo8Hr-ZPY7HF0-gNK3YNL6UJ4VZPm-
hQaIUBn+kA0-pQqJmQm-jNW-DQ4JiEZB29W-
hNLF0IoEUML7Z65FcNL7ZDm-ANLEbQm-nNKI
hPY7HF0-qNL7nRLAUHaJoEZB265-jQrFn64x
h64Zi657VR4Zj64xa61IUR4wUAGsUJ4VZQaJ
hR0+rA1+k9nIUDG+lB1+k62tZR27HF0-pQqJ
h63JnNKtZR0-VQaIUMK7jRLEUO43gNW-jNW-
hF0-kPrBoQmsUJ4VZQaJaPr7Z65FcNL7Z643
hPqMUEZB29oxH9W--657ZMqJiR0-VQbFdMql
hPrJo61Uk65-ZQaBZPbEUPqMUR4VZ60d0IoE
hR4VZQaIUML7Z60UrA1+k8n2oA1+fBn+k8Gc
hQqJmQmsUJ4VdQm-dQm-XPqtnOLBoNKto65R
hQaJZEZB263JnNKtZR0-kPrBoQmsU1EcB0YF
hPqMUJq3gPbJo62BmNKJf90-VMbZnPK3g65B
hNI7HF0-rNKto64xpR0-jNW-WRLBdPaJnQm-
hMbYUEZB2GG-rO4wUQqJgP0-VPaxoO4Jm65F
hGG-dQm-VP5Bj64FZMKEg64ZoQm-XPr7kQqI
h643iPrFcNL6UMqVVQatZP0-cPrJnNGsU1Ec
h65BcPrQUR4VVR0+eEZB264VVQm-nR4JVN4Z
hNLEUQqVVQaIi60d0IoEUOLAURaJmSG-nOKB
h65BpQbNdRa3g65-mPrBkNKBoQm-VQaIURaJ
hR4wUQrJmRaZqNG-VR0-VP4kUOLEURqZgP0-
hR0-YMK7WP4JmQmsU8Y7HF0-XPqtoOKtpNLA
hQqVjQbEUPqMUMG-hOL7VMqlZ64BjRKlY65B
hR0-dPW-oOKpZ9W-4Pr6UMKlg65-mMKBoOKB
WQm-YNK3Y9W+B0Uo8Fa3XR1cU8Y7HF0-dQm-
+
end