The Linux Kernel's Fuzzy Future (InformationWeek)
Posted Dec 6, 2004 20:21 UTC (Mon) by
Max.Hyre (subscriber, #1054)
Parent article:
The Linux Kernel's Fuzzy Future (InformationWeek)
[Copy of reply I posted on their site.]
Dear Mr. Foley:
I'm a bit puzzled by your article. When Microsoft supplies a
``roadmap'', it sounds like you're getting a chart of an area with all
the possible paths laid out for you to choose. In actuality, so far
as I can see, such a roadmap is more a travelogue describing the only
way you can go. Yes, it's nice to plan for what MS will offer next,
but there's not a lot of choice involved, especially if what you need
is missing.
Linux, on the other hand, has no roadmap because its advances are
unplanned---they occur as people improve on extant capabilities, and
others add what they need. Who could have planned IBM's addition of
JFS, or NUMA, or RCU three years before each was released? That
early, it was unclear whether IBM even planned to play nicely.
Under Linux, on the other hand, useful additions are rapid. If the
current kernel meets your specifications, why care about a roadmap?
If it doesn't, check whether anyone's working on the required
function. If so, send resources. If not, hire a kernel hacker or two
and add it now, not when a roadmap shows it's planned for. If the mod
is accepted into the mainline kernel, you're in clover. Even if it
isn't, you've still got the kernel you need, and if it's writeable
as a module, it won't be too hard to keep it current with newer kernel
releases.
So, what would a roadmap (assuming anyone could define and enforce
one) do for you? It's another unnecessary evil that has been
eliminated from Linux.
Best wishes,
Max Hyre
(
Log in to post comments)