Slashdot Mirror
Java 2 for Linux Released & Blackdown Gets Creds
burner writes, "After quite a wait, JDK1.2.2 is released for Linux. You can grab the final release from Sun's site. Sun has also put up bios for the Blackdown guys. Sun's been acting pretty flippy lately, but this is great news. I've been using Blackdown's latest release candidates lately, and they're excellent, but now there's a final release. Nice work guys! "
I'm very pleased to see this and to see Blackdown getting credit. I have been hoping to use Java on Linux for a distributed network-of-computers project and this release makes the whole thing look more "polished" then using an RC.
Lest you people forget, there was a horrific accident some months ago when developers tried to code Q uake in Java. Please do not make the same mistakes.
Hates people who have stupid little sigs
Upgrade away, this should be a very stable release seeing as Blackdown doesn't seem to relaese flaky code. The betas were very stable and I have been happily developing with them for quite a while. :)
Now onto java 1.3, 3 or whatever it will be called
It's so disappointing to still see Java so fragmented across platforms. The 'Linux' release is only officially supported on one processor and increasing the officially supported OS's by 50% has been like pulling teeth. It's not the end-all-be-all of languages, but two years ago I had hopes that by now it would be faster and more pervasive than it has become--especially outside the browser cage. Such a shame... mh
Point taken, but misplaced.
/. readers seem to care about. If you wanna bitch, try posting at http://dev.null.com.
Java development is growing daily. The speed with which Java applications and servlets can be developed is unprecedented. The speed issues with Java are decreasing with each release, and 1.2.2 is pretty quick. The 1.3 early-release 1.3 JRE is quite a bit faster, and Blackdown is already working on the port.
This is very good news for Linux, which, as you may have noticed, a few
Let's see how many we get on this story:
Offtopic: If you don't have an X-server, JavaLobby posted a story about a very nice GPL'ed Xserver/Esound/Truetype server written in Java at called WeirdX Even runs as an applet. Very nice if all you have is a Windows/Mac box, or are at a public terminal/cybercafe and need to remote-X from your Linux box. :) Mostly impressive because a single guy wrote an X server from scratch in a short period of time.
:)
The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
Uh, can I instruct Netscape to use this JRE so it doesn't crash and burn? If so, how?
thanks. (if the stupidity of my question costs you a layer of brain-cells, my apologies and please direct all bills and requests for compensation to Steve Case, Chairman and Chief Executioner, America Online.)
There was a JavaLive chat yesterday about the Java on Linux stuff. They haven't put up the transcripts yet though.
For Java 1.3 from Sun, the Windows version will come out first, then Solaris then Linux. However, they do want to syncronise all releases together and should do this at or before Java 1.4 - might happen first for a maintenance release.
The blackdown JDK (1.2.2 RC4) supports native threads, while the Sun/Inprise release does not. The Sun/JDK release for liunx is not recommended for use on SMP systems....
That's not to insinuate that there's anything bad about Sun's version of Java. Other than it has a history of being the slowest. (Jikes leaves Sun's v1.1 compilers trailing in the dust.)
Also, now that Blackdown have it ported to Linux, will it be ported to different Linux processors? Or just ix86?
I can't see why it should be anything beyond a simple recompile, to get binaries for all the Linux platforms, and compilation speed isn't an issue, as you're not looking to debug the logic. Emulators, such as the ARM emulator, and cross-compilers, should be fine in producing Java 2 for Linux for every platform it runs on.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
I have been using IBM's Java 1.1.8 for basically powering my backend web applications on linux and frankly it has been working so well I have not seen a need to move to Java 2.
I don't use any of the Java EE beans or really anything major complicated, but my team has built some fairly complicated web sites that use multi-tier architecture with a great deal of success.
From the benchmarks I have seen I wouldn't argue that 1.2 is not really any faster than IBM's JDK? Actually, the benchmarks I have seen argue strongly the opposite.
From what I understand IBM will have Java 1.3 ported to Linux Q2 this year. Is Java 2 really worth it on the backend on linux?
Does anyone know what HotSpot is and what advantage that is going to bring us on using Java where it belongs, on the Server.
I admire the Blackdown crew, and the work they've done to get the JVM working under Linux. Unfortunately however, its not something I can use to write a professional application if I expect it to work properly.
I've done a lot of Java development under Linux this year, and I've noticed several things that prevent me from doing serious work with Java (under Linux). For example, rmiregistry crashes without fail for any type of heavily loaded RMI project. Another example is that Thread objects break just as easily, or refuse to start altogether when you spawn multiple Threads (even if there is plenty of memory available). Luckily I have access to a cluster of Ultra5's to test my applications on, which execute almost flawlessly (I've noticed a few quirks with Threads under Solaris as well, but not nearly as bad as under Linux).
I see the state of the JVM under Linux as being close to a toy. I know all the Blackdown people will probably find this insulting, but unfortunately, I can't do hard-core Java the way I can under Solaris. I do not blame Blackdown in any way for this however. I feel that this is solely Sun's fault.
Thats my $0.02 on the issue. I love Blackdown, I love Java. Bugs suck.
If they would've known the amount of time I had to struggle with getting GCC loaded and config'd for the HP, just so I could then compile Apache, just so after that I could compile JServ, just so I could *then* use an "Officially Sanctioned" JDK....
As I said, long overdue...
~Exaggeration is a billion times worse than understatement.
My life with the Sun JDK for Linux: 1. Got excited! Downloaded. 2. Installed 3. Ran my app. 4. waited. 5. killed process; tried again. 6. waited, waited, waited, waited. 7. killed process. 8. Uninstalled. 9. Downloaded and reinstalled RC4 *sigh*
Has anyone gotten Jini and Javaspaces to run? I'm taking a class that has an assignment to write a "distributed" program using javaspaces, and I've been trying to get the examples to run using a release candidate... needless to say, it bombs out, and I don't want to attempt this project in Win98... Thanks!
What might be the best way to put this JDK 1.2 into a Debian Box? Un-tar directly it into /usr/local as they say ? Or should we wait just a little while until .debs are available in unstable? Any guesses as to whether it might be soon?
My experience has been that Blackdown's port was faster and more stable than Sun's. Now that Sun's port has been officially blessed, I imagine it will have the stability edge for a little while, but I will continue to use the Blackdown port for its superior performance.
Okay, I'm happy for a (hopefully) stable java for linux.... but one question remains.... will companies get off their buts and starting making/updating their java apps as a way to adress (the media hyped) linux market? I mean will ICQ for Java finally have 1/2 the features of its win/mac counterparts? With all the APIs out by sun/java, there is no reason companies cannot update/create their apps for java. nil*
...the real problem isn't the warm-and-fuzzies, (although there's no underestimating the importance of people's feelings). The real problem is that Java is not open-source, and the stewardship of Java standards/apis is not open. The earlier slight to the Blackdown team was just a symptom, the real disease is Sun's unwillingness to let go of their baby and let it grow up into an adult. The result is that Java is still running largely with training wheels. Who wants to see how well the sandbox works when there are precious few applications worth running? Who wants to run an app that is theoretically pleasing but is, in practice, slow and kinda ugly? And not 100% stable? We can fix all that, but not under the current conditions. If things continue as they are, yes, progress will happen, but it will be sloooooooooow... maybe *too* slow.
I don't want to sound ungrateful, but... when are you going to drop the other shoe, Scott???
Life's a bitch but somebody's gotta do it.
I've been using 1.2rc3 for some time on an intranet site using a bunch of servlets/JSPs. Works like a charm. 1.2 JVMs are SOO much easier to use and configure than 1.1.x JVMs. They're much more intelligent about using .jar's, etc. The performance is also quite good, especially with Resin (www.caucho.com). No, I don't work for them, but I'm incredibly impressed by their servlet engine. It also has a cool feature that compiles JavaScript (in JSPs) to real Java bytecode. Plus a lot of great utility classes (like automatic database connection pooling, and XML support). I highly recommend checking it out. We're running an app on a $400 Linux machine and the response is basically instantaneous, even with multiple database queries. --JRZ
The last Blackdown release had a wobbly JIT and native-threads that were just plain broken. To run Netbeans, I had to disable the JIT and switch to green-threads - in other words, to turn off anything that makes Java run faster than molasses. Is this fixed in this release? Is there infact any real reason to upgrade from Blackdown 1.2.2 RC4?
An important distinction between the two is that the "official Sun JDK" does NOT support native threads and in fact recommends NOT running it on SMP machines, while the Blackdown release does native threads and SMP just fine.
-=-=-=-=-
-=-=-=-=-
My mom's going to kick you in the face!
maybe the moderators should check the link before..
I wrote a Java program for my son to use. Supposedly, it puts pictures of animal pictures on the screen, plays a sound clip, and a person is supposed to click on the picture of the right animal. Programming it was a dream. Easy! Not much code.
The problem: It doesn't run the same on any 2 platforms that I've tried. It doesn't run the same twice on any single platform. You never know which thread will run first. Sometimes the sound comes before the pictures appear (which is not the order it's programmed). Often, it doesn't load the images when I tell it to, and sometimes it doesn't load one of the images at all. The only way I could keep it from playing 2 sound clips at the same time was to specify a sleep the duration of the 1st sound clip. This happens with 4 different JVMs and operating systems (no Sun platforms) that I've tried. And, of course, it often crashes.
I have given up on Java. The point was to make a cross-platform program that non-Linux users could use, but if it only runs well on Sun products, forget it.
The image used for the Java stories has something that looks like a teabag or marshmallow floating in it. Not something that I've ever seen in a cup of coffee in any case. Any guesses as to what it might be?
to see if my IP is still banned.
Java is an appopriate choice for many kinds of games, but not all. First-Person shooters would not be a good class of game to do in Java; they are so resource-intensive and speed-critical that the performance hit of running on a JVM would probably be unacceptable. However, many other types of games would be great on Java - multi-player turn-based strategy games (Like Civilization II)would benefit from Java's strengths. I think that pretty much any game that isn't dependant having a high framerate to be enjoyable could be done in Java with no noticeable degradation to playability.
"The axiom 'An honest man has nothing to fear from the police'
Why is it that the proponents of "one nation under God" are so eager to get rid of "liberty and justice for all"?
I was once very excited about java. Did a fair amount of development under Java 1.0, Java 1.1, and Java 1.2, before we as a company decided to dump the product because of Sun's mismanagement of the standard and their lackluster support of the Blackdown group and Linux in general. This may have changed for the moment, but for us (and I suspect many others) it came far too late to be of much use (c.f. "sun sucks").
Performance may now be acceptable, but at the time we dumped the product even a small, simple data entry application was too demanding of the JVM at the time (even on Sparc 10's running Solaris, much less Linux). The choice Sun gave us was stark: run the Java VM under Windows or Solaris on a high end sparc, or suffer. We chose Linux, adopted a more open development environment, and now having dumped the product we will not, in the future, ever consider going back (c.f "sun sucks" and "slow"). Using GNU configure and its associated utilities, we are able to get all the cross-platform support we require, even if it involves a quick rebuild of the sources (typing "./configure" and "make install" isn't terribly difficult) with the performance our users demand and languages we can hire developers for (c.f. "use Perl" and "Java sucks").
I enjoyed using Java (despite the, even now, still horrificly screwed up date and time classes) as a language, but the drawbacks were too severe and too critical for too long of a time, and Sun's current and future motives with respect to the openness of the standard and support for Linux, FreeBSD, and whatever other platform we may, in the future, chose to deploy, has eroded our confidence in the product too much for us to seriously consider any future use of Java. Put simply, the stumbling blocks Sun until recently put in the way of development on anything other than their "blessed" platforms far outweighed any advantage the language itself offered (and those were not inconsiderable for those of us coming from C++, with Java's simpler memory management and garbage collection and other features).
Alas, the promise of "write once, run everywhere" quickly became (and IMHO remains) "write once, run where Sun would like you to." At present Sun has chosen to become mildly friendly towards Linux. This is great! However, I would not expect this to remain a long term strategy on their part, unless there are some serious changes in the mentaility of Sun's upper management. (c.f. "blah blah blah").
The Future of Human Evolution: Autonomy
JMC
Does this mean that us poor linux users can finally use the java plugin for mozilla ? (oh please please please ...)
All that we see or seem is but a dream within a dream.
You may want to brush up on multi-threaded programming- what you describe is exactly the way it is supposed to work (i.e. the order of thread execution is not guaranteed).
It sounds like you've seriously overdeveloped your app- if you're doing things sequentially, why put the actions in seperate threads? If you actually need threads for something, can the UI functions you describe be in one thread? Perhaps you should sychronize things using events.
YMMV, but I daily do development between 98, NT, Linux, and Solaris (on an UltraSparc) with Java and my code works the same on all platforms. Of course, I'm only doing Server Side applications and am not using AWT or Swing.
I'm not saying Java is all the hype made it out to be. In fact, all of the hype probably did more damage to Java over the long term than helped in the short term, but overall as a language it's not too shabby. As always, you should use the right tool for the job- maybe it's Java, maybe it's C, maybe it's Perl, maybe it's VB or Delphi. Depends on what needs to be done.
For the record, I've never been able to get a client side application using AWT or Swing to work the same between implementations.
DOOM in Java.
I just ran some of my old programs, even the one's with 1000+ threads work fine now, no crashing...sweet
This is great news. I had been holding the WebMacro servlet framework to 1.1.8 because there wasn't good support for Java2 on free OS's.
Now I can move it forward to Java2!
Tomcat isn't ready for primetime yet. It's lacking many features that JServ already has (and has had for a while now). Just an example, but it still doesn't support servlet reloading. JServ does.
I'm running both side by side, and while I would like to use some of what Tomcat has (ex. support for Servlet 2.2), right now I can only deploy to JServ. Maybe when 3.1 is out I can switch.
In real simple terms, HotSpot is a run-time optimizer for bytecode. It sees what pieces of code are getting used over and over (hot spots) and optimizes them - in a way that I believe is similar to storing data in registers instead of memory; whatever that means in JVM parlance.
-- What you do today will cost you a day of your life.
Port it to Java!!
<^>_<(ô ô)>_<^>
Let me correct myself. The JLS obviously does say a lot about threading semantics, just not enough to specify whether threads are even pre-emptive under Java, let alone map to native threads or across processors on an SMP box.
If you are extraordinarily careful and use synchronization primitives with care, you can write code that will function (however slowly/poorly) even in a very limited threading environment.
- jon
Ganymede, a GPL'ed metadirectory for UNIX
Most of us live in a free, market driven society. If enough developers and/or users demand better JVMs for more platforms etc. etc. then we should ask SUN to make them, or make them ourselves. blackdown.org is a modern hero of the linux community.
Java is a higher level language, with a modern and (mostly) solid API that forces correct use of OO principals (not a partial hack like C++).
I feel we need this, be it java or something else.
Anyone interested in a java knock-off?
Maybe "cocoa"???
Aren't native threads allowed to preempt? I think there are garunteed atomic operations too like (a = b);
What are the difference between the latest Sun JVM and latest Blackdown JVM ? Why is the Blackdown team working on java ports since Sun is releasing an official Linux port ?
a big grit!
I am currently employed in the telecommunications industry working on a SNMP administration tool written in Java. We started with JDK1.2.1, moved to JDK1.2.2, and are now developing with JDK1.3. With JDK1.3 our application blazes onto the screen in under a second, whereas with the earlier versions it took substantially longer. Good work Sun! Blackdown, I can't wait for the port.
Check out Frag Island - a Java FPS, that if only had gone all the way...
Reason is the Path to God - Anon
Post feature requests for the next JDK as replys to this message.
MODERATORS, please rate the suggestions!
Please, only one request per posting or you will mess up the rating.
Lets work together and make better software!
Preemption is allowed, yes, and there are guaranteed atomic operations (reference and integer assignment, at the very least). That's why I backpedalled and said that the JLS did indeed have guarantees on thread semantics.
It just doesn't have any guarantee as to when a particular thread will be run, nor whether a thread will ever be switched unless the active thread comes to the end of its execution or to a wait() call. In practice, every JVM that I care about will do those things, and I don't bother seeking out a Palm Pilot or Win 3.1 JVM to test my code on, but in theory it's something to be aware of.
- jon
Ganymede, a GPL'ed metadirectory for UNIX
Do not you do memory management when coding in C++? Only by hand and error-prone. Your code spends 80% of its time withing like 10% of the program. If you do not create and dispose of too many objects in there - GC overhead is negligible and well worth it. REal bottleneck in Java for me was its floating point performance. I can not use GCC now, for lack of features, but I would expect it will alleviate this..
<^>_<(ô ô)>_<^>
code like:
public class Test {
private static Frame frame;
public static void main(String[] args) {
frame = new Frame("Test");
frame.show();
}
}
compiles fine, but segfaults every time I run it. Something isn't right here...
a=b is guaranteed atomic unless a and b are longs.
You want the moderators to use their brains???
Java is just plain Object (or Objective) programming.
Programming teachers hate it when you don't know the difference.
I didn't know this before I read these news, but now I do: I needed a good JVM for Linux in order to competely switch my focus from C to Java. I will certainly continue working in C, but less and less. My company does a lot of Java developement (on HP UX and NT), but I wasn't very motivated to join R&D with Java. Now I am!
Thanks Blackdown and Sun!
Sigged!
Hey, SUN PHBs, hire the blackdown team so they can work full time on the JDK port - OK? Better do it before IBM hires them ;-)
...to see if any Greek soldiers are lurking in there.
Really, the README says that only green threads are supported and running under SMP kernels is discouraged. Given the resources Sun has to do things right, this can mean only one thing: it's their way of saying "Linux is OK for single-user toy usage but for high-end SMP stuff just get Solaris, OK?". This is more a PR release "We do Linux, we want our stock to go up" than the REAL thing.
I hope IBM will bring out a SMP-supporting JDK2 SOON! Their 1.1.8 is wonderful and fast. Are you listening, IBM?
Tuomas
Hey guys,
Quick question for all of you.
Does anybody have any recommendations for books or any links to tutorials or any other information on servlets.
Although I have found some info on Sun's site it isn't nearly as good as I would hope it would be.
I have been using IBMs JDK 1.1.8 for 6 months and despite one huge bug (which is fixed), it has been a stable and fast JVM.
Anyone know how BD/Sun JDK 1.2.2 compares in terms of raw speed?
--
"You're gonna need a bigger boat." - Chief Brody
Sorry to post as an AC (away from usual box, password stored as cookie etc etc), but who the hell thought this was worth a +5 (Funny)? It's not very funny, it's not clever and it should be a -1 (Troll).
/. management are trying to reduce the value of the site by encouraging troll weevils, posting deadly dull old stories and hiring new story posters without any mention of their provenance.
If I were a conspiracy theorist I'd say that the
Rob, You're best readers/contributors are going to get really pissed off and leave. If you're feeling too rich/bored to run the site properly, hand it over to someone who *will* run it properly.
Back on topic, I spent half of today writing a neat little Java utility. Console only (with JDBC to three Oracle boxes), and I can't see how I could have built it that fast with any other system. I considered perl, python, C, C++, but for me, today, Java worked.
[Yay! I've managed to get X to my usual box - the cookie's still there, so I'm not an AC after all. The magic of modern telecoms...]
If sun really wanted to get Java multi-platform they would get the following straight:
1. Built in support for every major Linux distribution.
2. Automatic or at least automated update of the JVM on your system to the latest stable version. By components hopefully as the whole thing is a little big.
3. Finish the damn Java plug-in for browsers. No one wants to include Java in their browser anymore, so just finish that Java runtime as a plug-in deal and get it out there.
Then we could have some serious open source Java projects for Linux and I could finally start contributing...
Hotnutz.com - Funny
I think it's a "good thing"(tm) that they ported it. But I don't think we should accept Java as it is. We should develop a better or even worser language as long as it's free, open and doesn't contain any evil licenses. Sun isn't any better than Ms and they should _not_ own something that might become language no.1 in the world. If somebody owned C/C++ ? How would the world look like today?
::Optimization is the root of all evil
Before you go too far into JAVA, JITs etc, please read this warning about using executable content languages via html
It is about time Sun got decent Java support to Linux. I know that they'd rather spend effort on working on their own OS, but if they truly want a language that is portable to all systems, they need to make sure it actually works on all systems.
Now for the negative side. My experience with Java screams that the language is in need of much work. It runs slowly. It requires you to look up the APIs constantly anytime you want to do something useful, and it just doesn't get the job done as well as C/C++. It has a place, but I'm not sure that it is really the greatest tool for Linux programmers when compared to C/C++/Perl/Whatever. Still, the idea of "crossplatform" is nice.
"You spoony bard!" -Tellah
Moderation on Slashdot is such a bloody mess.
Congratulations! You win a lolipop! Only certain people get to moderate - people that the existing Slapdash.org establishment want.
Wingnut
What does this have to do with the article?
Java can be used for a lot more than applets.
>> a dual p3 with MySQL outperforms a 30 cpu sun E6500
>> with oracle by over 500 times, with more features
>> and better reliability
This statement is completely and wholly untrue. It's like saying a skateboard can go faster than a train, there's no matter of opinion. The poster wasn't saying MySQL is a better choice for some situations, he was saying that it is several thousand times faster than Oracle. The rest of the comments were equally crazy. Perhaps the original poster was being sarcastic, or perhaps he was just trolling. But he sure as heck wasn't being sincere.
perl -e 'fork||print for split//,"hahahaha"'
I hope to goodness they aren't supposed to be marshmallows. Marshmallows go in cocoa...
The html delivery model for executable content which includes JAVA/JavaScript/etc has serious security flaws that need to be addressed, and this issue was discussed at length in the CERT's advisory. Java applets are one of the major application areas for Java. Today's Slashdot article is about JAVA, a member of the group of executable content languages impacted by the security problems.
According to the README, SUN says otherwise...
Of course, it is possible that they have native threads, but it hasn't been tested well enough to use in a production environment.
Check out the Volano Report. Sun/Solaris and Blackdown/Linux rock....
Is this release only for Intel x86 or do they support Linux on any other architecture?
Lord Pixel - The cat who walks through walls
Lord Pixel - The cat who walks through walls
A little bigger on the inside than out
C'mon!
you dumped Java because of Sun ? Why ? So far sun has managed to produce a fairly decent language as of java 2 with very few bugs (at least not as many as the horrible java 1.0.x). with kaffe other GPLed java implementations and class libraries Sun could be dumped almost completely. yes, its slow (as yet..) but its probably the only language out there which *can* be compiled once and run anywhere you can get a compatible VM. i can understand if youre coding in C and using the GNU tools - thats a FAR superior environment ..but for stuff such as server side programming - Java far outclasses anything else if you have the hardware to pull it off.
It's in a early stage right now (version 0.0), but should more people hack on it, we can say bye-bye to Sun.
A good feature for Mozilla: userdefined acl for sites where Java is enabled; default is no Java at all.
well i had no idea anyone would find my ramblings of any interest... but the issue that i was hinting at is what anyone who has been testing Mozilla on Linux has known for quite a while: support for Java applets in Mozilla is implemented by a Java runtime engine plugin, which is included in the Java 2 release, which until now has been unavailable on Linux.
All that we see or seem is but a dream within a dream.
This is indeed one of the great features of Mozilla, but let's hope it isn't reversed when Mozilla is finally released and incorporated into set-top boxes, mail-order PCs etc. The released Mozilla will need to be an order of magnitude easier-to-use and more bug free than the competition to stand a chance of displacing IE5 from its dominant position. Even if Mozilla takes over from IE5, until IPv6/HTML 5/secure DNS are universally deployed, the availability of Java and JavaScript in common browsers is going to continue being of more risk than benefit to most users. There will probably always, however, be the odd user who actually likes and expects client-side excitement like flashy mouseOver.goWild animations, open.Window.Uncloseable popups etc.
I posted this damn message at 5:00 AM EST this morning. What's the deal, no one awake that early?
www.linuxticker.com posted the news 14 hours before that and Sun did the whole thing on Monday. Happy Valentines Day!!!
I didn't realize that you have to be somebody to post something...
I guess opinions counter to yours are forbidden. The original poster about Java making crappy games was correct.
One of the most cynical deals recently involves the merger of two software companies trying to cash in on the Linux operating system craze: Andover.net Inc. of Acton, Mass., and VA Linux Systems Inc. of Sunnyvale, Calif.--which went public within 24 hours of each other back in early December. Less than eight weeks later, on Feb. 3, the two companies announced a stock-for-stock merger in which the California company has agreed to acquire the Massachusetts crowd for about 6 million shares of VA Linux and $60 million in cash. The cynicism in the transaction is not simply that the deal took place so shockingly soon after the two companies wrapped up their I.P.O.'s, but that the transaction included what amounted to a legalized bribe on the part of the VA Linux bunch to get the Andover.net crowd to accept the offer. The deal means that the $60 million in cash from VA Linux will go directly to Andover.net's shareholders, at $3.81 per share, in effect handing over the same amount of money Andover.net raised in the I.P.O. only weeks earlier. Prior to the I.P.O., the company's insiders had only paid a grand total of $15.7 million in cash into the company. Now they are being handed back $60 million as compensation. What a deal. As for investors in VA Linux, they are getting hosed. The company's stock was priced in the I.P.O. at $30 per share, but opened for trading at $299 and instantly shot to $320, then collapsed like many of the others and eight weeks later is now selling for $110. Faced with 39.7 million total shares outstanding already--of which only 4.4 million are held by the general public--investors in the stock can now look forward to the imminent registration of 4 million more shares by the company, which will doubtless come pouring into the market soon thereafter, thanks to the Andover.net deal. In other words, the only really valuable asset Andover.net ever had--its cash from the I.P.O.--was creamed off by the company's insiders almost the very instant they got their hands on it, leaving VA Linux's shareholders to face a 100 percent increase in the float of their own stock for the privilege of winding up with the worthless trash that the Andover.net bunch dumped at the very first opportunity.
... or doubles.
too many compagnies consider linux a x86 only platform and it's not
Blackdown used to run on other processors what abouts the official release ?
none Yet.
Look, its Java, not JAVA.
Learn to spell dammit
There has been alot of improvement.
In fact blackdowns's jdk-1.2.2 JVM is one of very few JVMs (2) that didn't error out on Volano's network tests. It also is now 4 times faster than jdk-1.1.7 in the same tests (IBM's jdk-1.1.8 on NT is twice as fast as the new blackdown on linux but it used to 10 times faster).
The major problem with Java is the speed of the graphics routines. Swing still suffers from this, compared to natively compiled GUI's like eg. GTK+ stuff. Recently, however, I've become aware of 2 important facts, that will allow those of us who want to, code games in Java at good speed.
1 Magician, an OpenGL implementation for Java which yields Java code that seamlessly uses existing native OpenGL libraries to provide high-performance rendering over a variety of platforms - how's that for starters?
2 Crusoe, a processor which can emulate x86 instructions - and I'm pretty certain that it'll be able to handle bytecode as well as x86 instructions sometime in the near future. IBM has backed the chip for the past years as has their interest in Java increased a lot in the same time span.
Hooray.
Unable to read configuration file '/bigassraid/htdig//conf/14229.conf'
Geocrawler error message.
It was interesting how a month ago, you could find JDK1.2 for Linux, but not on the Sun site. You had to go to Inprise's site and link over to Sun's download page. My 30 KSLOC (Thousand Source Lines of Code) app ported over to the Linux VM nicely (modified 1 file a lot changing "\" to File.separator. backslashes.) JFC, servlets, RMI, beans, etc... no anomalies. No problems with Sun's VM. Got to go get Blackdown's... Check out the GPLed BeanBrowser at http://www.inforaction.com. Server runs best on Linux (because it doesn't crash).
:-)
The only Good System is a Sound System
Not hosting Java applets on a server will not prevent this problem, because the whole point is that hackers can introduce arbitrary APPLETs and SCRIPTs onto web pages. This is not a flaw in Java, it is a flaw in web servers. Turning off executable code on the client is a bad quick fix - the best solution is fixing the servers.
I thought it had been established that Java was secure enough for applets. Please get a clue.
Female Prison Rape in NY
Um, unsigned Java applets can't cause any damage (apart from spoofing password dialogs etc. but that can even be done in non-dynamic HTML). Or do you know something that Sun doesn't?
Female Prison Rape in NY
My program contains no threading language, bozos. The threading is done by the JVMs. A different thread is run for the sounds, the graphics, etc. I have no control over how the JVMs on different platforms run my program. And, it seems entirely nondeterministic.
Do the world a huge favor -- stay away from Slashdot until you've become qualified, finished your undergraduate studies at Lancaster University, improved your interpersonal skills, and done a remedial course in English comprehension and effective communication.
The original comment was "Before you go too far into JAVA, JITs etc, please read this warning about using executable content languages via html". The clue, especially for you Robin Dizzard Green, is in "via html" which explicitly identifies the html delivery model as part of a security problem relating to executable languages. Did the comment say there was a flaw in Java? No. Did it say anything about the consequences of hosting or not hosting JAVA applets on a server? No. What did it say? It said here is a warning about using executables languages via html. That's all, bud.
I don't drink quads, because I like the added sugar and milk-fat from Mochas and Raspberry Lattes. :)
Running a numerically intensive program, which has no disk access and static memory requirements, execution time varied considerably:
Sun's JDK 1.2.2 under Windows NT ... 40 sec ... 7.5 min ... 1.5 min
Sun's JDK 1.2.2 under Linux
Kaffe 1.0b4 under Linux
Identical hardware, all default compiler/JVM options, nothing else running, etc.
I'd generally rather use Sun's product but not with that kind of lack-luster performance. (And I'm trying to avoid rebooting to NT--hooked on Linux!)