You don't need insider information to know that memory management has never been MS's strongpoint on any product/application. Their own (I hesitate to use the plural) operating systems aren't good at it... so why should we expect it at all?
As someone who had to use MS's J++, I'll say that the number of crashes a windows system went through in a month after running the VM, garbage collection couldn't have been completely implemented. And as I said before, its not like the OS will go in and adequately clean up after a terminated application.
>>You could not write html for explorer that would work with netscape and reverse...
>What the hell crack have you been smoking? >Some of the advanced features arn't cross compatable, but you could always code somthing that would work in both
Yeah but how does that ruin his point?
Microsoft's "modus operandi" (sp) has pretty much always been to take something that someone else has developed, make it their own and make it either completely incompatible with the original or at the very least difficult to avoid the incompatibilities. In the case of HTML, it seems a violation merged from netscape too, but in the case of Java, Microsoft was the great Satan. J++ was an obvious attempt to make MS Java different from Java in general.
It isn't a question of whether Microsoft gives you more advanced features as an option -- they are free to do so as long as it isn't harder to avoid the incompatible advances than it is to dig to China. Don't we all realize that MS's attempts at expanding Java constantly blurred the lines at what was Java and what was not?
The bottom line is this... one of the main features of Java is that it is a compile-once cross-platform tool. Though they may not have completely achieved this goal... it certainly doesn't make sense for some imperialist company to go in and put the gears in reverse.
I like developing in Java... I find it a bit refreshing from the C++ brushlands I have to chop through occasionally. But regardless of how much I like or dislike Java, it is more than clear that MS was at least somewhat threatened by a tool that makes it possible to bypass their historic "Iron Curtain" platform. And their actions make it more than clear that their solution of blurring the lines was a standard Microsoft tactic.
I don't know about the rest of you... but I am glad that for once they didn't get away with it.
Slashdot Mirror
You don't need insider information to know that memory management has never been MS's strongpoint on any product/application. Their own (I hesitate to use the plural) operating systems aren't good at it... so why should we expect it at all?
As someone who had to use MS's J++, I'll say that the number of crashes a windows system went through in a month after running the VM, garbage collection couldn't have been completely implemented. And as I said before, its not like the OS will go in and adequately clean up after a terminated application.
>What the hell crack have you been smoking?
>Some of the advanced features arn't cross compatable, but you could always code somthing that would work in both
Yeah but how does that ruin his point?
Microsoft's "modus operandi" (sp) has pretty much always been to take something that someone else has developed, make it their own and make it either completely incompatible with the original or at the very least difficult to avoid the incompatibilities. In the case of HTML, it seems a violation merged from netscape too, but in the case of Java, Microsoft was the great Satan. J++ was an obvious attempt to make MS Java different from Java in general.
It isn't a question of whether Microsoft gives you more advanced features as an option -- they are free to do so as long as it isn't harder to avoid the incompatible advances than it is to dig to China. Don't we all realize that MS's attempts at expanding Java constantly blurred the lines at what was Java and what was not?
The bottom line is this... one of the main features of Java is that it is a compile-once cross-platform tool. Though they may not have completely achieved this goal... it certainly doesn't make sense for some imperialist company to go in and put the gears in reverse.
I like developing in Java... I find it a bit refreshing from the C++ brushlands I have to chop through occasionally. But regardless of how much I like or dislike Java, it is more than clear that MS was at least somewhat threatened by a tool that makes it possible to bypass their historic "Iron Curtain" platform. And their actions make it more than clear that their solution of blurring the lines was a standard Microsoft tactic.
I don't know about the rest of you... but I am glad that for once they didn't get away with it.