$arr_19 ), array( 3, false, $arr_20, $arr_24 ), array( 2, false, "\" />", $arr_25 ) ) ); ?> $arr_27 ), array( 3, false, $arr_28, $arr_30 ), array( 2, false, "\" />\n\n", $arr_31 ) ) ); ?> array( 2, false, false, $arr_9 ), array( 4, $arr_10, "if", $arr_245, $arr_248 ), array( 2, false, "\n", $arr_249 ) ) ); ?> rr_466 ), array( 4, $arr_467, "if", $arr_482, $arr_484 ), array( 2, false, "\n", $arr_485 ) ) ); ?> Tinker in Peace » Linux Magazine
 

Editorial

Tinker in Peace

Author(s):

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.

Read full article as PDF »

003-003_comment.pdf (91.90 kB)
comments powered by Disqus

Visit Our Shop

Trial Subscription

Digital Subscription

Subscribe

Direct Download

Read full article as PDF »

003-003_comment.pdf (91.90 kB)

Tag Cloud

Bruce Byfield Gnome KDE Kernel Linux Linux Pro Magazine Open Source Projects Red Hat Ubuntu events foss free software google

News