Commentary

Serdar Yegulalp
 

Linux Kernel, Meet Windows Kernel. Behave.

Here's one for the "only in the Linux world" folder: an attempt to place the Windows NT kernel mechanisms directly in the Linux kernel. Am I the only one who thinks, outside of extremely specialized use cases, this isn't such a hot idea?

Here's one for the "only in the Linux world" folder: an attempt to place the Windows NT kernel mechanisms directly in the Linux kernel. Am I the only one who thinks, outside of extremely specialized use cases, this isn't such a hot idea?


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

To be fair, as a programming project, it's "dash clever", as one of my friends from England used to put it. (OSNews.com has some more technical details.) It's a perfect example of Linux's bend-me-shape-me-any-way-you-want-me ethos. It's sort of like a polar opposite of the Cooperative Linux project, where the Linux kernel is compiled as a native Windows binary.

But it's ultimately also the wrong approach, the wrong kind of clever, because it encourages that much less truly native Linux development -- not just the software itself, but the kernel's own progamming interfaces.

The best thing to do with the Linux kernel right now is to make sure it has a stable programming interface that makes writing binary applications for Linux itself as appealing as possible. That's up to the kernel team, of course, but the more they can be encouraged to include things that benefit Linux directly -- instead of Windows indirectly -- the better of Linux will be as a whole.

One very good thing this would allow -- and I cannot dispute this would be genuinely useful -- is allowing native Windows drivers to be used in Linux. But I have to balance that against the amount of work involved, and whether or not the same net effects can be garnered by making the stock Linux kernel that much better a place to write native drivers for in the first place.

I'm not against the mere idea of running Windows software on Linux. I just think it's the wrong solution to the wrong problem. You can do it if you have no other choice, but given how much software there is out there -- especially how much open source software that runs natively on both platforms anyway -- it's a disingenuous approach. Doubly so when virtual machines, dual-booting and the Wine layer already provide many different ways to skin that particular cat.

So: color me skeptical. I want to see this particular tree bear fruit before I go a-picking.


InformationWeek Analytics has published an independent analysis of the current state of open source adoption. Download the report here (registration required).


Follow me and the rest of InformationWeek on Twitter.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links