A closed-source code base is a huge, ever-fading inertial mass. When it begins, with those first exhilarating lines, or even up through the first few releases, you can truly say that you are writing it. But after a while, it is more like you are tending it – or feeding it. It becomes an investment, an asset, a castle you are protecting, which means all your strategies are defensive and your dreams will not stray far from your spot of holy ground.
The bigger and more grandiose a code base becomes, the more time and effort it takes to nurture and sustain it, and even with all your love and effort, it still starts to look ragged after enough time – no matter what you do or how much you care. When the time comes for it to become something completely different, you can’t just re-form it like silly putty. The best you can hope is to tweak it around the edges and force it into some kind of tenuous interface with the tools of the next generation. Eventually, the details of maintaining that interface start to undermine the aura of technical relevance one needs to sell the software. So it was with MS-DOS, Novell NetWare, and Mac OS 9.
The Raspberry Pi Foundation has announced an even smaller version of the tiny computer that will fit into a DIMM slot.
A new class of problems lets a malicious app pre-configure an invisible privilege update.
New Hack language adds static typing and other conveniences.
New crypto policy system will offer easier configuration and more uniform security.
Ubuntu founder denounces insecurity in proprietary, close-source software blobs.
Vulnerability affects many Linux web servers
The Bavarian capital shuns Microsoft, Google, and other alternatives to implement an open source groupware solution.
Phone vendor partnerships bring Mark Shuttleworth's dream of Ubuntu on a phone a step closer to reality.
Donors will get to vote on new features for the free video editor.
Debian project puts init out to pasture and says no to Ubuntu's Upstart.