"Oxite" doomed to the rust heap.
Microsoft's corporate-sponsored open source club, "MixOnline" has released a content management system called "Oxite".
It all looks pretty OK -- like YAWP; yet another WordPress. You might ask, "why do we need another?" and the only workable answer is "why not". It's not like it's going to kill anybody or anything and, hey, maybe it could be where the next really cool CMS/blogging idea comes from.
At least that's the way that's it looks until you get to the "requires ASP.NET" gotcha. And, come to think of it, I shouldn't say "that's the way it looks" because, frankly it "looks" pretty bad when something made with it (like it's own home site) is up and running in your web browser.
Even in it own (presumably) web browser; MSIE 7.
Go two or three pages into it and then "back" out... oops. Page Too Dynamic, Browser Get Confused, So Sorry, Bye.
Or; squeeze the home page for Oxite into a window slightly smaller than the page's internally set dimensions. Ooops again. Parts of backgrounds flicker in and out of existance. Blocks of text disappear.
OK; one might ask "why not" have another working CMS. But come on fellas. It's just a little transparent to make one that requires ASP.NET and, really, just give it up. I mean really; are you that rich that you can afford to create your own windmills and then spend more money tilting at them? LOL
But then to make one that doesn't even work? That's just making a bad rust joke; Microsoft.
