Will Sun Open Source Java?
capt turnpike writes "According to eWEEK.com, there's an internal debate going on at Sun whether to open-source Java. (Insert typical response: "It's about time!") Company spokespersons have no official comment, as might be expected, but perhaps we could hear confirmation or denial as early as May 16, at the JavaOne conference. One commentator said, "Sun should endorse PHP and go one step forward and make sure the 'P' languages run great on the JVM [Java virtual machine] by open-sourcing Java." Would this move Java up the desirability scale in your eyes? Could this be a way to help improve what's lacking in Java?"
"Open Source" covers a LOT of licenses.
What changes and how would depend upon which license was chosen.
Phalanger is going to support Mono in their next release, which already support IKVM.
I think this could be an excellent idea, if only to allow for third-party JVMs.
I, for one, have always seen Sun's JVM as bulky and slow on Windows PCs, and this is a large reason that I don't advocate its usage.
"Will Sun Open Source Java?"
No, haven't they already said that? Like hundreds of times? And does it really matter?
"Sun should endorse PHP and go one step forward and make sure the 'P' languages run great on the JVM [Java virtual machine] by open-sourcing Java."
"No", who would run PHP on Java anyway? Why? Why would open-sourcing it help?
"Would this move Java up the desirability scale in your eyes?"
No, Java is already desirable in my eyes.
"Could this be a way to help improve what's lacking in Java?"
No, what is lacking?
People who complain that Java is slow, should be open-sourced, and so on have never seemed to had a clue.
> Would this move Java up the desirability scale in your eyes?
It would certainly bring it across the threshold to something I might be willing to install on my machine. I'm not sure I'd actually be interested in using it for anything, but at least it would no longer be in the "completely unacceptable" column.
Of course, I'd probably wait till it was "apt-get"able. But I suspect that an actually-Free Java(tm) wouldn't have to wait long to find a Debian packager.
Certainly couldn't do worse.
No boom today. Boom tomorrow. There's always a boom tomorrow. - Cmdr. Susan Ivanova
I currently avoid Java like the plauge, my reasons are the same reasons that java isnt included in debian... http://www.debian.org/doc/manuals/debian-java-faq/ ch5.html#s-license-concerns
if they address those license concers i would be much happier...
"I reject your reality, and substitute my own" - Adam Savage
... and just do it.
.NET, so Java *will* be open source some day anyway. Sun needs to get at least J2SE out there before .NET runs on every electronic device available.
.NET is looking like the only alternative for managed coding on handheld platforms. (Cellphones are not yet good PDAs, ok?)
WINE did it for Win32 and Mono did it for
Now that Sharp's Zaurus has dropped Java,
SLM
main() {1;}
I still fail to see the benefits of "open sourcing" Java. How will it be improved? It's not as if the engineers at Sun are stupid and don't know how to engineer enterprise software. Don't you think Sun has heard that same complaint from some major league/big $$$$$ customers and done everything they could to improve said performance?
Even if they *do* open it up, Im sure the slashdot community will still hate them because they don't use a GPL variant license. Its a lose-lose situation for Sun, I don't get why they would even consider it. Is there a business case that will generate a 9-figure revenue jump from giving away the source for Java? I don't see it, but Im sure someone around here will happily clue me in.
all the things java was supposed to be great for, all the portability, consumer gadgets, smart coffee machines, etc. there's where Sun could really benefit most from open sourcing. There just isn't that much of a reason to use it on the net anymore, unless you work at a financial institution, the technology at large is just moving too slow. But when hobbyists can easily adopt java to connect the things around the house, that will be a big push forward for everyone. and open sourcing java only speeds up that barrier that keeps most java programmers working on desktops and servers...
Open sourcing Java? Are you kidding me? Chaos would reign. Every month new features would crop up and we have to keep learning and learning and learning. Look at Ruby on Rails, new features every couple of days. Nobody can keep up.
No no no. Let Sun handle Java.
It'll be a cold day in hell before Sun releases the source code to any software that people actually use.
Badass Resumes
Today, as far as I'm concerned, Java is:
1. gcj (the gcc that does Java-to-JVM and JVM-to-native)
2. GNU classpath
3. Kaffe?
I've never seen it do anything, either in a browser or in OpenOffice. Oh well.
(not that language which overloads "+" for string+number is sane; that ought to be a compile error)
"One commentator said, "Sun should endorse PHP and go one step forward and make sure the 'P' languages run great on the JVM [Java virtual machine] by open-sourcing Java."
Explain that to comment to me, please. It makes no sense.
It is very reasonable to run Java in Linux. It's harder/more painful/whatever in the BSDs but it works.
FreeBSD now includes Sun Java as part of the distro, so it should be easy. Any Linux/BSD/etc distro can do this, it just requires spending the money to get it certified.
#!/
"Also memory are cheap and who cares"
;)
I do... I knew a few other people who may also
For a good comparison of what c is capable of compared to java, compare the speed and memory footprint of azureus with utorrent. They have very similar functinality and interface, but utorrent uses about 1/5 the memory!
"Open Source" + "Sun Microsystems" almost certainly = "CDDL"
"Would this move Java up the desirability scale in your eyes?"
Java isn't the answer for everything. Either is C, C++, Perl, Python, Ruby, or PHP. Each language has it's strengths and weaknesses.
Nobody should be making decisions about what programming language to use based on whether it's open source or not. There are freely available implementations of those languages.
If you've got your company, that's another story, do what you want. If you're basing decision on open source ideology instead of what's best for your employer, you're not doing your job.
Is the employer always right? Hell no. But making decisions based on open source ideology instead of the right technical decision, you'll be no better than the managers "upstairs" you like to complain about.
Writing a fully compliant JVM takes a lot of time and a lot of effort, especially the class libraries. Sun spent years writing that code, and none of the JCP partners can be bothered re-writing it themselves.
IBM, BEA, Oracle, etc pay Sun to license their source code so they can release compliant JVMs.
So, it should be no suprised the the open *cough*IBM*cough* source community "demands" that Sun open source Java. Guess how much money a certain company would save getting free source code that they're paying to license now? In the same of "the open source community", they'd like nothing better than to get the #1 competitor's hard work for free so they stop having to pay them for it.
The Java spec is open for anybody the re-implement, the source code is viewable by all, and the JDK is a free download. Sun has stated that they won't stand in the way of Apache Harmony or any other open source project that aims for a full open source implementation of the JVM/JDK spec.
So what exactly is the problem?
This space left intentionally blank.
Actually, FreeBSD were given a license at no cost by Sun, and any not-for-profit organisation with a need for access to a Sun-maintained compliance test kit can get it at no charge. So it's really just a matter of having the motivation to ask.
Yeah, because what the world needs is more php.
Really. At this point, who cares? If they did it at this late date it would speed up the process by a year or so at the cost of keeping Sun in the driver's seat. If they don't open their implementation GCJ will catch in a year or so and it will quickly become the reference implementation that everyone will track in server environments.
.NET today. But that is history that could have been and wasn't, now Sun needs to just continue to quietly fade away.
Why do I say that? Because it is the one all non-Sun/Microsoft server environments (meaning Linux & *BSD) will be shipping. RedHat is already there. If you want a different Java you have to deal with the implications of having it co-exist with GCJ. Although they do use alternatives to make that managable, they ship the IBM JDK on their extras CD, not Sun's and the Sun packages almost certainly (haven't bothered to check a recent vintage) don't deal with that, their 'rpms' are brain damaged tarballs wrapped in a thin rpm wrapper.
So it no longer matters what Sun does. Five years ago they could have turned around the fortunes of Java when it was under serious threats. Ten years ago OPening Java would have meant we wouldn't be dealing with
Democrat delenda est
I fear, some smart ass Java programmer will fork off the Java OpenSource and give some crackpot name like "Javalava" or "JavaJ" or "JuJu Bean" or "Grande Capacino"
I am scared...
"Don't let fools fool you. They are the clever ones."
You are failing to recognise the hidden costs here. Memory is cheap, paying a programmer is not.
Kaffe and GNU/Classpath are excellent, active projects with dedicated developers. Notably, GNU/Classpath has recently passed the 99% code coverage mark measured against the Java SE specification. Apache Harmony was started because Apache won't use code licensed under the GPL, not because of any technical defect in the work of the Kaffe and GNU/Classpath developers. Harmony is also making excellent progress and has a skilled and active community. Both are committed to making compatible implementations of Java, but licensed under the licenses their communities need.
The SCSL is going away in Java 1.6 in favor of some much more liberal licenses. I'll be able to compile and use it on my production FreeBSD server at work and not worry about being "tainted" as a programmer.
3 437481
http://www.internetnews.com/dev-news/article.php/
PHP is probably one of the best (worst) examples of what a language would look like if it was designed and developed incrementally in an open source community. It's hack upon hack upon hack. It's backward compatibility breaking changes is just about every point(!) release. Register_globals enyone? Magic quotes? Ambivalence towards types/objects - "type hinting". Arguably (and freely admitted by the designers) PHP is *not* a well designed language. It's a pragmatic ooops kind of language whose main advantage is a large (albeit somewhat amateurish) user base, and free availability. Java on the other hand - if anything - tends to be over-engineered. Swing is actually more flexible than even .NET Windows Forms (which was designed later). It's easier to combine widgets, e.g. put textboxes inside tree nodes, etc. Swing may be a little slow, but nothing Java has ever had that "hackish" feel to it. It's always well thought out. Same thing could be said about JSF, JDO and certainly EJB.
Sun has always taken great care of minimizing BC breaking changes. Sun has always taken pride in being a little on the conservative side, i.e. only introduce well understood technologies. This has been received well by the enterprise developer community. PHP is nowhere near that yet. There's still tons of BC breaking changes in store for PHP developers when PHP finally will get namespaces, unicode support etc.
To put it simple, the primary virtues of Java is nowhere to be found in PHP. And frankly, if PHP is the way a language looks like when it's designed by an open source community, open sourcing Java would possibly destroy it. A model like eclipse where it's formally open sourced but in reality still maintained by a single, competent organization might work, though.
Reading slashdot one-liner: (irm http://rss.slashdot.org/Slashdot/slashdot).rdf.item | fl title,desc*
Yared has long called for Sun to open Java, which, he said, is "great on the back end, but LAMP is great on the Web tier, as Google, Amazon, Yahoo, Flickr, MySpace and Friendster have shown.
Amazon is not LAMP.
Two major development platforms are .Net and Java. One is fairly Open Standard but not open source - and gets demands for Open Source. The other is not even open standard yet people accept this. Maybe the real issue is people can imagine a world where Java is totally open but don't ever expect .Net to be so don't bother discussing it (The wonderful Mono efforts aside)
As the two ACs who have been modded out of view said, that particular drug already exists - Jython - and is already supported in Java IDEs like NetBeans (via Coyote) and Eclipse. It's been interesting to see all the old urban myths about the Java platform being slow, bloated, single language and so on doing the rounds again though, I'd almost forgotten about them...
Please don't forget that utorrent requires Windows to run.
uTorrent is NOT self-contained. It requires the Windows API to run. This part of its footprint is not shown when you look at its memory usage, but that first 256MB of RAM that windows uses is the reason uTorrent looks so small.
I am much happier with Sun's Java than most open source projects out there. It's very high quality. I know that I may offend some people, but I think it's higher quality than Linux (as an OS, not kernel). It's my opinion though. Sun managed to keep it standard is admirable. I think Sun also deserve to make money/own the property it created. Why not develop open source version of it instead of asking Sun to open source it? One answer I think is that Sun does not have enough resource to fix bug or bring out features quicker for something as large as Java. This is a good argument. I think it could be addressed differently than Open sourcing it. For example, manage the development better. Provide better incentive for users to submit bug fixes. Promote Java support service so that critical bugs a company needs to be fixed is fixed quicker (it's there, but maynot be promoted enough). I develop Java enough to know that it's very hard to have a perfect tool to test Java standard. For example, there's no clear spec for Gridbaglayout. What you see isn't enough to implement an exact replacement for what Java has. This is just a simple example to show that stardard is hard to make, hard to be changed quickly.
This brings another point about Java standard. I remember JSF has many bugs that it tooks months to years to be fixed because the standard was broken. I think Sun needs to be much quicker than now to address these issue. These big problem should be fixed in a couple of weeks, or couple of months (2). Most people don't wait for a technology for a year or two to adopt it. They use alternative tech. This is usually a one way street and Sun will loose those customers.
What changes and how would depend upon which license was chosen.
And equally on what community process is chosen.
I regularly look at the source for some Java library class and cover my face in horror. I'm sure I'd submit a patch a week just in code cleanup and adding unit tests -- if I thought they would ever accept anything. An open license is only the start.
mod up!
Windows is loaded at startup as well as several services. Java initializes and caches its 100,000 methods in the JVM when a java applet starts which gives the appearance that its slow. However if you start a second app in java you will notice it will take ALOT LESS ram than if you just ran the second app seperately.
This is because of the loading and caching of the JVM and most of the core dlls that windows apps use are loaded at startup. Its kind of an unfair comparison.
http://saveie6.com/
I'm saying there is no time to lose. Newton is gone, Palm has hit the wall ... .NET mobile will be the only binary compatible handheld platform unless Sun act now.
.NET for embedded devices, and they're pushing it *hard*. The first words out of the mouth of every new MS guy I meet are "are you using managed code?". Every single presentation I've seen, block diagrams, feature lists, tools descriptions, every one has a block dedicated to managed code, c-sharp, and the portable dotnet framework right next to native code. It's pretty obvious that there was a directive from high on up of what to do and how to do it (I've never seen Microsoft so organized about something before). On the desktop side, they expect to kill Java by pushing out the dotnet framework with the next version of Windows, so things are currently pretty relaxed. On the server side, they are working on strong integration into all of their server products and all of their development tools (vb and asp replaced by dotnet versions). On the embedded side, they are pushing dotnet like it's the cure for every development issue ever.
As an embedded systems developer who has recently been dealing with Windows CE, let me tell you that Microsoft is pushing
The Java market is fragmenting. All these groups are taking it in different directions. The Apache people are re-implementing it, the GNU people won't deal with Sun Java, distribution is a mess. Microsoft offers a consistant product, a consistant platform, and a hard sell. Java is losing ground on the server side. On the embedded side, Microsoft is determined to "fucking kill [java]", and they're not resting. It's not all doom and gloom, Java will be around for a while. But it wouldn't hurt if Sun got off their asses and removed the obstacles in the way of their allies in the war against dotnet.
you are correct. but whatever we saved using java to get the project started, we have already spent trying to figure out why, oh, why java croaks on OutOfMemoryException when we have more than 8G of ram most of which is not being used.
on a more philosophical level, there is already an excellent VM that *can* use all the 8G and then some. it's called linux. using java to build apps because it's easy to program in is like using tonka trucks because those trucks are so much easier to handle than the real thing. after all, why pay commercial driver rates to drive a multi ton truck when you can get you own kids (for free) to 'drive' the tonka trucks.
i learned java back around '95, '96 and was really excited about it then. but after having used it on some really large projects, i have been really really disappointed and came to the conclusion that the only real contribution of the JVM was a serious neutering to most modern advances in the OS.
forget portable programming languages - use a portable OS - linux. and forget the V, use the M (tm).
anyhow, Guy Steel was right. i am looking at lisp right now (mostly for emacs tho).
In decreasing order of importance:
1) A free software license (GPL?) to allow for fast, active development, quick fixes of current problems, and license purity. Plus, imagine the boost if all those talented GCJ people put their efforts into the already rich Sun codebase!
2) Constant references! Please! Java's encapsulation is about as secure as Internet Explorer. A harmless getter method for a private member variable allows you to replace that variable with anything of your choice, because you effectively get a pointer to the member. The only current solution is to copy everything in the getter, which is unacceptably awkward and slow. So much for design by contract.
3) Sane memory requirements. Right now coding an inherently memory-intensive app in Java is very very difficult. I tried it once, and had to rewrite in C++ to get anywhere.
Pretty meaningless comment, unless you can supply some examples. I've done consulting and development for a number of large, lawyer heavy organizations, and none of them had a problem deploying Java solutions on linux. None.
"2. JVM is fat fat fat, it uses way more RAM than is reasonable."
Sadly uninformed, probably due to severe lack of experience with large applications. Per example, a couple of years ago I worked in a team that bid on and developed an application that, in a nutshell, receives up to 20Megs per sec of market data, breaks it up into itty-bitty messages, and then makes it available to any number of subscribing clients. Call it a proxy, if you will. We developed the app in pure Java, using the new NIO functionality. We competed with another team who started out in C, moved to C++ midway through, and were barely in a position to go alplha when we were ready to deploy. The client, since they were paying and had a lot of anti-Java staff, insisted on waiting, even though the delivery date had long since passed. When they finally had something to show, the apps were launched on identical hardware, and allowed to run 24/7. Our app ran smoothly, uninterrupted (except for a blown network interface) for the duration of the test. The other team had to restart their app several times a day, resulting in unnacceptable outages. Their restart time was, likewise, poor. Their app required 2Gigs to run. Ours ran happily under a Gig.
The client paid both teams for their efforts, then licensed our solution.
So, my quesion then is, where's the fat?
All of this is terribly ironic to me. I've worked with Java for about 6 years now. It's considered the Enterprise Open Source solution (because admin types typically confuse open source with "free and runs on lots of platforms) usually. So it's either Java or Microsoft in every shop I've ever worked for. No PHP. No Ruby. And often Java is paired up with Linux, MySQL, etc. So I find it funny (although I understand the point, but it's still funny) that people consider Java to be so difficult because it's closed source. In every shop where Microsoft is the choice, the decision is usually made because the stack is predictable. It's predictable because Microsoft controls every aspect of it from the database to the app server to the language you use to code on it. So open sourcing Java would probably have the unintended consequence of giving Java a perception problem in the eyes of manager types. It would become risky on the same level as Linux and MySQL and so instead of being the safe, "adult" part of that crazy open source stack, it would just become one more piece of it. Albeit a powerful one, but it would probably push more people into the arms of Microsoft. Sorry, but that's been my experience, given what I've witnessed in the industry lately.
Problem with this argument is that almost nobody runs Windows just to use uTorrent, while quite a lot of people run Java just for Azureus. The resources required for Windows are used by all applications (*including Java*), but most desktop users only infrequently use Java apps.
Business. Numbers. Money. People. Computer World.
As for the second point, there _are_ other portable execution environments in the world, such as the python runtime, which do not have the same order of magnitude of memory fragmentation and very poor garbage collection that java tends to exhibit. Sun java has an amazing ability to lock hundreds of megabytes in core when very little is going on in the running application. It somehow manages to achieve nearly pathologically bad cases of memory use fragmentation and page faults to keep hundreds of megs allocated even under significant memory pressure.
Even when writing the most boneheaded python code with extremely naive object creation strategies that end up hitting the VM ceiling, I never manage to lock more than a few tens of megabytes in real RAM. There are some types of applications which will tend to exhibit this type of pattern unavoidably, but the Sun JVM seems to maximize the potential for this poor condition.
Many people point out that the cost goes down as you share the jvm across multiple applications. I have some reservations about the abandoning of memory space seperation between different servies, but practically speaking in many cases the intial hundred or hundred and fifty megs loss is simply too high to care about the much lower cost of the second java application. On a server where a box may be dedicated to a single task or set of tasks, throwing 2, 4, or more gigs at the problem may be totally reasonable. For ad-hoc tasks, desktop tasks, etc, it often a dealbreaker.
-josh
I address question 1 elsewhere. There are legal barriers to convenient redistribution of the JVM.
Your second comment is a nonsequitor. My point is the Sun JVM is extremely greedy in allocating memory. You relate a story about a C/C++ project going poorly. Whether or not Java is a superior language and deployment environment for some types of applications (an argument I do not contest) is irrelevant to the fact that the Sun JVM significantly more memory than an equivalent program in a variety of other languages. There are many causes contributing to this, from the java gui classes, to common java programming style, to the Sun JVM memory fragmentation behavior and garbage collector. None of them is "fundamental". You could write better java code; you could clean up the gui classes or write better ones. The Sun JVM could be fixed or improved to have better behavior. On second thought I don't really know if the garbage collector semantics have any fundamental flaws, although I suspect they do not. In practice, however, all these problems do exist, and contribute to relatively plain longrunning java programs balooning to many tens of megabytes when other similar technologies (for example smalltalk) do not have any problems of the sort.
You may counter that java is nontheless a more practial virtual development environment than other available systems, a point I do not care to argue at this time. That is completely aside from the fact that the other comparable virtual execution evironments of comparable complexity do not suffer from nearly the same level of allocation bloat. Squeak for example executes a large virtual system complete with a wide variety of applications, runtime debugger and modifier, entire virtualized framebuffer, a comparably complex foundation library all within a few tens of megabytes, even when used over very long sessions. Java in similar situations will consume hundreds.
-josh
I have the impression that the last couple of months I see more people on Slashdot mentioning Common Lisp as a replacement for Java.
Here is a blog by a Microsoft ASP.NET dev describing the details (it's an interesting read):
http://weblogs.asp.net/scottgu/archive/2006/03/25
Note that some parts of MySpace still use
And just to add more proof (since I know that most here will be skeptical
-- "I never gave these stories much credence." - HAL 9000
Really, i mean it. At the moment, it's hard to find good developers who can leverage the advantages of java. What advantages i'm talking about? Let me explain. I am managing a team of developers (senior & junior) developing a large piece of software. Basicly it's a j2ee app, but with a simple desing, avoiding entity beans, using hibernate etc.. .net developer, the cost of a longer development schedule is a hard thing to defend againgst the management. Please don't start the usual, java is more productive if you know how to do this or that. We usually can't find guys good enough for that. If you can, then it's good for you. Generally our developers are not much experienced or skilled, and this is again related to our budget. We have a certain amount of money, and we are unable to hire the super developers that can use java in a very productive way. .net windows forms, ms office integration requests etc. agains the advantages of .net, we have the huge advantage of depending on specs, and providing better cost alternatives.
what we have done for all the project has been following the specs. we did not do any tricks for windows or any other os. We did not do any tricks for any app server. And now, our solution is able to work on three major os's that we have targeted in the beginning, without even recompiling. we really wrote once, and we're running wherever we need.
Against the more productive avarage
this is our reality, and under these circumstances, the only way we can win against the ms shops doing the same job, is to use our platform independence. we can come up with zero licence versions of our software for small customers, using linux, jboss and postgresql, and it just works. the eliminated licence cost gives us many advantages, and this is how we are going to win. Other than that, there are many problems in real life, like customers falling in love with
so, go ahead, make java open source, and starting from the one man utility developer to IBM, let everyone change anything since they believe it is a better method of doing x,y,z... So 3 years from now, working on the new major version, my software will no longer be easily portable to other configs. It will be possible, but it will cost me much more than today. That cost my friends, will make us go down in the not so long run.
Having a technology based on strict rules, has it's own advantages. in case of java, i believe these advantages far outweight the cons, but that's just me. However, i don't think my argument will be nonsense for many enterprise development projects.
I run a dual English/Japanese Fedora AMD64 and x86 win32 system, and have never had any troubles with java and language input or display on any of them. Especially with Eclipse which I use probably 5-10 hours of every day. SCIM-Anthy is great, it very quickly learned and suggested the most commonly used kanji versions too, as windows does.
I call bullshit - just because you don't know how to set up your machine properly doesn't mean java has language problems.
Servlet v2.4 container in a single 161KB jar file ? Try Winstone
Quoting Deb Goodkin of FreeBSD Foundation (from here):
We spent close to $35,000 for this release. It is hard to estimate the future costs of maintaining the Java releases since we expect to build updated distributions in response to all security advisories released by Sun.
So, while the license itself might have been given gratis, this clearly shows that the process of obtaining it was cumbersome and costly, and the result is still a limited, version-dependent, binary-only distribution.
Yes, Java is still evil. Changing license for something more liberal would certainly help much with adoption here.
So, my quesion then is, where's the fat?
Lets follow the logic here. We take 2 different sets of programmers, 2 completely different sets of designs and implementations, and by the way, because they are implemented using 2 different languages, this proves what exactly? Does the fact your competitors changed languages half-way through the project not give you a clue that competence might be a determining factor here?
I call bullshit - just because you don't know how to set up your machine properly doesn't mean java has language problems.
Great for you; I never got it to work properly (Ubuntu and SCIM/Anthy). I first had to add fonts to some java-specific list to get it to show CJK at all. When I run the app with Swedish locale it refuses to let me input Japanese (it does not listen to the SCIM server).
I'm sure I could get it working with enough effort - but after one frustrating evening I'm not going to bother. Java isn't alone out there; just about every Java app has good equivalents without the hassle (including the Kanji app I was trying to use). And I'm certainly not going to be using Java to develop anything knowing that potential users will have go through the same mess I do.
I should not have to "set up my machine properly" - most users do not have the technical skills to do so. I should be able to select "java" in the package manager (or rather, select the app I'm actually interested in) and it should all work - but it doesn't.
Trust the Computer. The Computer is your friend.
2. JVM is fat fat fat, it uses way more RAM than is reasonable.
1) You do know that tools such as top and ps report a lot more memory than is really used? This has been adressed in the upcoming Java 6, which will more accurately report the memory used, you will likely see a decrease of 25-55% reported memory use on Linux/Unix, and at least 11% of real memory used.
2) You can use jvm startup parameters to limit memory usage and still get acceptable performance.
Being bitter is drinking poison and hoping someone else will die
Because you forgot to give the JVM a permission to use that memory (with the "-Xmx8G" parameter) ?-) I hate it when that happens...
Linux is a virtual machine ?-o And here I've thought all this time that it is an operating system kernel.
More to the point, using Java (or any garbage-collected mandatory bounds-checking language with no way for the programmer to overflow the buffers no matter how hard he tries) is like using a seatbelt rather than just trusting the driver not to crash the thing.
Such as ?
Forget magic. Any technology distinguishable from divine power is insufficiently advanced.
That is the reason that with SUSE you can decide yourself wether or not you use it or not. e.g. for the upcoming 10.1 version the CD1-5 are pure OSS. There is an additional CD6 that will hold the non-OSS stuff, like Opera and Java.
That way SUSE lies the choice with the user, not with the distribution. If the user still decides to use it (and many will) they still have all the advantages as they have with the different other packages that are included with SUSE, including security updates.
Don't fight for your country, if your country does not fight for you.
Can't speak on the licensing, I'd say that the technology itself however is the complication in deployment. Java has a tremendous number of rough edges and that is was is the problem.
Now, before I take a moment to rag on your ridiculous RAM comment, let me assure you that I hate Java from that ground up. I find it to be little more than a virus.
JVM is thin thin thin. The fact is that most non-Sun implementations of the JVM are tight and small. In fact, from a performance perspective, Java is typically superior to compiled languages because of how it handles RAM. Before you blow me off, let me justify my comment. Thanks to the Java license and NDA agreements, I in fact can not say where I learned this information, but I have extensive experience in this topic since I was forced for extended periods to suffer the Java VM on embedded devices.
Java is a relatively simplistic (though strangley complete to the point of OVER KILL!!!) architecture/language/etc... It provides a language matched to a virtual machine matched to a set of somewhat poorly written libraries.
What makes Java superior to compiled languages is that it compensates for several key factors. First I'll refine my definition of a compiled language to clearly specify C/C++/Pascal/other non-garbage collected languages.
1) Application Developers are not System Developers
Using C++ as an example, most application developers use the standard implementation of new and delete. This is fine, but the first thing to keep in mind is that memory allocation for a C++ application that makes use of a lot of small objects tend to pay a huge performance price. C developers regularly shoot down the performance of C++ without realizing that it's the limitation in the C allocation routines.
Object oriented programming is typically very heap intensive. In many cases, developers insist on iterating through strings and lists far too much. Students are even taught in the university that data structures should be used absolutely everywhere. Of course they are taught Big-O and Little-O, but unless you're actually implementing the data structure classes and types, very little importance is placed on performance of these classes.
Strings are abused regularly since even though the allocation unit size of the heap allocator is limited to blocks of 16 bytes (for example), programmers will actually reallocate the buffer for a string to resize it from 8 to 9 bytes in length. By reallocating, I mean they will in fact allocate a new 9 byte string, then copy the original to the new buffer and delete the original buffer.
Application developers pay very little attention to the actual internal mechanics of the classes and functions which they use. To a certain extent, I can forgive them since an application developer is expected to think differently than a system developer. When we depend on system developers to write applications, they're often extremely fast, but relatively unusable.
So here's where Java shines, because of the garbage collection system and because of the relocatable memory architecture, memory is managed in such a way which decreases the cycles spent in allocation and deallocation of buffers. A well written JVM actually will actually either when necessary or when time is available compress the heap to maximize performance and minimize heap consumption.
So although Java seems like a memory hog, it's actually not that bad given the number of allocations and deallocations being performed by the developers. Sadly, the extreme memory use you're talking about is related to the poor system level development skills of application developers stacked on the additional layer which abstracts even more from the developer therefore making it less practical for the developer to understand the internals of the system.
2) System Developers make Terrible Applications
A system developer is typically biased towards raw high level languages such as C (not C++) because their used to making use of the stack whereever po
Programmer time is much more expensive than processor time these days. Therefore, many current programming languages are optimised to save programmer time first. C and C++ were designed in a time when processor cycles were extremely expensive, and therefore are optimised to save time at runtime instead.
As you have seen, java typically gets you results more quickly than C. In this case, since you simply took less time to get to your basic functionality, you could take more time to think about how to code more efficiently, and ended up actually writing faster code in the end.
However, java is not the only modern programming language out there. People have designed several new languages in the past decade. It seems reasonable to assume that some of those people deliberately set out to improve on java. Compared to such languages, java might appear to be very inefficient.
I'll leave it up to you to compare and decide. For instance, here's a comparison for web applications, done at JPL. (YMMV):
http://oodt.jpl.nasa.gov/better-web-app.movYes, you're right, it does cover a lot of licenses. In order to be allowed to use the trademarked term "Open Source" however, whatever license they choose must (a) comply with the Open Source Definition, and (b) be approved by the Open Source Initiative.
Sure, not all Open Source licenses are the ducks guts to all people, but there's pretty much an assurance of no evil in there. Even microsoft knows that!
"Men will never be free until the last king is strangled with the entrails of the last priest." (Diderot)
Half a SuSE installation? I haven't even got Linux compatibility compiled into my kernel.
$ uname -a/ i386/compile/LAPTOP i386
NetBSD tietokone.panews.press.net 3.0_STABLE NetBSD 3.0_STABLE (LAPTOP) #0: Fri Apr 14 22:31:45 BST 2006 root@tietokone.panews.press.net:/usr/src/sys/arch
$ pkg_info jdk14
Information for jdk14-1.4.2.8:
Comment:
Java Development Kit 1.4.2
Requires:
openmotif>=2.2.3
xorg-libs>=6.9.0
Description:
This is Sun's Java[tm] Development Kit, version 1.4.2, made buildable
and usable natively on *BSD/i386 by Greg Lewis and a host of others.
Azureus already uses SWT as underlying library, so this argument is a bit moot. SWT *is* using the underlying Windows functions for drawing. Nevertheless, Java will always use some more memory than a comparative (well written) C++ program, due to the class meta information that is included. You get a lot back in readability and in descriptive error messages, and several runtime advantages because of reflection (e.g. plugins). You need C# with .NET to get the same in a Windows only environment, and I wonder if such a program compares favourably.
http://www.object-refinery.com/classpath/statcvs/
Progress, over the last two years in particular, has been astonishing.
Only three things are certain; death, taxes, and apocryphal quotations - Ben Franklin.
Who cares how many projects are written in it, if it works better for you and does the job?
Personally I use Ruby (on Rails) these days for web development: convention over configuration is, imo, a much more important advance in the art than object-orientation was.
Bad analogies are like waxing a monkey with a rainbow.
It don't sound like they were but still.
Let me know point you to some of the most demanding applications in existence that push hardware to its limits.
Yes, games.
Now how many of the BIG titles that have your CPU and GPU groaning and gobble memory like it is candy are written in C/C++ vs Java?
This is as fair as your story for showing wich is the superior language.
The fucking fact is that it don't matter shit. I bet you could do the application you describe in perl as long as the person doing it is competent.
For fun, look up code that checks wether an IP has a valid format. You get the weirdest examples. Some look really cumbersome but would translate to fast code while some of the smallest regex would choke you cpu like a java GUI (Sorry had to get a java jab in to keep my cool license)
Frankly I think the fat is for a large part still there from the days of java applets that you got on your pentium with 32mb that took ages to load and then crash.
Funny thing, you still get those. They still take ages to load and then crash.
Java applets are offcourse not server side java BUT most people don't care. Reputation matters sadly enough.
Don't expect sympathy however as long as every java programmer says PHP don't scale. We all got our prejudices.
MMO Quests are like orgasms:
You may solo them, I prefer them in a group.
You may not realize, but "libraries are the new language". Seriousely, what good is a cool language if you have to reinvent the wheel everytime you want to have something like a report printer with print preview - a bit upset on python, with which I'm fighting right now to get something nice for a business app, I would really like something like jasper reports for python. Drawing on the DC with wx sucks for more then one form, and using reportlab to generate pdfs sucks as well. I've settled on doing a mono-platform hack, generating html with simpletal and calling its print preview dialog through ActiveX.
I'll do the stupid thing first and then you shy people follow...
I don't know if it would replace Java, but it would definitely empty many cups of it.
"You're everywhere. You're omnivorous."
You forgot to mention the fact that you *still* need the sun jdk to build the package, the fact that this is an 1.4 jdk, and you conveniently snipped the bit of the Description where it says that, really, "using it in a production environment is at your own risk".
;)
But that's all irrelevant - just like the fact that this is a pkgsrc-wip package, which is a more or less independant addition to the package set, and in practice means that you cannot use the quarterly stable branches - the fact still remains:
===> jdk14-1.4.2.8 is not available for NetBSD-3.99.18-x86_64
Or anything else but -i386. Really: I want coffee with my toast!
Flame away if you will but every Java app I've used (on Windows) has been clunky, buggy, and hard to use. None of the standard keyboard shortcuts seem to work, the apps *always* seem to be sluggish, and to top it off, they look funny - they don't inherit any of the look and feel aspects of the desktop. Now some smart Java person will say all these problems are fixable but it seems to me that it takes more effort to put out a quality Java app then say, an MFC or other similar program. The lure of cross-platform portability is nice but not at the expense of usability.
I'll stick to C++ and code in native development environments thank you.
convention over configuration is, imo, a much more important advance in the art than object-orientation was.
Convention over configuration is just another name for having sensible defaults, and nothing stops you from using that in Java. Indeed most Java frameworks have already added (or are working on) this.
Being bitter is drinking poison and hoping someone else will die
Sun don't allow redistribution or bundling of java JREs except under certain specific conditions. This makes java as a language unattractive to many organisations when compared with .NET and can also hurt developers tendering for work.
.Net. For the company, this means a single set of negotiations, one licence to review (Team A's app licence) and only 2 support contact points (Microsoft and Team A).
Lets take a hypothetical new company. So far, all they've done is bought Windows and installed their workstation and server population. Now they need an application to do Foo.
Team A propose a solution based on
Team B propose a solution based on Java. Now the company would have to have their lawyers review 2 sets of licences as opposed to one (Team A and Sun), and their support contact points climbs to 3. It also increases overall administrative hassle, as Java has to be patched / updated outside of their OS / application lifecycle.
Team B automatically look less attractive to the company because their hidden costs are much higher. If Sun just allowed Team B to bundle the JRE with their application, this would go away. Of course, then the different problem of every application trying to install Java comes up, but that can be got around by providing a 'JRE bundled' and 'No JRE' version of the products.
If you think that companies won't bother to review Sun's licence before installing Java, you'd be wrong... I've consulted at 2 different places now where they had their lawyers review the GPL and Java's licence before allowing deployment of products licenced under those.
Seriously, though, there are other problem domains out there. A lot of them, in fact. And even in web development, depending on the complexity and context of the solution, might require vast amounts of code that never interact with a GUI of any kind. When you evaluate these languages and platforms in context's outside of web development, Java starts to look far more robust and flexible.
As another poster pointed out, where are the buffered readers for ruby/php? Sure File.open("name") might LOOK nice, but Java's addition of a buffer solves a common problem many programmers in the past needed to solve by hand. There are about a thousand of these examples where Java's framework is more complex than its ruby/php counterpart, but for good reason: it adds much needed functionality for the enterprise developer.
Taft
In order to be allowed to use the trademarked term "Open Source" however, whatever license they choose must (a) comply with the Open Source Definition, and (b) be approved by the Open Source Initiative.
Did you even read the pages you were linking to? The Open Source Initiative's own certification page, that you linked to, has this to say, right in the first paragraph: "the term 'open source' itself [...] can't be protected as a trademark".
I can call anything I like Open Source, and nobody can do a thing to stop me. The new Evil Proprietary License (a viral license that infects any software in the same room with a deadly curse that can only be lifted by the sacrifice of your firstborn) could be called Open Source. What it couldn't legally be called is OSI Certified(tm).
Maybe we'll finally see an AMD64 Java plugin for Firefox.
Oh, no! You have walked into the slavering fangs of a lurking grue!
New NIO--is that like a PIN number for an ATM machine?
Media that can be recorded and distributed can be recorded and distributed.
-kfg
I might be mistaken here, but isn't "open sourcing Java" meaningless?
Java is an open standard already.
What I believe is being discussed, is whether Sun should open source their Java Virtual Machine (JVM) - Sun's implementation of the Java standard.
Why are you arguing as if I stated that java uses more memory than C? Has downsides, sure, but the point is that Java is _the most memory hungry language in the entire world_.
You can go look at language shootouts showing example code and note how java always allocates the most memory. You can look at real world server applications (tomcat vs medus vs apache) or real world client applications (bittorrent vs rufus vs azureus). You will find that java is always using way more memory than the competition.
Java uses more memory than C.
Java uses more memory than C++.
Java uses more memory than Common Lisp.
Java uses more memory than Smalltalk.
Java uses more memory than Self.
Java uses more memory than Erlang.
Java uses more memory than Icon.
Java uses more memory than Pascal.
Java uses more memory than Simula.
Java uses more memory than Python.
Java uses more memory than BCPL.
Java uses more memory than Perl.
Java uses more memory than TCL.
Java uses more memory than Haskell.
Java uses more memory than Ocaml.
Java uses more memory than javascript.
There is _no_ common denomonator to these languages. Some have virtual machines as sophisticated as the jvm. Some have simple hand-hacked runtimes. Some are compiled. Some have features and dynamicism Java cannot hope to touch. Some are terse. Some are verbose. Some are forgotten and old. Some are quite new. Java uses more memory than every single one, and that is a major weakness of java in practical terms at this time.
-josh
Who the hell would switch languages mid-project? C to C++ isn't a trivial switch, that or you ended up with some seriously shit code out of that wise move. Sounds to me like you're talking out your ass.
why, oh, why java croaks on OutOfMemoryException when we have more than 8G of ram most of which is not being used
Because you are rank amateurs who are unable to read documents or use profiling tools such as jconsole or YourKit?
I diagree. Java is far to bloated and complicated. I've been using it since it first came out and I balk at the vast array of libraries you need to use or choose between to get anything done. I feel really sorry for anyone coming to it for the first time.
So basically Java is the Linux of programming languages? You must really hate choice and having a large amount of problems already solved for you. Java is not for those with NIH syndrome.
#!/
One commentator said, "Sun should endorse PHP and go one step forward and make sure the 'P' languages run great on the JVM [Java virtual machine] by open-sourcing Java.
You are free to write a PHP Interpreter which is Open Source and runs on a JVM
I frankly don't know if it benefits me, or anyone, if Java is OSS. However it would be horrible if we face what we currently have with C++, litterally hundrets of compilers where everyone implements his favorite subset of the language definition.
angel'o'sphere
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
I just realized that in my entire life I've never once knowingly avoided the plague.
I doubt you will see much uptake from a PHP running on the JVM. When you port a langauge to the JVM, you typically leave behind the C bound modules, because they just DON'T play well with the JVM (frequently non-thread safe, etc). For this reason languages that have nothing to offer but their c bound modules (Perl, PHP) don't fair well. Languages like Python and Ruby that have significant things to recommend them as languages do much better.
Interesting...I've had the opposite experience. I spent time in the MS camp where there are a wealth of 'VB for dummies" books but everything beyond that comes from Microsoft itself, and you better have a MSDN subscription. With Java it seems there are tons of free online resources for specific questions, and there are also some very good books like "Thinking in Java" (perhaps a bit dated now) that get the beginner to the point of understanding all the basics, without being condescending the way, for instance, MSDN so often is.
Then again, given the languages you list Java may not be useful for what you do. If it might be, though, I'd give it another try...
Premature optimization is the root of all evil
I diagree. Java is far to bloated and complicated. I've been using it since it first came out and I balk at the vast array of libraries you need to use or choose between to get anything done. I feel really sorry for anyone coming to it for the first time.
I really don't understand this. Having a rich and versatile range of libraries is a problem?
Personally I use Ruby (on Rails) these days for web development: convention over configuration is, imo, a much more important advance in the art than object-orientation was.
And Java has had this for years. I use JDO to persist my Java objects (it is a far more powerful and versatile system than Rails - much faster, and can persist to non-relational stores as well). How much configuration do I need in principle to describe my schema? Nothing but a list of classes. By default, the schema is created and mappings are automatically set up based on the field names of my classes. By default, no configuration needed.
How long has JDO had this? Since 2000!
Convention over configuration is nothing new.
It is already being worked on, and you can download and try it out today (though it's not finished yet). It's called Quercus, from the guys who do the Resin open-source app server. (Which is a fabulous piece of work, I might add.) It compiles PHP to Java bytecode, which can then be JIT-compiled to native code.
There is _no_ common denomonator to these languages. Some have virtual machines as sophisticated as the jvm. Some have simple hand-hacked runtimes. Some are compiled. Some have features and dynamicism Java cannot hope to touch. Some are terse. Some are verbose. Some are forgotten and old. Some are quite new. Java uses more memory than every single one, and that is a major weakness of java in practical terms at this time.
I know. This is a real weakness in Java. It would have been great if it was a far more memory efficient languages, because then it could have been used in a wide range of low-memory situations like embedded devices, PDAs or mobile phones....
Er - something wrong with this argument, perhaps?
hi again! ;)
"Having a rich and versatile range of libraries is a problem?"
nope. the problem is when you have a poor enough language without support for high level constructs and has to do literally anything with libraries. it's just a lot more tiresome than builtin language support...
"Convention over configuration is nothing new."
yeah, shame it's not used more often in the java world rather than the XML craze...
I don't feel like it...
You hit it precisely on the head. Linux and Java proponents tend to have a particular problem with being unsympathetic to n00bs
Unlike Linux, Java is very well documented, so having to interact with a community is not necessary to learn and use it (the language itself). There's plenty of books, as well as courses you can take (since it is so mainstream).
Once you start using 3rd party libraries and tools, then you might need to interact with the community. Just like any large online community dealing with tech, there's always a few assholes and elitists (it's people on the Internet, what do you expect?). If that's enough to push you away from a particular technology, you might as well give up on anything that requires interaction with people.
#!/
So basically, random individuals on the Internet (who had no connection to Sun I assume) made you lose interest in a programming language. I can understand if the developers of a product are pricks and that turns you off of a product, but I'm sick of hearing "I don't use it because people told me 'RTFM' or 'Google'". That happens everywhere on the Internet. That's what anonymous/semi-anonymous non-face-to-face communication does to people. Get over it.
So I take it you don't use Linux either because some big, bad forum jerks told you "RTFM" too?
#!/