What is really cool about assemblies is that you can dynamically generate them using classes exposed in the core framework.
That's nice, but not exactly a great advantage over Java per se. After all, JDK version 1.2 and up also provide ways of dynamically handling JARs (including creation).
(i'm not aware of implementation for my other computer running beos.)
I know of two tentative ones: the BeKaffe project (attempting to port Kaffe to to BeOS) at http://bekaffe.sourceforge.net/ and the Guavac project at http://www.bebits.com/app/1195. The first is having development problems (that is, capacity problems with respect to people) and the second is at the 1.1-level, unfortunately. But you can check them out, I suppose.
Of course, I wouldn't expect too much in future any more. BeOS seems to have gone the way of the dodo, so...
Indeed. Although why this should be true is beyond me -- the executable jar system is there for a reason. If only people would use it more regularly....
I always call it "zoooozuh". It's a German company and the Germans pronounce an "s" like a "z" and a "u" like "ooooo" (like a ghost rattling its chains). They also don't do silent vowels on the end, so I make it zooozuh.
"Trusted Debian" is clearly targetted to compete with "Trusted Solaris" and "Trusted(?name right?) BSD".
Actually, I severely doubt that -- seems to me they just liked the sound of "trusted" and adopted it, rather than that the developers are looking to take anybody on specifically.
Yes, well, I think we can all rejoice in the knowledge that the DoD doesn't dictate proper uses of words outside their own backyard. There is absolutely no reason why any distribution of any operating system whatsoever (especially ones not stemming from the United States, like Trusted Debian) should have to conform in its naming to the definitions set by the Pentagon.
Slashdot Mirror
The argument that closer EU integration will destroy national cultures is completely bogus and introspective.
It does seem a bit unlikely, yes. Especially given the importance of the REgions within the EU.
What is really cool about assemblies is that you can dynamically generate them using classes exposed in the core framework. That's nice, but not exactly a great advantage over Java per se. After all, JDK version 1.2 and up also provide ways of dynamically handling JARs (including creation).
(i'm not aware of implementation for my other computer running beos.) I know of two tentative ones: the BeKaffe project (attempting to port Kaffe to to BeOS) at http://bekaffe.sourceforge.net/ and the Guavac project at http://www.bebits.com/app/1195. The first is having development problems (that is, capacity problems with respect to people) and the second is at the 1.1-level, unfortunately. But you can check them out, I suppose. Of course, I wouldn't expect too much in future any more. BeOS seems to have gone the way of the dodo, so...
>>> especially in the case of Java
Indeed. Although why this should be true is beyond me -- the executable jar system is there for a reason. If only people would use it more regularly....
I always call it "zoooozuh". It's a German company and the Germans pronounce an "s" like a "z" and a "u" like "ooooo" (like a ghost rattling its chains). They also don't do silent vowels on the end, so I make it zooozuh.
"Trusted Debian" is clearly targetted to compete with "Trusted Solaris" and "Trusted(?name right?) BSD".
Actually, I severely doubt that -- seems to me they just liked the sound of "trusted" and adopted it, rather than that the developers are looking to take anybody on specifically.
Yes, well, I think we can all rejoice in the knowledge that the DoD doesn't dictate proper uses of words outside their own backyard. There is absolutely no reason why any distribution of any operating system whatsoever (especially ones not stemming from the United States, like Trusted Debian) should have to conform in its naming to the definitions set by the Pentagon.