Well, I guess that's because they are talking about REAL robots, with embedded CPUs and controllers, not those brain-dead remote-controlled piece of crap they called BattleBots.
Standards and M$.... LOL; where have you been these past years?
What do you do when you are a big fat M$ Gorilla and you go play in the open and well regulated field of "standards"?
Let's say M$ Bill encounter Mr Kerberos Standard. Purely hypothetical situation, of course....
[Bill$:] Well, Mr Kerberos, would you mind if I hijack a little obscure part of your spec so that for now on, using this "innovation" to your standard, only M$ based clients will be able to talk Kerberos with M$ based servers? You see, I need this innovation for a pet project of mine called.NET$
[Mr Kerberos:] Well, Bill$, that would render my standard a bit weak dont you think? What about all the non-M$ clients and non-M$ servers out there? That would render them inoperative with M$ servers/apps wouldn't it?
[Bill$:] Of course not, those "less efficient and surely dying applications and servers" will have access to my clever "innovation" just by signing a Non Disclosure Agreement giving me access to to everything they own and breathe; or even better, they could simply switch to this brand innovation of mine,.NET$, the new and more secure way to do E-Busine$$.....
VRML is another standard. M$ participated in the development of this standard until its own VRML 2.0 proposition got rejected. M$ simply left the VRML standardisation effort. How well does VRML do these days? Does M$ Explorer support VRML natively?
VRML is a standard. It's got a life of his own... M$ is simply ignoring VRML....
Corba vs COM/DCOM.... Should I continue?....
M$ is big and heavy; when you are a planetary monopoly, you dictate the standards, not the other way around. And this, I know from experience.
I dont dispute the fact that C$ and.NET$ are useful; they are or will be as much useful as ActiveX and Outlook are. People (and viruses) all over the planet are using them. I know that, you know that.
My point is that M$ dont need us to develop C$ and.NET$ for Linux; they have plenty of bright monkeys to do that themselves, people with access to the "right documentation". Spending time doing this ourselves is a waste of time.
My point is that Java/J2EE is a much more mature alternative, and one alternative that M$ doesn't control well. Of course, Sun could have played the "standards" game with a bit more wisdom. But standards are not that important in a M$ monopoly world.
My point is that by developping for.NET$, we are potentially tying our open source code with M$ patents. M$ monkeys are happy. M$ lawyers are big, heavy, and smiling too.
Why reinvent the wheel when so much is available with J2EE/Java? Why not contribute to J2EE/Java on our own instead of diluting it's impact? J2EE/JBoss should be on our radar, not.NET
For me,.NET$ and C$ is a pure waste of time and opportunities. The M$ Gorilla is smiling.
Dont you all see the pattern here? Oh geez, let's all begin developping using this so neat C$ language and let's contribute to this so great.NET$ "innovation". Bill and his buffoons must be smoking a big fat one with a smile now.... And we are even lighting it for them...
The trap is set, and we are happily jumping on the trigger using both feet. Of course, Bill will help us out by releasing his.NET vital infrastructure source code real soon now, since we are so nice in contributing to the hype and fud ourselves. And of course, there is no way in hell Bill will pollute his own spec just for our own good and for the sake of his own pocket... Noooooo, of course not!
During this time, Java continues to die slowly, getting fewer and fewer developpers. Don't you realize that we are contributing in digging our own grave?
Java might be not so great, but it is still the only true alternative to this M$ obscenity.
Please people, read the J2EE spec, the Java language spec., and go play with JBoss for a while... Then, come back, and take another look at this.NET$ aberration and you will be the one laughing, not Bill and his monkeys.
Slashdot Mirror
Hum... Who???
Well, I guess that's because they are talking about REAL robots, with embedded CPUs and controllers, not those brain-dead remote-controlled piece of crap they called BattleBots.
Narrow minded people.....
Exactly.
It's so obvious it hurts.
Zruty
Standards and M$.... LOL; where have you been these past years?
.NET$
.NET$, the new and more secure way to do E-Busine$$. ....
...
....
.NET$ are useful; they are or will be as much useful as ActiveX and Outlook are. People (and viruses) all over the planet are using them. I know that, you know that.
.NET$ for Linux; they have plenty of bright monkeys to do that themselves, people with access to the "right documentation". Spending time doing this ourselves is a waste of time.
.NET$, we are potentially tying our open source code with M$ patents. M$ monkeys are happy. M$ lawyers are big, heavy, and smiling too.
.NET
.NET$ and C$ is a pure waste of time and opportunities. The M$ Gorilla is smiling.
What do you do when you are a big fat M$ Gorilla and you go play in the open and well regulated field of "standards"?
Let's say M$ Bill encounter Mr Kerberos Standard. Purely hypothetical situation, of course....
[Bill$:] Well, Mr Kerberos, would you mind if I hijack a little obscure part of your spec so that for now on, using this "innovation" to your standard, only M$ based clients will be able to talk Kerberos with M$ based servers? You see, I need this innovation for a pet project of mine called
[Mr Kerberos:] Well, Bill$, that would render my standard a bit weak dont you think? What about all the non-M$ clients and non-M$ servers out there? That would render them inoperative with M$ servers/apps wouldn't it?
[Bill$:] Of course not, those "less efficient and surely dying applications and servers" will have access to my clever "innovation" just by signing a Non Disclosure Agreement giving me access to to everything they own and breathe; or even better, they could simply switch to this brand innovation of mine,
VRML is another standard. M$ participated in the development of this standard until its own VRML 2.0 proposition got rejected. M$ simply left the VRML standardisation effort. How well does VRML do these days? Does M$ Explorer support VRML natively?
VRML is a standard. It's got a life of his own... M$ is simply ignoring VRML.
Corba vs COM/DCOM.... Should I continue?
M$ is big and heavy; when you are a planetary monopoly, you dictate the standards, not the other way around. And this, I know from experience.
I dont dispute the fact that C$ and
My point is that M$ dont need us to develop C$ and
My point is that Java/J2EE is a much more mature alternative, and one alternative that M$ doesn't control well. Of course, Sun could have played the "standards" game with a bit more wisdom. But standards are not that important in a M$ monopoly world.
My point is that by developping for
Why reinvent the wheel when so much is available with J2EE/Java? Why not contribute to J2EE/Java on our own instead of diluting it's impact? J2EE/JBoss should be on our radar, not
For me,
Zruty
This place is really getting full of M$ trolls.
.NET$ "innovation". Bill and his buffoons must be smoking a big fat one with a smile now.... And we are even lighting it for them...
.NET vital infrastructure source code real soon now, since we are so nice in contributing to the hype and fud ourselves. And of course, there is no way in hell Bill will pollute his own spec just for our own good and for the sake of his own pocket... Noooooo, of course not!
.NET$ aberration and you will be the one laughing, not Bill and his monkeys.
Dont you all see the pattern here? Oh geez, let's all begin developping using this so neat C$ language and let's contribute to this so great
The trap is set, and we are happily jumping on the trigger using both feet. Of course, Bill will help us out by releasing his
During this time, Java continues to die slowly, getting fewer and fewer developpers. Don't you realize that we are contributing in digging our own grave?
Java might be not so great, but it is still the only true alternative to this M$ obscenity.
Please people, read the J2EE spec, the Java language spec., and go play with JBoss for a while... Then, come back, and take another look at this
Wake up people!
Zruty