SourceForge Drifting
Zocalo sent us a story running at FSF Europe talking about SourceForge's Drifting. Talks about the fact that they are releasing a closed-source version of the code commercially and various copyright related things. Obviously VA owns both SF and Slashdot so I'm skewed, but my personal opinion is that VA is doing what they need to do to make a buck while still providing the SourceForge.net website to the Open Source community. And I think their decision to sell a closed-source proprietary version of the code would be hypocritical, except that they aren't a 100% open-source company any more. And *that* is the part that makes me the most sad.
Obviously you didn't delve too deeply into Linux based on your paragraph about what Linux lacks support for. You say "Not to mention the fact that the Linux kernel itself lacks any support for any type of journaled filesystem, memory protection, SMP support, etc", but ALL of these points are wrong (even in the kernel version you were using).
Journalling file system: ReiserFS
memory protection: has been in since 0.x days. A kernel panic is a bug, not a lack of a feature. Also, the VM in 2.4.9 wasn't exactly stable. 2.4.14 is.
SMP: My experience is that SMP in linux works better than Win2k.
And don't think I am saying this because I hate MS products. I don't. I use Win2k/Exchange for my home network, and Win2k Pro on my laptops. But if you are going to pick on Linux, try finding something with a basis in fact.
DON'T update the article...
This is just another comment, and it's not clear that Hemos is really talking with any authority or first hand knowladge. In other words, in 6 months it is VERY VERY possible that sourceforge.net will be using stuff like Oracle etc.
That was my impression, and I'd like to hear WHY Hemos is so sure that will not happen before he goes and updates any articles. All to often folks post comments where they imply they know something with authority, when they really have just as little first hand knowladge as the rest of us who follow the issue closely.