Perpetual motion controller

I have implemented systems for Windows NT requiring 24x7x365 usage. It does work quite well, as long as people can avoid adding these strange little hardware extras to the computer, and in the progress install a large number of more or less buggy drivers. After all, a very large number of blue-screens (yes, the color blue should sue M$ for the bad reputation) are from the drivers.

The Windows driver model is - in my view - quite lousy. Few people manages to produce reasonably bug-free Windows drivers, which directly results in a lot of complaints about unstable Windows machines. It really doesn't help how stable the kernel is if the drivers have critical bugs because they are too complicated to write.

But if I have the choice, I would prefer BSD or Linux before Windows. The source code availability increases the options available. The licensing fees allows inexpensive work with clusters or other redundant solutions. And there are a lot of server applications that have matured for 20 years or more in the unix world.

One thing to note is that the unix world decided to go for source-code compatiblity, whilw M$ strived for binary compatibility in Windows. Because of this, unix programs are normally written to auto-detect machine capabilities at compile time so you get very optimized binaries.

Another thing is that M$ is walking towards managed code. This may affect the market a lot when some of the following steps are taken and .NET becomes the native API - will WIN32 be emulated or an alternative API?

You'll have to wait for our captain to get feedback on his view of Unix or any of the derivatives.

"For someone like me, I am not smart,"
Define smart. A professor who gets home and afer a couple of hours are asked by his wife where the dog is? Skills tends to develop in different directions, often following our interests. In some parts of the world, it is considered smart to not walk into the wrong parts of the city.

I have implemented systems for Windows NT requiring 24x7x365 usage. It does work quite well, as long as people can avoid adding these strange little hardware extras to the computer, and in the progress install a large number of more or less buggy drivers. After all, a very large number of blue-screens (yes, the color blue should sue M$ for the bad reputation) are from the drivers.

The Windows driver model is - in my view - quite lousy. Few people manages to produce reasonably bug-free Windows drivers, which directly results in a lot of complaints about unstable Windows machines. It really doesn't help how stable the kernel is if the drivers have critical bugs because they are too complicated to write.

But if I have the choice, I would prefer BSD or Linux before Windows. The source code availability increases the options available. The licensing fees allows inexpensive work with clusters or other redundant solutions. And there are a lot of server applications that have matured for 20 years or more in the unix world.

One thing to note is that the unix world decided to go for source-code compatiblity, whilw M$ strived for binary compatibility in Windows. Because of this, unix programs are normally written to auto-detect machine capabilities at compile time so you get very optimized binaries.

Another thing is that M$ is walking towards managed code. This may affect the market a lot when some of the following steps are taken and .NET becomes the native API - will WIN32 be emulated or an alternative API?

You'll have to wait for our captain to get feedback on his view of Unix or any of the derivatives.

"For someone like me, I am not smart,"
Define smart. A professor who gets home and afer a couple of hours are asked by his wife where the dog is? Skills tends to develop in different directions, often following our interests. In some parts of the world, it is considered smart to not walk into the wrong parts of the city.