« March 2005 | Main | May 2005 »

April 30, 2005

Virtualization to be Part of the OS

Microsoft plans to build virtualization support into the operating system with Longhorn, and may ultimately drop Virtual PC and Virtual Server.

It doesn't sound like exactly what I'm looking for, but interesting none the less.

Posted on April 30, 2005 at 07:42 PM | Permalink | Comments (0)

April 28, 2005

Cold Fusion (for real)

A device the size of a egg fuses Deuterium and spits out neutrons.

I just love this quote:

"This development, which scientists heralded as "amazing," has no practical application at the moment..."

Posted on April 28, 2005 at 01:01 PM | Permalink | Comments (0)

April 24, 2005

You Eat What you Are

Japanese researchers put a human gene in rice.

For some time, biotech companies have been splicing genes into plants to make them resistant to herbicides. This lets you, for example, spray your entire corn field with Round-Up, and not exterminate your crop. However, the genes have been selective, confering resistance to generally a single herbacide. When you spray with the same herbacide every year, the weeds can build up immunity.

However, by inserting a human liver gene into rice, Japanese researchers have created a plant that is resistant to as many as 13 herbacides.

More of my wild speculation about this kind of thing here, and here.

Posted on April 24, 2005 at 06:24 PM | Permalink | Comments (0)

One note on VB.NET Refactoring...


The VB.NET Refactor! tool will work with the full Visual Studio, but it's not support with just VB Express.

Posted on April 24, 2005 at 06:17 PM | Permalink | Comments (0)

April 21, 2005

Microsoft Provides Refactoring for VB.NET

Microsoft is providing refactoring for VB.NET after all. Woo Hoo.

Posted on April 21, 2005 at 02:35 PM | Permalink | Comments (0)

April 20, 2005

The product doesn't ship until the Customer says it's ready.


Posted on April 20, 2005 at 05:39 PM | Permalink | Comments (0)


It looks like Microsoft is planning some significant improvements on the virtualizaiton front. Good news, esp. about the support for the Intel Vanderpool technology (which moves more of the virtualizaiton work into the chip), and 64 bit support.

But, to me, the holy grail is an operating system that's designed from the ground up for virtualization. I want an OS that clearly separates the "code segment" from the "data segment". Meaning, I want the OS isolated from applications, which are isolated from application/user data, such that I can use one OS binary for many configurations, the gain being that when I apply SP2 to my OS portion of the image, all my images get it (and I don't have to patch each one individually).

Posted on April 20, 2005 at 05:30 PM | Permalink | Comments (0)

April 19, 2005

We are behoovant of you.

Julia points to a great MSDN editorial about the sin of inventing technical words when existing words would work just fine.

We see this across many industries. Ever read a legal contract? It's written in English, and yet you need to pay someone $250 per hour to tell you what it says, or to write down what you mean. Many professional domains develop their own code. I think it's on purpose. It's to separate those who are in the cult club from those who aren't. If you don't have the decoder ring, you can't understand what someone is saying. The medical profession does the same thing. Do we need anterior and posterior? Couldn't we just say "front" and "back"? If my doctor talks to me about abrasions or hematomas, is that servicing me better than saying "scrap", "clot" or "bruise"?

We have it to. We've all sat in a room and had a technical conversation, and afterwords, the non-techie in the room says "I have no idea what you were all talking about, but it seems like everyone's happy." Why? We all spoke English, or did we?

Within the techie culture, we develop accents so strong, they're unintelligible even to other technies from a different region. So you think it's an accident that a Java developer would have no idea what you mean if you say "Yukon is able to import assemblies and host the CLR allowing procedures to be implemented in managed code."


The problem is when you actually want to have a conversation with someone who doesn't speak Redmondian English, you want to convey information, and although the English language has the words you need, you haven't used them in so long that you can't find them any more.

Posted on April 19, 2005 at 10:38 PM | Permalink | Comments (1)

Paul Yuknewicz blogs on

Paul Yuknewicz has started blogging. Subscribed.

Posted on April 19, 2005 at 05:12 PM | Permalink | Comments (0)


I thought SkypeOut was cool. It's nothing compared to SkypeIn. For $13 for 3 months, I have a local Portland Oregon phone number that anyone can call to reach me while I travel through Latin America. Magic.

Posted on April 19, 2005 at 02:42 PM | Permalink | Comments (0)