For server-side apps, it makes no difference whether Microsoft bundles the JRE or not--anybody putting together a bunch of servers is going to install the latest JRE directly from Sun anyway.
On your planet, perhaps. My client's servers are covered in numerous JREs, each specific to various applications, because they can only be qualified on particular point releases.
Because it's better than what Sun has right now (OpenWindows).
Sun don't ship OpenWindows management tools, they ship CDE/Motif based ones.
And the whole point of the memo is that both the engineers being forced to reengineer them in Java and the customers talking to them think the new Java tools are a big, festering pile of shit that are a great deal worse than the Motif ones.
If you bothered reading the piece before clicking "Post a slaverng Java fanboi response", you';d notice the engineer is recommending Java is so bad at Sun it not be used BECAUSE THE JAVA ENGINEERING TEAM WILL NOT FIX IT. Because they regard features as more important than a stable API or bug-free runtime.
It would be plenty of evidence to bring suit, if one chose, which would ultimately give the plantiff access to Castle's documentaiton, electronic and written records, source code, etc. Of course, they could have a go at destorying the evidence ("Oops, the dog ate my backups"), but that tends to upset judges.
Standards compliance and psuedo-webbish features. Microsoft themselves culled a huge about of crap and non-standard extensions between 4.0 and 5.0, some more between 5.0 and 5.5, and 6.0 is becoming stricter again.
(Although it should be added there's stuff 5.5 that wasn't in 5.0; IIRC, the JavaScript XML parser is new in 5.5).
Sun zealots gloss over the fact that Digital did it first, faster, and had support for it on their operating systems. Oh, and didn't need OS hacks to work around terminally buggy hardware.
NT 4 is a good, stable target that encompasses the bulk of the Win32 API that is also in Win2k and WinXP. Once they've got that right, rolling forward to Win2K and up should be trivial - getting the basic microkernel and servers right will likely be the hard part.
That means *plain* ASCII. Plain ASCII means you could read it in edlin if you really had to.
This is a Good Thing.
No, it's a bad thing, because it renders Gutenberg near useless for anything other than English, and it cripples it for creating PDFs, TeX files for printing, and the like.
One can take SGML (which came into being around the time of the Project) and create plain text. One cannot take the plain text and create SGML.
Paper books aren't readily available. My wife and I, between us, own a fairly large number of 19th century and earlier volumes that aren't in print any more. If you're interested in those volumes for some reason, an etext version is the only way to go.
And there's nothing to stop you printing Gutenberg texts out. If they weren't so impoverished (ASCII only), they'd even look real pretty (although I'm sure that people have Gutenberg to TeX programs, which would help).
Nope. History evolves constantly. Interpretations change, and primary source material can be uncovered. Archaeological digs, you name it, all feed into our understanding. Sutton Hoo, for example, revolutionised our understanding of aspects of pre-Norman Britain, and it was dug up within the period commonly covered by infinitely extending copyright.
Because ASCII is American. Much of the rest of the world uses different charactersets. Gutenberg is completely impoverised with regard to, say, French, Norse, or countless other languages.
That's only a problem in the US currently. Perhaps Gutenberg will need to have a Gutenberg-Berne (for countries with the Berne convention minimum of 50 years) and a Gutenberg-US (for the States).
Also, one item which emerged: the embedded database used by all the client-side.NET tools (Visual Studio, for example), is vulnerable, as well, and doesn't have a patch available when I looked a couple of days ago. So any number of what you think of as your client system have this worm, where they're harder to patch, but can infect your servers. Nasty.
I'm more concerned it'll do for Harry what AICN has. The more hits AICN gets, the more pounds Harry puts on. A gaming site could be the cause of his first obesity related coronary.
I think you've missed my point; the parent was asked what made Java a suitable language for large applications. A big library of code is a dumb answer, because every man and his dog has that.
If he'd discussed design features of Java *as a language* that make it harder to write unmaintainable code, it would have been a useful comment.
As for bad perl - well, yes, there's a lot of it out there. Unfortunately, there's now a lot of crapulent Java. I'm currently looking at some commercial products which have been written by the sorts of idiots who can't use an RDBMS properly, so reimplement WHERE, ORDER, and GROUP in their Java code.
Would those be the sysadmins working in a climate of record layoffs? With fewer people doing the same work? On a platform where service packs include payloads that can destory your file system (NT SP2) or randomly change your licensing agreements to allow the vendor to access your proprietary information (Win2K SP3, WinXP SP1)?
WOuld it also be the Security Pack which Microsoft have now announced actually has two different versions - one on CD which fixes all installations, and one from the 'net which will not actually solve this problem, on some installations, when applied (if the latest and greates from Bugtraq is to be believed)?
All it takes is for someone to have SQL Server running on a laptop. They dial in when they're outside the company LAN, get infected, come to work, and boom!
There are a *lot* of people out there running server tools on laptops - pre-sales, consultants, contractors, as well as your internal staff.
humans lived for thousands of years without destroying the earth.
Bullshit, pure and simple, as anyone even mildly aquianted with the mass extinctions and deforestation of Australia, or the desertification of the Middle East can tell you.
Slashdot Mirror
On your planet, perhaps. My client's servers are covered in numerous JREs, each specific to various applications, because they can only be qualified on particular point releases.
Sun don't ship OpenWindows management tools, they ship CDE/Motif based ones.
And the whole point of the memo is that both the engineers being forced to reengineer them in Java and the customers talking to them think the new Java tools are a big, festering pile of shit that are a great deal worse than the Motif ones.
Insightful? For what? Not even reading the memo?
If you bothered reading the piece before clicking "Post a slaverng Java fanboi response", you';d notice the engineer is recommending Java is so bad at Sun it not be used BECAUSE THE JAVA ENGINEERING TEAM WILL NOT FIX IT. Because they regard features as more important than a stable API or bug-free runtime.
Might as well start learning to love Windows, then. Sun's success in conflating "J2EE" and "Unix" means that Unix will likely go down with J2EE.
For definitions of multitasking that include System 7, Windows 3.1, and other festering piles.
I loved the UI of RiscOS 2 and 3, but the underpinnings were crap. Memory management, multitasking, file systems, you name it. Rubbish.
It would be plenty of evidence to bring suit, if one chose, which would ultimately give the plantiff access to Castle's documentaiton, electronic and written records, source code, etc. Of course, they could have a go at destorying the evidence ("Oops, the dog ate my backups"), but that tends to upset judges.
Standards compliance and psuedo-webbish features. Microsoft themselves culled a huge about of crap and non-standard extensions between 4.0 and 5.0, some more between 5.0 and 5.5, and 6.0 is becoming stricter again.
(Although it should be added there's stuff 5.5 that wasn't in 5.0; IIRC, the JavaScript XML parser is new in 5.5).
You could photo restoration on an Amiga, too. This doesn't make it a fine idea.
Sun zealots gloss over the fact that Digital did it first, faster, and had support for it on their operating systems. Oh, and didn't need OS hacks to work around terminally buggy hardware.
NT 4 is a good, stable target that encompasses the bulk of the Win32 API that is also in Win2k and WinXP. Once they've got that right, rolling forward to Win2K and up should be trivial - getting the basic microkernel and servers right will likely be the hard part.
Can you say "Honeypot"?
You missed their excellent HA clustering. And SMIT.
No, it's a bad thing, because it renders Gutenberg near useless for anything other than English, and it cripples it for creating PDFs, TeX files for printing, and the like.
One can take SGML (which came into being around the time of the Project) and create plain text. One cannot take the plain text and create SGML.
Paper books aren't readily available. My wife and I, between us, own a fairly large number of 19th century and earlier volumes that aren't in print any more. If you're interested in those volumes for some reason, an etext version is the only way to go.
And there's nothing to stop you printing Gutenberg texts out. If they weren't so impoverished (ASCII only), they'd even look real pretty (although I'm sure that people have Gutenberg to TeX programs, which would help).
Nope. History evolves constantly. Interpretations change, and primary source material can be uncovered. Archaeological digs, you name it, all feed into our understanding. Sutton Hoo, for example, revolutionised our understanding of aspects of pre-Norman Britain, and it was dug up within the period commonly covered by infinitely extending copyright.
Because ASCII is American. Much of the rest of the world uses different charactersets. Gutenberg is completely impoverised with regard to, say, French, Norse, or countless other languages.
It's a dumb thing to retain.
Amen.
It could at least shift to unicode, so we can write in languages other than English (and English-with-no-accents, at that!).
Useful, but all US law, of course.
That's only a problem in the US currently. Perhaps Gutenberg will need to have a Gutenberg-Berne (for countries with the Berne convention minimum of 50 years) and a Gutenberg-US (for the States).
No idea. But enough time and infected hosts.
.NET tools (Visual Studio, for example), is vulnerable, as well, and doesn't have a patch available when I looked a couple of days ago. So any number of what you think of as your client system have this worm, where they're harder to patch, but can infect your servers. Nasty.
Also, one item which emerged: the embedded database used by all the client-side
I'm more concerned it'll do for Harry what AICN has. The more hits AICN gets, the more pounds Harry puts on. A gaming site could be the cause of his first obesity related coronary.
I think you've missed my point; the parent was asked what made Java a suitable language for large applications. A big library of code is a dumb answer, because every man and his dog has that.
If he'd discussed design features of Java *as a language* that make it harder to write unmaintainable code, it would have been a useful comment.
As for bad perl - well, yes, there's a lot of it out there. Unfortunately, there's now a lot of crapulent Java. I'm currently looking at some commercial products which have been written by the sorts of idiots who can't use an RDBMS properly, so reimplement WHERE, ORDER, and GROUP in their Java code.
Would those be the sysadmins working in a climate of record layoffs? With fewer people doing the same work? On a platform where service packs include payloads that can destory your file system (NT SP2) or randomly change your licensing agreements to allow the vendor to access your proprietary information (Win2K SP3, WinXP SP1)?
WOuld it also be the Security Pack which Microsoft have now announced actually has two different versions - one on CD which fixes all installations, and one from the 'net which will not actually solve this problem, on some installations, when applied (if the latest and greates from Bugtraq is to be believed)?
All it takes is for someone to have SQL Server running on a laptop. They dial in when they're outside the company LAN, get infected, come to work, and boom!
There are a *lot* of people out there running server tools on laptops - pre-sales, consultants, contractors, as well as your internal staff.
Bullshit, pure and simple, as anyone even mildly aquianted with the mass extinctions and deforestation of Australia, or the desertification of the Middle East can tell you.