To view parent comment, click here.
To read all comments associated with this story, please click here.
You are so delusional, what "crap" are you talking about?
OOXML became an ISO standard, tell me, how did that affected ISO? and what with the fact MS didn't comply entirely with the specification? is not mandatory, just like no browser comply with HTML 5. MS implemented the requirements of the ISO, yeah, even fixing the part of the OOXML specification to make it more open, but hey, Groklaw's and you don't care or omit the history.
So don't try to tell me what happened cause I was also there reading Groklaw's non sense and the opinionated trolls that follow it.
And again, you point to a post by a crack pot who has a beef against PJ over a subject he is wholly invested in. And she wasn't wrong. Parts of .Net like ASP are still patent encumbered. Oh, and Moonlight, the beacon in the sky for the reason to everyone to use Mono, got cancelled.
You are clueless, Groklaw was making statements not on ASP.NET or mono, it was making wrong statements on the MS PL, the open source license apache like licesen from MS, so, come back here when you actually read the article.
I was taking your word for the gripe and not doing my fact checking. Guess I shouldn't have. Groklaw isn't even the target of that article. Pundit #1 as Miguel puts it, is Steven Vaughan-Nichols. His point was valid, as Miguel spends most of the post talking about how GNU had to battle the same concerns back in the day. He even confirms that the fear exists at Mono as they have rules about such things. Still, as Steven states, people can and do break rules. See the AT&T vs BSD lawsuit for examples of code transfer going both ways.
Pundit #2 appears to be Matt Asay. I am not sure if he is affiliated with Groklaw, but the article was originally posted to Cnet. And if you read the article, the very next line Matt writes after the quoted text is "In other words, it's not open source. But is it good for developers, anyway?" The article does not in any way say that "Microsoft open sourced .NET".
So who has the real axe to grind?





Member since:
2006-01-14
OOXML? Are you serious? PJ was pretty much spot on about that steaming pile of crap. Microsoft pushed its standard through the ISO. Even now they don't conform to their own standard. In the process they also pretty much broke the ISO, causing a lot of problem for everyone.
And again, you point to a post by a crack pot who has a beef against PJ over a subject he is wholly invested in. And she wasn't wrong. Parts of .Net like ASP are still patent encumbered. Oh, and Moonlight, the beacon in the sky for the reason to everyone to use Mono, got cancelled.
Her original point still stands. Microsoft declared war on Linux, so why should anyone trust them. Its not like they would go around extorting money over vague and changing patent claims on software that is clearly open source. Oh wait.....