Izhido posted on Tuesday, October 24, 2006
Hi!
This question is bugging me a lot since many many months ago. I want (someday) to create my own implementation of the Common Language Specification, specifically my own VES (the runtime, if you follow me), in order to use it:
1. in as many platforms as it is possible (or having any sense);
2. as a part of a larger project
Also, I'd like it's functionality to match as closely as possible to
the .NET Framework, so anyone could use VS tools (if they wish) to
develop for it.
Of course, I know about Mono & DotGNU; what I want here is to develop the runtime with a new perspective, including some ideas I've gathered through my life as a developer.
BUT...
http://en.wikipedia.org/wiki/Common_Language_Infrastructure (see "Standardization and Licensing")
I'm not sure I'm understanding this. Could it be possible that, if I implement my own VES, by my own means (read "not using ROTOR source code, but using every single piece of CLI documentation available to the public"), and distribute it so everyone can use / develop with / develop FOR it, then someday suddenly MS, HP et al. knock at my doors telling me "sorry, you're screwed BIG TIME, see you at court..." ?
And, if so, how the %$/$&/$@ did Novell/FSF do to avoid this? (Or even worse, did they NOT???)
Sorry for the harsh language. This is one of my most cherished project ideas, and it would be a shame (for me, at least) to see it going into the drain because of patent & licensing issues that... um... sorry for this...
SHOULD
HAVE
NEVER
EXISTED
ANYWAY
???? . Whew, felt better.
Could you people please share your thoughts on this? Thank you!