About .NET … in the many years that I’ve been doing this thick/thin development I’ve been exposed to a lot of technologies. It’s impossible not to form preferences based on a personal sense of comfort, or to make decisions based on marketability. In short, I personally believe the .NET technologies (including Mono)  gives me the most flexibility, the best overall results, and solid commercial value for now and the future. I could go with passion and use (just an example) Perl, but all indications tell me that’s dead. I could go for "popular" but I can count on one hand how many times I’ve been asked for a Java solution in the MV market. I could go LAMP but the tools are just too primitive.

So I’m not biased toward .NET because of any particular affinity for Microsoft, it’s just been consistently a good solution – and as you say, you know I’ve looked at almost all of the others. I’m not shy about writing about non-.NET tech here. In fact my ongoing mantra is that we should always do our research for whatever might be (subjectively) "better". So I try to keep up with my research and I try to present my findings here for our colleagues.

I’m hesitent to do in-depth material on something like Ruby because, frankly, I don’t know anything about it. So I’ll leave such reviews to others with a clue – and I’ll be happy to link to material written by others if it seems of interest to the MV community. But I’m doing more work with "JACXX" stuff these days so I may write some material, for example, focused on JavaScript integration with MV.

And as long as your notes about Winnix are related to the content I have no problem with you mentioning your fine product.

Regards
T