The GPL infects everything it comes into direct contact with - put GPL code into a proprietry app, the app must go GPL, put add on proprietry code into a GPL app, the add on code must go GPL.
Methinks this only applies where the code is mixed though - if you never used their code and they never used yours, noone should be claiming rights over anyone else's stuff. I'm not sure about seperately developed plugins, but a plugin developed without any use of the main app's source is quite rare
In a democracy:
The people vote for who makes decisions, the voted person makes decisions.
I a political democracy (what we have):
The people vote for who makes the decisions, the voted person takes bribes.
The java 1.4 vm runs 1.0 1.1 1.2 and 1.3 code, the 1.2 vm even runs 1.3 code! The bytecodes are not the problem, even a major change can be picked up by version number in the class file and a different vm called, it's the heavily bloated libraries that make java slow.
Using JIT, java is compiled to the optimal native code for any platform, thus making it (sometimes) faster than C code compiled for compatability on many processors. The problem is that the unused deprecated methods take time to compile from bytecode to native code, so each time a new object is created, it takes ages before it can be used.
Also all the unused methods take up RAM, with java's bloat memory is used up very quickly
As to getting rid of primitive types, think of RAM again! a byte primitive takes up a byte of ram, but a byte object (like java.lang.Byte) takes up the byte of it's value plus all the methods.
I think java 3 should screw compatability and just cut out all the deprecated/rarely used methods, thus making it faster and more portable (rt.jar - the core java library - is 22meg, but a fair chunk of it is never used, think of all the 56k AOLers!)
http://www.microsoft.com/windows/Embedded/sak/eval uation/compare/advantage.asp
straightforward licensing...
Industry-leading scalability and performance...
Proven reliability...
a more secure environment...
an array of licensing complexities around the General Public License...
Does microsoft get karma for being funny?
Slashdot Mirror
Java is bad
MS's java clone is good
GNU's clone of MS's java clone isn't good (yet)
like, huh?
And why was my first title (so.......) filtered out as "too much like ascii art"?
The GPL infects everything it comes into direct contact with - put GPL code into a proprietry app, the app must go GPL, put add on proprietry code into a GPL app, the add on code must go GPL.
Methinks this only applies where the code is mixed though - if you never used their code and they never used yours, noone should be claiming rights over anyone else's stuff. I'm not sure about seperately developed plugins, but a plugin developed without any use of the main app's source is quite rare
In a democracy: The people vote for who makes decisions, the voted person makes decisions. I a political democracy (what we have): The people vote for who makes the decisions, the voted person takes bribes.
> That's because a service pack is basically the entire winnt directory's binary files all zipped up. It's almost the whole OS.
What, *every* binary in the winnt directory has bugs?
The java 1.4 vm runs 1.0 1.1 1.2 and 1.3 code, the 1.2 vm even runs 1.3 code! The bytecodes are not the problem, even a major change can be picked up by version number in the class file and a different vm called, it's the heavily bloated libraries that make java slow.
Using JIT, java is compiled to the optimal native code for any platform, thus making it (sometimes) faster than C code compiled for compatability on many processors. The problem is that the unused deprecated methods take time to compile from bytecode to native code, so each time a new object is created, it takes ages before it can be used.
Also all the unused methods take up RAM, with java's bloat memory is used up very quickly
As to getting rid of primitive types, think of RAM again! a byte primitive takes up a byte of ram, but a byte object (like java.lang.Byte) takes up the byte of it's value plus all the methods.
I think java 3 should screw compatability and just cut out all the deprecated/rarely used methods, thus making it faster and more portable (rt.jar - the core java library - is 22meg, but a fair chunk of it is never used, think of all the 56k AOLers!)
Yeah, blender's a right b*tch until you get used to it...
http://www.microsoft.com/windows/Embedded/sak/eval uation/compare/advantage.asp
straightforward licensing...
Industry-leading scalability and performance...
Proven reliability...
a more secure environment...
an array of licensing complexities around the General Public License...
Does microsoft get karma for being funny?