Open Source And Closed Standards?
jaaron writes "Can open source and closed standards work together? That's the question asked by Kevin Bedell in his O'Reilly weblog article. The issue springs from questions on an OSI mailing list, hinting that Sun Microsystems is looking for an open source license that would require derivatives to maintain test suite compatibility. Under such a scheme Sun could maintain control of the Java API but allow open implementations."
The only problem I forsee here is the proliferating of pseudo-Javas.
.cpp program, I can say with 95% reliability that it will compile under VC2003 or gcc 3.
I already don't care to learn Java- there are way too many "Java"'s out there already- 1.0, 1.1, 1.2, and more. The install is a complete bear, requiring playing with paths and the like under Win32- not fun!
Now, you take C++ or C or Lisp.
Old C++ is basically a subset of modern C++
Same for C and Lisp.
When I download a
I canna say that with Java. I've <i>tried</i>. I'm not blowing smoke here. Java implementations for me have tended to be flat out inferior than C or Lisp implementation in terms of cost of use.
*shrug* But we will see, yes?
/b
|f(x)dx = F(b) - F(a)
IT IS "LOSING" WITH A SINGLE "O" YOU MOTHER FUCKING CRETIN.
You don't know what a 'derived work' is, do you?