Java SDK 1.5 'Tiger' Beta Finally Released
kingkola writes "Finally, after about two years of development, the Beta for Java SDK 1.5, aka Tiger, has been released. Features added in this edition include generics support, autoboxing of primitives, syntactic sugar for loops, enumerated types, variable arguments, sharing of memory between multiple VMs and a bunch of other bugfixes, enchancements, etc."
Why use Java in place of better known and popular languages? There's certainly no efficiency motivation; anybody who has ever programmed in a real world environment knows that Java is slow and C is fast.
warning, goatse link in parent post
"Features added in this edition include generics support, autoboxing of primitives, syntactic sugar for loops, enumerated types, variable arguments, sharing of memory between multiple VMs and a bunch of other bugfixes, enchancements, etc."
... decades late. :)
So essentially it's become C++...
The ratio of people to cake is too big
Looks more and more like Python. All I need now to move from Python to Java is just same small size of memory footprint and ability to interprete the source code. No need to mention FP-things like list comprehensions. Until then - keep your coffe for your blind-dumb managers. I use a real language.
Less is more !
*Sigh*... you can get precompiled binaries for Windows x86, Linux x86, Solaris SPARC and Solaris x86. Whoopie. Gee, how exciting.
Oh, and the downloads page actually confused me for a second. They have a giant section labelled "32-bit/64-bit for Windows/Linux/Solaris SPARC
32-bit for Solaris x86". I kept thinking, "Why do they offer a Linux SPARC version but not a Linux x86 version??" Then I figured out how to parse it. When they write "Linux", they mean "Linux x86", because there aren't any other Linux architectures on the whole planet, right? Sheesh.
Excuse me while I continue not using Java(R)(TM) on my HP-UX workstation at work, or on my OpenBSD x86 box at home (but Kaffe sort of runs on the latter).
Why can't Sun just release a god-damned TARBALL OF THE SOURCE CODE and say, "Here you go. Here's Java 1.5.0 release candidate 1. We'd like to have some help porting it to FreeBSD, OpenBSD, NetBSD, BeOS, Mac OS X, AIX, HP-UX, Tru64, IRIX, and so on. Patches are welcome. In fact, we've released the entire thing under the new BSD license (without advertising clause), so you can integrate it with your applications, include it on official Debian CDs, etc."?
*Sigh*
I hate it when someone makes a valid point and gets modded down because it's controversial.
Come to the realization friends; Java IS slow.
Personally, I LOVE Java as a pedagogical tool to aid in teaching computer science, and I had the same love for Logo, but obviously both of these languages have at least one thing in common; they are hampered by the fact that they are slow.
I don't know the meaning of the word 'don't' - J
Yes, I know that we're locked in to MS OS and server, but given the incredible productivity increase, this is a small price to pay.
Having the entire technology infrastructure of your company depend on one (evil monopolistic) vendor is a small price?
1. A good IDE.
Nice to have, but you don't need it if you can code. A good text editor is all a REAL programmer needs.
2. Servers that are not obtuse. I can get IIS to do anything in about 5 minutes. It takes hours or days to do anything in Tomcat or Resin and Apache.
What on earth could you have to do with Apache that would takes hours or days? Unless, as I'm beginning to suspect, you're an idiot who is in the IT area because it pays well, not because you are actually competent or anything.
And finally, when you say operator overloading, you lose me. My opinion of operator overloading is that it is absolutely bad. Let me be clear. It is always bad, under any circumstances, when used for any reason. It has exactly zero functional value, and, as opposed to other kinds of "syntactic sugar" it has a tendency to make code where it is used with any frequency into a confusing, unmaintainable minefield. When advocating for operator overloading you are basically advocating a programming style with 1 letter method names, only it's worse, because you're limited to a few "commonly used" letters.
// fuck you in the ass
cock*you[1]