Java 7: What's In It For Developers

GMGruman writes "After five years of a torturous political process and now under the new ownership of Oracle, Java SE 7 is finally out (and its initial bugs patched in the Update 1 release). So what does it actually offer? Paul Krill surveys the new capabilities that matter most for Java developers, from dynamic language support to an improved file system."

Comments

Kill it Oracle

[Anonymous Coward]

Oracle can't kill Java fast enough. Once it's dead we can go back to having actual competent people writing code rather than Java weenies who couldn't code themselves out of a paper sack without a VM to hold their hand.

Re:Kill it Oracle

[Anonymous Coward]

You can always tell a language fanboy. He's the one with no computer science degree. He's also a flunkie that needs to attack other languages because of his own inadequacies as a developer and as a person.

Re:Kill it Oracle

[Anonymous Coward]

You can always spot a Java weenie. They get super defensive at any criticism of their shitty language. They're also so poor at being a programmer that their code is still able to leak memory despite the presence of a GC in the language.

Oh and I don't program in C or C++ if that's what you think, weenie boy.

Re:Kill it Oracle

[LordLimecat]

You can usually spot "likely to be baseless" criticisms on slashdot, even if youre not up to date on the particular topic. Usually they are made by ACs.

Re:Kill it Oracle

[Anonymous Coward]

So I take it you're a VB6 developer?

Re:Kill it Oracle

[Anonymous Coward]

The last guy who signed an expensive licensing agreement from Oracle to use Java 7 ended up looking like this.

Re:Kill it Oracle

[Anonymous Coward]

Ah yes. The old "blame the language for the lack of a developer's skills" ploy. It's a sad carpenter who blames his tools for his incompetence. It's a sadder carpenter who blames a tool for other carpenters' incompetence.

Just curious: what do you think all those "Java weenies who couldn't code themselves out of a paper sack" would do if Java died. Would they magically become skilled code gurus because Java doesn't exist? Or would they be incompetent coders in a different language?

As Dilbert so succinctly put it: you're solving the wrong problem!

Re:Kill it Oracle

[binarylarry]

I hate to break it to you asshole, but all languages suck.

Re:Kill it Oracle

[Afforess]

Let me get this straight - you think that a harder programming language increases programmer competence. While I'm not defending Java, this logic is deeply flawed.

If you follow it to it's logical conclusion, the best programmer's flip the machine bits by hand...

Re:Kill it Oracle

[Rik Rohl]

Obligatory xkcd

Re:Kill it Oracle

[AliasMarlowe]

If you follow it to it's logical conclusion, the best programmer's flip the machine bits by hand...

Correct: the best programmers can use machine code if needed. But the best programmers also don't abuse the apostrophe as much as you did...

Re:Kill it Oracle

[slack_justyb]

Warning goatse link in parent!

Re:Kill it Oracle

[Afforess]

If you follow it to it's logical conclusion, the best programmer's flip the machine bits by hand...

Correct: the best programmers can use machine code if needed. But the best programmers also don't abuse the apostrophe as much as you did...

If I found out someone was manipulating code at the machine level - I'd definitely have issues with that. You lose portability and expose yourself to a nearly infinite amount of issues - there really aren't many cases left where this would even be remotely advisable.

PS. Nitpicking grammar - that's nearly as bad as using machine code directly. :p

Re:Kill it Oracle

[Anonymous Coward]

It is not goatse. Totally different guy doing something even more extreme.

Not something new like this. No butts on this last one

Re:Kill it Oracle

[Lord Kano]

Ah yes. The old "blame the language for the lack of a developer's skills" ploy. It's a sad carpenter who blames his tools for his incompetence. It's a sadder carpenter who blames a tool for other carpenters' incompetence.

I can't speak for other workplaces, but there are certain languages that people at my company develop in and you can get a pretty good idea of a programmer's skill level by what language he develops in. Anyone who develops in only one language is very good at that language. S/He can solve any problem you throw at him/her in that one language. There's nothing wrong with that per se, but demand is not constant. Sometimes, they need more people in a different department. If you are a one language programmer, you have very good odds of being let go when that happens. If you are competent in many, you can go far.

The hands down best programmer I ever worked with could code in anything from FORTRAN 77 through .NET and his code was always amazing. But, that's one out of hundreds.

LK

Re:Kill it Oracle

[secretsquirel]

except for l0lcode at least :(

Re:Kill it Oracle

[AliasMarlowe]

If you follow it to it's logical conclusion, the best programmer's flip the machine bits by hand...

Correct: the best programmers can use machine code if needed. But the best programmers also don't abuse the apostrophe as much as you did...

If I found out someone was manipulating code at the machine level - I'd definitely have issues with that. You lose portability and expose yourself to a nearly infinite amount of issues - there really aren't many cases left where this would even be remotely advisable.

Well, that's why I emphasized the "if needed" bit. I suspect that cases where a real need for machine code might arise are probably limited to embedded systems and other single-architecture real-time applications, where a complete re-write (from specs) would be needed for a change in architecture.

PS. Nitpicking grammar - that's nearly as bad as using machine code directly. :p

Hmm... now was I picking at a grammar nit or a spelling nit? Or were you suggesting that grammar related to a disgusting activity is nearly equivalent to direct use of machine laguage?

Re:Kill it Oracle

[mywhitewolf]

You can always spot a "over the squabbling" post as it normally sits at the end of a chain of AC's, normally followed by "THIS!" and also someones request to "mod parent up!"

also, mod parent up!

Re:Kill it Oracle

[mywhitewolf]

there is a difference between understanding how the computer does what it does (and a logical extension of that is knowing how to change it should that be required), and actually attempting to do something via machine code. but you're right, modern day programming is a different beast than old school logic gate manipulation.

Re:Kill it Oracle

[GigaplexNZ]

Lolcode sucks, it just sucks in a fun way :/

Re:Kill it Oracle

[Ragondux]

Ah yes. The old "blame the language for the lack of a developer's skills" ploy.

Well, the thing is, one of the goals of Java was to deal with bad programmers by putting safeguards, not having features like multiple inheritance that are useful but require you to have a brain, and forcing you to either catch an exception declare that it can be thrown, among many examples. These are useful, but frustrating if you're prototyping, and not mecanically implementing a well designed specification. Anyway, all those safeguards mean a bad programmer may be able to write some working code in Java.

On the other hand, take Perl. It was meant for good programmers, has no safeguards, and in many ways relies on the programmer using it the sane way. For example, it doesn't enforce public/private access, but instead relies on you to be polite and not access private stuff. No bad programmers could ever be productive in Perl, but a lot of decent-to-good programmers found it very helpful (before Python and Ruby came).

So, in the end, you'll have more bad Java developers than bad Perl developers, just because Java is more friendly to them. Of course, if Java died, its bad developers wouldn't magically become good developers by switching to another language, but they'd either find another dummy-proof language, improve their skills, or change jobs. Just like if PHP died, a lot of crappy web developers would have to either find a replacement that still allows them to write websites without learning to code, or change hobs.

Re:Kill it Oracle

[neokushan]

A Language that gives you head? Where do I sign up?!

Re:Kill it Oracle

[Kjella]

There are places where it's still very legitimate, like high performance crypto libraries, video processing, graphics engines, that sort of thing. Typically you have a reference implementation in C or some other portable language and the assembler is conditionally compiled in, so it works on other platforms but you only get the extra performance boost on that particular platform. It's a niche but so is kernel and driver development, it still makes sense to have some people specialize and do those specific tasks. I wouldn't go it as a career though, there's way, way too many developers from the "bad old days" who know all about shaving two bits and four instructions off a calculation.

Re:Kill it Oracle

[angel'o'sphere]

I don't really get why people emphasize to be able to program in assembler. Or machine code ...

Do you really believe a programmer who can program in Java or even Visual Basic is incapable of learning assembler?

For most programmers there likely never was a need to learn any assembler or more than 2 languages ... nevertheless assembler is easy to learn.

There is no magic about it.

Re:Kill it Oracle

[Anonymous Coward]

No, I think the Java weenies should be fired en masse and replaced by competent people. Then the Java weenies can work at the fry cook station which is more apt to their abilities as mouth breathers.

Re:Kill it Oracle

[ByOhTek]

Umm, incompetent numbskulls such as yourself can program in any language - Java, C#, Perl, Python, PHP, C, C++...

I've seen idiocies in ALL of them. There are things I hate about Java (and reasons I would never use it for my own projects, unless the only other option was Perl), no doubt about it, but blaming it on people not being able to program... I feel sorry for your boss if you are a developer.

Re:Kill it Oracle

[Anonymous Coward]

The old "blame the language for the lack of a developer's skills" ploy.

Only in your imagination. Java, like PHP, specifically sought to attract the low end developers away from VB; and those who struggled with basic C/C++. The fact that Java is purposely a very limited and dumbed down C++ is further proof in the pudding. In fact, that was part of the marketing strategy. They basically positioned Java as the C++ for idiots. That was their whole enterprise marketing campaign - you don't need expensive, good, C++ programmers when you can do the same with shitty, third rate (frequently third world), cheap, Java programmers. That literally was the push into the enterprise with Java.

While not politically correct to say so, the FACT of the matter is, Java is C++ for idiots. That, of course, doesn't mean ONLY idiots use Java or that C++ has no idiots, but the sad fact is, Java, like PHP, has a vastly disproportionate number of shitty programmers.

Did the language make them shitty? Absolutely not. Do these languages attract a large number of shitty programmers? Absolutely, yes!

Sorry, but this is one of those classic cases where politically correct or not, the fact is, the non-politically correct answer is factually true, regardless of how much it offends your sensibilities.

Re:Kill it Oracle

[c00rdb]

Not english

Re:Kill it Oracle

[GooberToo]

Let me get this straight - you think that a harder programming language increases programmer competence. While I'm not defending Java, this logic is deeply flawed.

Glad to know you're here to fix the entire world's education system. Sorry, but YOUR logic is deeply flawed. With your logic, none of the "good schools" are actually any good. So yes, clearly those capable of mastering difficult tasks show they are better in any way.

I'm going to take a wild stab here and say, perhaps you are a Java programmer? And even if you are not, YOUR logic is dubious at best and in no way invalidates the line of thinking which spurred your initial response.

Re:Kill it Oracle

[Anonymous Coward]

Do you really believe a programmer who can program in Java or even Visual Basic is incapable of learning assembler?

Of course not. They'll be a much better programmer once they have learnt at least one assembly dialect, however.

Re:Kill it Oracle

[GooberToo]

I don't really get why people emphasize to be able to program in assembler. Or machine code ...

Says a lot. There are still plenty of platforms where assembler is REQUIRED. Furthermore, on others, even where higher level languages, such as C, are available, to access certain hardware features are still only available via direct assemble and/or machine code.

Do you really believe a programmer who can program in Java or even Visual Basic is incapable of learning assembler?

Bit of a red herring there. Capable of learning? Probably they are capable of learning. Do they have a desire to learn it? Probably not. Are they capable of learning it well? Maybe. Are they capable of understand the overall implications of some of the code they may generate at this level? Its iffy if we're talking about the average Java coder.

nevertheless assembler is easy to learn.

Reading a dictionary is easy. Remembering the words and knowing how to put them together properly and concisely is an entirely different animal.

Re:Kill it Oracle

[Anonymous Coward]

It would seem I've hit a nerve. It must be embarrassing talking about your lack of education when it comes up. Now, go back to your cubicle, code monkey.

Re:Kill it Oracle

[alexo]

Let me get this straight - you think that a harder programming language increases programmer competence. While I'm not defending Java, this logic is deeply flawed.

Not speaking for the GP, but my take is that the harder the language, the less incompetent programmers it will attract.

Think about it this way: if any idiot can do VB then every idiot will do VB (in preference of other languages).

That said, if a language is merely hard, with no added benefits in power, expressiveness, etc., it will also fail to attract the competent programmers.

Re:Kill it Oracle

[Toonol]

I think that the best programmers learn the hardest and most difficult languages in order to improve their skill, and then actually program in the simplest language that meets the criteria for the task.

I don't like Java much, but it has a purpose, and good code can be written in it. Heck, old VB had it's purpose, and a niche where it was far superior for development purposes than C++.

Re:Kill it Oracle

[Raenex]

Did you really choose Perl as your unsafe language? I thought you were going to describe C. Perl copies lists and strings by default because it's the safe thing to do, even though it is inefficient. Perl added "use strict" and it is widely encouraged and used. Perl doesn't enforce public and private because it is a dynamic language derived from shell programming, and its object-oriented features were tacked on with superglue.

Perl does have a lot of crazy magic and syntax, but that's just a reflection of the designer. Lots of good programmers don't like it, and hence Python was born.

The reason you have more bad Java developers is because that's the language business gravitated to after tons of bad developers were making a mess in other languages, like C and C++. As another example, PHP, has a lot of confusing design choices and lots of ways to screw up, but tons of programmers use it, bad ones included, because it's a very popular language on the Web.

Re:Kill it Oracle

[Raenex]

The correct use of apostrophe is grammar, not spelling, as it concerns syntax.

Re:Kill it Oracle

[Ragondux]

I didn't describe Perl as unsafe, but as difficult to use for bad programmers, and requiring skill to be used properly. That's also the case with C, but for historical reasons and because C is closer to the hardware. Perl was designed that way.

The rest of your message is rephrasing what I meant, so I agree... but maybe I wasn't very clear in my post.

Re:Kill it Oracle

[rhendershot]

I don't really get why people emphasize to be able to program in assembler. Or machine code ...

Says a lot.

says nothing at all. using C++ or C# or Java is a conceptual skill quite apart from machine level programming. Everything from threading to object/data maintenance to looping is different in a fundamental way.

I'm one of those "uneducated" (my background is Electronics, not CompSci) java programmers doing mostly business applications. I would only assert my competence. I also entered machine code in Heathkit ET3400 as well as C= Vic20/128. I repaired arcade video games like Defender and MsPackman also.

People learn what they're interested by and what they are required. The "average" anybody is not going to excite... talk about red-herring...

Do you really believe a programmer who can program in Java or even Visual Basic is incapable of learning assembler?

Bit of a red herring there. Capable of learning? Probably they are capable of learning. Do they have a desire to learn it? Probably not. Are they capable of learning it well? Maybe. Are they capable of understand the overall implications of some of the code they may generate at this level? Its iffy if we're talking about the average Java coder.

The truth of the matter is that C and below programming is really not necessary to the majority of today's programmers. I also modified xmodem on a coherent system where I had dial up. I did that to skip the 64, 128, 256 progression it did to bring up to speed. most of my transfers were 1k or greater and starting at 1024 made a huge difference in the kind of quick transfers I needed to do. I got my first job in software programming by showing the place in that C source code that I modified... why and how.

Even today I think the better, elegant solution eluded me at the time. But it worked; both in a pragmatic and preparatory sense.

That's all starkly irrelevant to job-health today for me though.

Re:Kill it Oracle

[Raenex]

What you described as features for bad programmers in Java were safety features. The only really valid claim you'd have for Perl was the horrid syntax and abundant magic, but you didn't mention those. You also can't explain why PHP is so popular and full of mediocre programmers when it's essentially Perl for the Web.

Re:Kill it Oracle

[leenks]

Not speaking for the GP, but my take is that the harder the language, the less incompetent programmers it will attract.

Surely the harder the language, the less programmers it will attract. There will be a similar proportion of incompetent ones in that language.

Think about it this way: if any idiot can do VB then every idiot will do VB (in preference of other languages).

Then why don't the programming Gods use VB? I'm pretty sure they can all code VB if they wanted.

Re:Kill it Oracle

[alexo]

> Surely the harder the language, the less programmers it will attract. There will be a similar proportion of incompetent ones in that language.

Not so, the incompetent one will choose easier languages instead, ones that mask their incompetence.

> Then why don't the programming Gods use VB? I'm pretty sure they can all code VB if they wanted.

I knew at least one that did.
He used VBA for MS-Office macros and straight VB for prototypes.

Re:Kill it Oracle

[angel'o'sphere]

Says a lot. There are still plenty of platforms where assembler is REQUIRED. Furthermore, on others, even where higher level languages, such as C, are available, to access certain hardware features are still only available via direct assemble and/or machine code.

Sorry, that si completely incorrect. Everything I can do with assembler, I as well can do with C/C++ or Modula 2 even. Except emitting the INT xyz opcode which is *perhaps* required for something.

I'm not really sure people know the difference between assembler and machine code ... there are far to many strange posts using the words ;D

I saw a post on stackoverflow lately where people talked about displaying java byte code operations by reading the class file and showing its opcodes. Some guy strongly argumented this was not "disassembling" as it only translated a byte into a mnemonic ;D

Re:Kill it Oracle

[Anonymous Coward]

> Not so, the incompetent one will choose easier languages instead, ones that mask their incompetence.

And out of those that choose the harder languages there will be a number with inflated egos that think they are awsome when they are actually incompetent in those languages.

A language with a file system?

[John Hasler]

WTF?

Re:A language with a file system?

[pauljlucas]

I assume the author meant, "... to improved file system access." See here.

Re:A language with a file system?

[LordLimecat]

Not being a programmer, I would guess that it has something to do with Java running on a VM, and needing some way to interact in a universal manner with the host OS's FS.

Any Java whizzes want to comment?

Re:A language with a file system?

[Anonymous Coward]

It is a poorly written article. What he means is that Java has a new version of the File APIs which is meant to make working with files easier and faster.

Re:A language with a file system?

[iggymanz]

It's just improvements to the I/O API. Java has the New IO API for doing I/O. java 7 has extended it, hence NIO2. http://www.ibm.com/developerworks/java/library/j-nio2-1/?ca=drs-

Re:A language with a file system?

[Anonymous Coward]

The improved file system API isn't even really about I/O, it's about a better API for querying file system metadata more or less.

Re:A language with a file system?

[whiteboy86]

Bullshit feature or not, it is another cherry on Oracle's fooled execs' lunch pie.

Re:A language with a file system?

[Anonymous Coward]

I don't know what you were voted up for, but it is kind of obvious that it means "an improved file system API".

Re:A language with a file system?

[Joce640k]

Why are you both confused/assuming? Too busy to read the article?

Re:A language with a file system?

[mywhitewolf]

It's really not that obvious in the summary.

Re:A language with a file system?

[NotBorg]

Thats why the summary links to an article. You must be new here.... oh wait... You'll fit in great here. Carry on.

Re:A language with a file system?

[wvmarle]

I hope this means they will have basic functions like copy built-in. I was quite surprised when I took up Java on Android that such a function was simply not there. And that I basically had to add it myself (luckily code snippets all over the place, but still). The whole I/O felt very primitive to me - it may have its advantages to do it that way, but me coming from Python is used to being able to address files much easier.

Re:A language with a file system?

[DrXym]

Well it is. It has new asynchronous channel functionality and the FS stuff also allows Java to watch directories, walk through them, examine attributes and other stuff. Java is generally a good language but some stuff particularly Date & Time and IO have been pretty mouldy and long over due a revamp.

Re:A language with a file system?

[Exitar]

Read the article? Do you know where you are?

Re:A language with a file system?

[GooberToo]

When I first started doing Java, I was shocked and amazed at how very shitty the entire IO model and APIs were for IO and Data/Time. Literally, doing it in C++ and especially Python would have been leaps about bounds faster, easier, and better. I quickly found my self wonderful why so many claim Java development is faster than C++ when in these areas, clearly it is not.

Re:A language with a file system?

[DrXym]

Date & time is a particular bug bear because I had to write an embedded system which dealt with time dependent data, had to cope with local time zones, daylight savings changes and data which was based off UTC. I think I did a pretty good job in the end but it sure as hell wasn't helped by the system libraries. The trick is to use time in millis from the epoch and never attempt to convert to / from local date at all except to present the data to the user. It's still a pain though. I would have used Joda time but it was too big and bloaty for embedding properly.

all i do

[Anonymous Coward]

is think about you.

you made my soul a burning fire
you're getting to be my JavaOne desire
you're getting to be all that matters to me

Re:all i do

[iggymanz]

Well since JDK downloaded, ant XML in my head,

jars, wars, and .class files all night with laptop by my bed,

well java you look so fine (look so fine)

for C++ errors took all my time,

for you to help me java

get Stroustrup outta my heart.

help me java, help help me java

help me java, help help me java
.........

help me java, yeah, get him outta my heart.

Bjarne was gonna be my god,

and we gonna be his bitches,

preprocessor bloat came between us,

patterns ruined by the glitches

The answer is...

[Anonymous Coward]

A: Not much that is interesting given the number of comments?

One day we will be done with java...

[FlyingGuy]

But not soon enough. FTFA...

Project Coin's diamond syntax for constructor calls lets the compiler infer type arguments, and the try-with-resources statement helps the compiler make reliable code by automatically closing files, sockets, and database connections when developers forget to do this, Ratcliff says: "That's something that's been tripping up developers -- especially young developers -- for years. That'll be a good productivity improvement and will reduce bugs."

I mean if that doesn't say it all I don't know what does. Hmm Allocate a resource, Free a resource. I think they still teach that in CS-101, then again maybe not. I alloc() therefor I free() ?".

Re:One day we will be done with java...

[Anonymous Coward]

While you are busy being a jackass and letting us all know you have never made a single mistake EVER with resource allocation, some of us have work to do and enjoy the fact that we will never have to type try{openFile}catch(DamnException){}finally{try{closeFile}catch(AotherDamnException){}} ever again.

Re:One day we will be done with java...

[PerformanceDude]

Please mod this reply up! Despite the slightly offensive language, it is NOT a troll statement. That new construct certainly has the potential to eliminate basic mistakes, which invariably will lead to more stable code. It is almost like a garbage collection for resources - and the value of that is (in my opinion) beyond dispute.

Re:One day we will be done with java...

[Anonymous Coward]

Ruby showed the value of this technique as well. The Java haters live in ignorance. Java is frequently used to solve difficult integration problems that require the use of diverse resources; database sessions, networks connections, file system resources, etc. Simplifying the code necessary to do this while reducing the chances for leaks is a genuine improvement.

Re:One day we will be done with java...

[Anonymous Coward]

So, it's basically like C++'s ancient RAII...

You know what? Bjarne Stroustrup was right: The more useful Java becomes, the more it approaches what C++ already provides.

Re:One day we will be done with java...

[ADRA]

Thanks for the object lesson dick.

1. Raii gives you the -ability- to reclaim resources after a fault, and that's something Java's had since 1.0. The new IO construct just means that IO resources are AUTOMATICALLY reclaimed when problems occur. The meaning is simply that dev's don't have to worry about it

2. If you mean writing a hell of a lot of useless boiler plate and trouble laden code to deal with things that devs are isolated from in Java, then yes. Flip this around. C++ is fixing problems through language, libraries, etc.. that Java has long been able to do safely for years

Re:One day we will be done with java...

[Anonymous Coward]

While you are busy being a jackass and letting us all know you have never made a single mistake EVER with resource allocation, some of us have work to do and enjoy the fact that we will never have to type try{openFile}catch(DamnException){}finally{try{closeFile}catch(AotherDamnException){}} ever again.

And of course, don't forget how try-with-resources fixes common bugs where an exception in closeFile gets swallowed, or overrides the original exception...

Alas, I guess the C# people will chime in about have they've had "using" forever... but hey, great language designers don't borrow, they steal. :-)

Re:One day we will be done with java...

[bonch]

In the 50s and 60s, programmers were skeptical of using a high-level programming language in place of assembly, but the productivity and understandability increase was too great to ignore. Today, using assembly is frowned upon expect in very specific situations. In fact, compilers are generally regarded as being capable of doing a better job than a human could.

The computer exists to do work for you, and that inevitably includes managing its own memory. Automatic memory management in some form is an inevitable future for most application programming.

Re:One day we will be done with java...

[Jmc23]

Wow, so it's almost like lisp?

Re:One day we will be done with java...

[nstlgc]

The punchline being that C# has had "using" clauses (try-with-resources) since 1.0 and its compiler type inference (you know, the one it got in 3.0) wipes the floor with that cute diamond syntax thingie. Sorry for the trollish language, but you know I have a point...

Re:One day we will be done with java...

[nstlgc]

C# had it 10 years ago.

Re:One day we will be done with java...

[prionic6]

I totally agree. Also, it's not about the noobs. I suspect most experienced java programmers cant' code the correct try/catch/finally/try/catch for a resource access without looking it up. Check http://stackoverflow.com/questions/4092914/java-try-catch-finally-best-practices-while-acquiring-closing-resources

Re:One day we will be done with java...

[DrXym]

I mean if that doesn't say it all I don't know what does. Hmm Allocate a resource, Free a resource. I think they still teach that in CS-101, then again maybe not. I alloc() therefor I free() ?".

Maybe they do. Doesn't mean it's not a pain in the arse to get right ESPECIALLY in Java since a close() can throw an IOException and ESPECIALLY if you have more than one resource open, e.g. input & output file and you need to ensure both get closed in all normal and extraordinary circumstances.

Re:One day we will be done with java...

[rpopescu]

Yeah, and C++ had it since before Gosling decided C++ wasn't good enough for him.
Ever since its inception, Java has steadily acquired lame, non-generic, basically hacks of implementations for features in C++ which it strived so hard to shun. Mainly due to Gosling being not smart enough to really understand C++ in the first place. Honestly, read some interviews with him, he's just guts and bile about it, no logical arguments whatsoever, typical I-don't-get-it-therefore-it's-wrong, holier than thou attitude.
The tasteless, confused hamburger that Java is today is the result of its small minded creator and the barriers built in since the beginning. Doug Lea's work turned the crapfest Java was into a workable platform for serious applications, but that's about it.

Re:One day we will be done with java...

[serviscope_minor]

Thanks for the object lesson dick.

You thank him for the lesson which is strange since you seemed to misunderstand it.

1. Raii gives you the -ability- to reclaim resources after a fault,

No, it automatically reclaims them. E.g.:

  osfstream f("tile.txt");
  throw "An error!";

now f is automatically flushed, closed and reclaimed.

2. If you mean writing a hell of a lot of useless boiler plate and trouble laden code

Well no, not really. In this case, the C++ version is shorter and therefore less error prone.

Re:One day we will be done with java...

[dshk]

osfstream f("tile.txt");
throw "An error!";

That is great (really), but it does not support inheritance. The declared type must be the same as the actual type, which would render a similar construct in Java useless most of the time.

Re:One day we will be done with java...

[LizardKing]

Cool! Can I use this C# language to create desktop apps that run without modification on Linux, Mac OS X and Windows? Is there a cross platform IDE for this C# language that allows me to develop in the same IDE on Linux as my colleagues do in Windows or OS X?

Re:One day we will be done with java...

[Mongoose Disciple]

Cool! Can I use this C# language to create desktop apps that run without modification on Linux, Mac OS X and Windows?

No, but in practice Java never really lived up to that promise either, except for very trivial applications.

"Write once, run anywhere" was like communism -- an idea that sounds nice in theory in some ways but utterly fails to work in reality.

Re:One day we will be done with java...

[LizardKing]

The try-with-resources handles all this for you. declare both resources in the try (...). The auto-closing will be applied to all the resources you specify, and in the event of an exception being thrown in your try block, then any exception thrown by the closing of the resources will be ignored (although there is a means to access them if you so wish).

Re:One day we will be done with java...

[BotnetZombie]

"Write once, run anywhere" was like communism -- an idea that sounds nice in theory in some ways but utterly fails to work in reality.

True, if you hardcode C:\something or /somethingelse in your app. I've never had cross-platform problems, either on big server side applications or trivial desktop ones. So I guess 'utterly failes to work in reality' is somewhat dependent on the developer.

Re:One day we will be done with java...

[LizardKing]

No, but in practice Java never really lived up to that promise either, except for very trivial applications.

Bollocks. I've worked on at least three non-trivial systems that are written in Java and run on at least two platforms (Linux and Windows) without modification. The first is a warehouse management system for a multi-national publishing company, the second is the front end to a repo trading platform used by a dozen Wall St or City of London based banks and the last is a large suite of applications for a government organisation. The only way it can "fail to work in reality" is if you deliberately use classes you shouldn't (eg. those in the sun.com hierarchy) or ignore the few areas where you have to use the - well documented - portability features of the class library (an example is using File.separator when manually constructing filesystem paths).

Re:One day we will be done with java...

[GooberToo]

Its funny that Python has had this licked for some time now. In fact, they have an entire interface to allow for clean resource acquisition and release of any object and even added a statement to compliment.

Python's combination of, "with/as", context management, and, "try/except/else/finally", make error handling and recovery for even complex use cases fairly easy and extremely powerful.

Re:One day we will be done with java...

[benjymouse]

Cool! Can I use this C# language to create desktop apps that run without modification on Linux, Mac OS X and Windows?

yes: http://www.mono-project.com/Main_Page.

You have a choice between Windows Forms or GTK as the widget toolkit. Both are supported on X11, Win32, and OSX.

Is there a cross platform IDE for this C# language that allows me to develop in the same IDE on Linux as my colleagues do in Windows or OS X?

yes: http://monodevelop.com/

Re:One day we will be done with java...

[EdgeCreeper]

And of course, don't forget how try-with-resources fixes common bugs where an exception in closeFile gets swallowed, or overrides the original exception...

This is what I do these days to avoid these problems:

Exception exception = null;
FileInputStream input = null;
 
try
{
  input = new FileInputStream("example.txt");
// Reading and processing of file content goes here
}
catch (Exception e)
{
  e.initCause(exception);
  exception = e;
}
finally
{
  try
  {
    if (input != null)
      input.close;
  }
  catch (Exception e)
  {
    e.initCause(exception);
    exception = e;
  }
// For other statements in the finally clause the same thing can be repeated
}
 
// Throw exception if one has been thrown
if (exception != null)
  throw exception;
 
// Return value from method

Handling exceptions this way has the advantage that I can see exactly what has happened even if statements in the finally clause throw an exception after another exception has been thrown. It also doesn't matter if many exceptions get thrown in the finally clause, they are all recorded in the stack trace. That is just the basics, helper classes can be created to make this even easier to write with fewer lines of code. Some exceptions may need to be caught and wrapped in another exception. For instance, SQLException has the SQLState and vendorCode properties which do not print in the stack trace. This means that another exception needs to be created to wrap SQLException and put these properties in its detail message.

Re:One day we will be done with java...

[leighklotz]

C# had it 10 years ago.

Lisp had it 30 years ago. Go suck eggs.

Re:One day we will be done with java...

[EdgeCreeper]

I would just like to post a link to my other comment which shows the way I handle exceptions. I believe this is superior because I can see every exception that gets thrown in the one stack trace, and that all the exception logging can be handled in one area of the program. It has worked very well for me.

Re:One day we will be done with java...

[serviscope_minor]

That is great (really), but it does not support inheritance.

Huh?

If you want inheritence, you have to do it with pointers.

auto_ptr p(get_from_factory());
throw "An error!\n";

Is that what you meant? It still works...

Re:One day we will be done with java...

[http]

You never owned a mac, right? PowerPC, not Intel. All kinds of fun with not working, on MacOS, OS X, and GNU/Linux.
Pardon me for remembering more than the last decade of my life.

Re:One day we will be done with java...

[shutdown -p now]

its compiler type inference (you know, the one it got in 3.0) wipes the floor with that cute diamond syntax thingie.

For the most part this is true, but C# "var" is only usable for local variables, whereas Java diamond inference can also be used with fields.

Re:One day we will be done with java...

[FlyingGuy]

I guess you think it stylish to use profanity, but since you are posting as AC I suppose you can get away with that.

Advancements in given programming language are great, advancements that encourage both laziness and a lack of attention to detail are worthless.

Is this what we have come to? Writing languages where programmer laziness and lack of attention to detail is heralded as the next great thing?

Someone mentioned programmers saying "High Level Languages" replacing assembler is bad? No that is not bad, it is a better means of programming when absolute metal level control is not required.

NO STATEMENT I MADE even attempted to assign any attribute to myself resembling anything like or even alluding to perfection.

Was it a true error of units that sent a billion dollar spacecraft into the surface of mars or was it someone who replied on the framework or the RTL working all that out for them? Could one ascribe that oversight as a lack of attention to detail? I think so, but that is just my opinion for whatever someone else things its worth.

It wasn't as if moving from assembler to C required less attention to detail, it simply made writing the code easier to understand 6 months later and took care of the really really love level things for you.

I have found many many bugs in my own code where I forgot to close a file before exiting and have lost data because the files contents were not flushed to disk and then properly closed and I found those bugs and fixed them before the code went out my door.

How much more will we push Moore's Law by adding yet more and more and more code to do things we as programmers should just remember to do? At what point will it take a machine with two quad core processors and 12 gigs of ram to run a simple program? Is there no limit to the lengths that we will go to take up the slack for basic laziness and lack of attention to detail so that some slack jaw can write code that will work to say nothing of having excellent performance?

Vernon D. Buerg (rip) wrote fast tiny programs that did big jobs and he did it elegantly. I shudder to think what kind of monster it would take to duplicate even LIST in Java.

M point is this. Programming takes attention to detail, it takes concentration, it takes keeping track of what you use and giving it back when you are done with it, not just skipping on to the next thing and saying "The RTL will take care of that, no need to waist my time on doing things like that.".

And yeah I have been around for a long time and I can tell by some of the low ID's replying that some of you have been around for a while as well and could see where you want to forget as many of the details as you can because of deadlines and this that or the other. Yet at the same time I see those same low ID numbers bitch and moan about bad code, programs that just blow up when you least expect it. When you bitch about that look in the mirror and tell yourself that you asked for it because you did when you advocate for things that are just automatic because really when you think about it there is not much in this world that works well 100% of the time automatically.

Re:One day we will be done with java...

[FlyingGuy]

If programming were easy everyone could do it. Well it is... Sorta... and everyone can sorta do it they all just can't do it correctly and well.

Yup dealing with those is a PITA but you knew the job was dangerous when you took it aye?

For years I have used the same bit of code to open and close files, streams, etc. One function to open one function to close and they have yet to fail me. The logic for opening is pretty simple, if you can't open it you report back and in certain very specific instances you have to bail out with a meaningful error message. Closing is pretty straight forward as well. If you cant release a resource ( close a file or what not ) then something is pretty drastically wrong and again time to bail out meaningful error message instead of a couple hundred lines of java stack trace which is practically meaningless to the end user.

Re:One day we will be done with java...

[TheTurtlesMoves]

I wish i could use lisp for my day job. Unfortunately I can't.

Re:One day we will be done with java...

[LizardKing]

Have you tried using Mono on Mac OS X? I have, and it's alpha quality. Also, Windows Forms has been superseded by WPF - which is far less painful to use than Forms - but isn't supported by Mono.

Re:One day we will be done with java...

[DrXym]

It's not a case of "if programming was easy...". Programming is already hard enough without a language throwing spanners at your head all the time. Java is a good language but it has some well publicized annoyances, long winded syntax and pitfalls. Anything that reduces bloat & boiler plate and reduces causes of bugs is a good thing. The problem is that Java the language isn't developing fast enough and Sun / Oracle have been loathe in many instances to implement things as best they could, e.g. generics.

Re:One day we will be done with java...

[Crag]

Preventing mistakes is nice, but the best reason to delegate resource control is code clarity. Allocating and freeing resources is something that has to be done all the time, like moving data in and out of registers in a CPU. We didn't move from ASM to C just to save us from mistakes in register allocation. We did it to save us from tedium and allow us to focus on new problems once we'd figured out how to generalize the old ones enough to hand them off to compilers. Memory and handle allocation is a solved problem. There are multiple competing solutions (reference counting, mark and sweep, etc), but it doesn't matter much which one your compiler/library/interpreter uses because unless you're writing a compiler/library/interpreter, that's not what your project is about.

So yes, humans are fallible, but taking control out of their hands is not the greatest benefit of higher level languages. The greatest benefit is increases in expressiveness.

Java is Great

[Anonymous Coward]

Java is great. The new release proves that Sun lives on inside Oracle.

The new version is a little faster from what I can tell especially file IO as a few have stated. It did even matter that much people just wanted to see that Java was still alive and it is.

Re:Java is Great

[Anonymous Coward]

You forgot "once upon a time" and "they all lived happily ever after."

Improvements

[FirefallPro]

Does this mean Java got any faster or a better UI toolkit?

Re:Improvements

[slack_justyb]

Arguments for slow Java are so 1990's. Every Java application, desktop or otherwise, I have written has been very snappy, very responsive. Swing has always had places where you can get caught making your own application slow to load or slow to respond. I believe that the community and Sun have really ushered in conventions to mitigate that. SwingWorker (part of core Java Swing), Timing Framework [java.net], JPA (especially our friends at Eclipse), and other community frameworks have really changed the way coders write Java desktop applications in ways that avoid a lot of the pitfalls that came with the 1.1, 1.2 and so on versions of Java.

I think this is the reason why Oracle really needs to embrace the community. It has been because of them that Java has gotten better and faster with each release. People who still talk about how slow Java is and how crappy Swing is, are still living in the past. Is it the perfect platform? No, but it has gotten multiple times better than where it was.

Re:Improvements

[Anonymous Coward]

Wait, you're using the monster known as Eclipse as an example of speed or UI improvements? Is GIMP a 1990's relic than? Most people aren't using Java software in their user facing day to day lives (Andriod comes close if you could even call it Java still). I could lay claim that some simple VB app was fast, but that hardly applies to comprehensive and cohesive applications.

Re:Improvements

[Joce640k]

Arguments for slow Java are so 1990's.

Nope, still as relevant as ever. Java simply doesn't scale. Try running your microbenchmarks with a million objects in memory...

Re:Improvements

[Lisandro]

To be fair here compared to other interpreted languages Java is still the king of the hill. By far.

Disclaimer: Yes, interpreted. Bytecode is interpreted, even with stuff like JIT.

Re:Improvements

[Anonymous Coward]

Wait, you're using the monster known as Eclipse as an example of speed or UI improvements?

His point was even more misguided than you're making it out to be. He wasn't mentioning Eclipse, he was mentioning JPA. One of the main implementations of JPA is called Eclipselink and is maintained as an Eclipse-hosted project. But the bulk of the development work for it was done by Oracle when it was called Toplink. Still, it has little to nothing to do with desktop application development since it's an ORM solution for interfacing with a relational database.

However he could have mentioned SWT as an example of how Java desktop applications can be fast. SWT is not the reason Eclipse is slow. Eclipse is slow because of the component architecture and the fact that basically the entire app is OSGi bundles. Applications that use SWT outside of the Eclipse RCP framework can definitely be fast. It does this by basically delegating everything to native code that uses the actual widget toolkits on each platform. So, unlike Swing, SWT apps are actually native Win32 widgets in Windows, Cocoa widgets on a Mac and GTK widgets in Linux. There's very little overhead.

Re:Improvements

[slack_justyb]

Java simply doesn't scale. Try running your microbenchmarks with a million objects in memory...

That sounds like EE development and not SE development. If that is the case:
That sounds like a problem with the design. Try using more lock free structures, you can use the java.util.concurrent package to find tools that will help you build these easier in Java 5 and better.

If your are indeed talking SE development, why is your desktop application using millions of objects in memory? I do not think it is wise to juggle that many objects in any desktop platform. Usually, and this is just me, I flush objects out of memory and to disk, network host, database file, or something other than memory once I hit over more than I could keep in my head. Pagination designs help smooth this out for users and using task workers keeps everything moving smoothly. For the curious the pagination design pattern in Java SE looks exactly the same using the QT toolkit (if you use that toolkit.)

I don't know your situation and I won't pretend that I do, but in most cases I find it is the developer just assumed Java would do this or they are still following an old convention that doesn't work well with today's JVM. Either way, EE or SE, if you are dealing with millions of objects in memory, there are ways of moving that data around to keep space on the stack for responsiveness in your application. Just having a million objects in memory just because is not a good idea.

Just curious what use case do you have that requires you to have that many objects in system memory at once? Are we talking simple objects or pretty complex ones?

Re:Improvements

[slack_justyb]

Disclaimer: Yes, interpreted. Bytecode is interpreted, even with stuff like JIT.

Um, no, it is not. There really isn't much to debate here. This is like debating if JIT is the same thing as a compiler.

Re:Improvements

[Lisandro]

Bytecode IS interpreted (by the JVM), sorry. Jazelle was the only attempt of a hardware JVM implementation that i know of and even that was short lived.

Re:Improvements

[Anonymous Coward]

Go find some hardware from the '90s and tell me modern Java has gotten better. In my experience most of Java's performance improvements have had more to do with advances in hardware. Java then was ahead of what hardware could do by some years and now it's seems to be playing catching up with its "better multicore and parallelism support." (Not that other languages are doing great in the multicore department, but Java doesn't seem any farther along.)

Re:Improvements

[SomeStupidNickName12]

Haha, if java doesn't scale why is it the defact standard for any large enterprise?

Probably not the best language to write a ray tracer or an on the fly 3D engine but the stuff I seen java do is pretty impressive. Go take a look at throughput of something like Websphere MQ.

Re:Improvements

[slack_justyb]

Let's look at the fundamental differences here:

Interpreted code does the following: Bytecode is loaded by a native program into an Interpreter. The Interpreter reads the code and sends native code to the machine or to another piece of software that can do such.

JIT code does the following: Bytecode is loaded by a native program into a compiler. The bytecode is compiled into native code. The native code is sent to the machine.

The difference is the following, the bytecode in JIT eventually becomes the native code. Interpreted bytecode never makes it as native code. Both can be optimized by saving the bits of machine code that get generated, however JIT usually means that the native code follows closely what the original bytecode looked like. Interpreted usually has to make assumptions on how execution should happen and in what order.

Re:Improvements

[bertok]

The problem with Java is that the startup time is poor, which is often ignored by benchmarks.

First, for an apples-to-apples comparison, this is the startup of a typical installed .NET app:

* Operating system loads the cached, fully compiled EXE or DLL.
* Operating system loads the cached, fully compiled System library DLLs.

If the app is not cacheable (not signed, not properly installed, or whatever), then the process is almost the same, except that the first step changes to "Operating system loads the bytecode, and compiles it one method at a time on demand and runs it". All of the system libraries are always fully pre-compiled. No code ever runs in an interpreter.

Compare to Java:

* Decompress Application JAR files (this is a ZIP file internally) -- this is slow. At best, you get 30MB/sec for typical compression ratios.
* Decompress Java system JAR files -- this is also slow, and there's a lot of it to load. At this point, anyone without an SSD gets to twiddle their thumbs while the disk makes crunching sounds for a while.
* Start running application (including the system libraries) using an interpreter -- this is several times slower than compiler code.
* At some point, some of the code (usually not all of it) is compiled -- now your app is probably fast.

Even for server apps, this is bad. I've seen a large J2EE app thrash a server (100% CPU!) for tens of minutes before it settled down. Compare that to, say, ASP.NET, which if precompiled can launch in a few hundred milliseconds!

Sure, in long running benchmarks, Java is faster, but the user experience is less than stellar.

There's no good reason for this. Oracle could use a container format that's uncompressed by default, pre-compile, cache, etc... but they don't. I know there's third-party JVMs that do that kind of thing, but the majority of users stick to the "official" JVM.

There's also still this attitude of having "User" vs "Server" JVMs, as if people still had single-core PCs. My laptop has 8 logical 64-bit CPUs!

Re:Improvements

[slack_justyb]

n my experience most of Java's performance improvements have had more to do with advances in hardware.

I can tell you that all compilers have advanced in step with hardware improvements. Also, I have easily ran Tomcat 6 and Linux on a Dell OptiPlex GX300. Trust me I have tons of 90's hardware that I am required to make work and enjoy hacking on. I still change DIP switches on ISA cards at my work place.

Re:Improvements

[Lisandro]

The difference is in the how. JIT gives huge improvements in stuff like loops and basic constructs because these are easily translated into machine code. But for Java bytecodes dealing with OOP constructs (new, for example) this basically means that the JIT has to embed a lot of machine code as an abstraction layer. The improvements there are minimal because this code is doing pretty much the same the JVM would do processing that bytecode on the fly.

Making a very loose comparison, i could easily bundle a JVM implementation and Java bytecode into an .EXE and call that "compiling". In fact, there's software that does exactly this. Quick Basic did it too back in the DOS days.

JIT is great, but it is not a compiling by any stretch. Is a hybrid approach that works pretty well, but every time you fire up your Java code the JVM will process it for you, interpret it and translate it, when possible, to native machine code on the fly. In fact, for big files this process can add a significant start up time penalty.

Re:Improvements

[m50d]

What are the prominent desktop applications written in Java? I'd say Azureus, Eclipse, and OpenOffice (and personally I'm using JDownloader, but that's a bit obscure) - all of which are dog slow (heck, every one needs a splash screen when starting). So you can't really blame people, for whom these applications are their only experience of Java, for perceiving Java as slow.

Re:Improvements

[phantomfive]

Once Java is launched, you are right. I have a Java program I use on a regular basis, and it is a fine program, which is why I use it, but I hate to launch that thing because it takes forever. Makes me want to rewrite it.

My biggest problem with Java isn't the language, which I have grown to respect, it's the Java programmers. They think they are using Java so they don't have to worry about memory, that things can't leak. No, you still can stick an object in a queue and forget about it. Or register a Swing listener and need to clean it up. If you aren't thinking about the lifecycle of resources, even in the back of your mind, you're probably leaking them all over the place.

Re:Improvements

[Post-O-Matron]

Java simply doesn't scale. Try running your microbenchmarks with a million objects in memory...

Can you give an example of a managed, cross-platform, enterprise language for which the above statement is incorrect?

Re:Improvements

[slack_justyb]

The problem with Java is that the startup time is poor, which is often ignored by benchmarks.

I can understand this poorly written application usually have very long start up times. Usually if you need to yank in a ton of stuff you can do that at runtime in the background. Dynamic loading.

Compare that to, say, ASP.NET, which if precompiled can launch in a few hundred milliseconds!

You can precompile EE applications as well and have them start up in milliseconds. I think the PHP guys are the ones who came up with this in the first place but then of course I am sure that at some point Xerox came up with the idea first.

There's no good reason for this. Oracle could use a container format that's uncompressed by default, pre-compile, cache, etc...

As far as EE goes you are not required to use WAR or whatever they are called. In SE that is being addressed in Java 8, but you can already do some of it with dynamic loading. .NET is snazzy in the fact that the VM is loaded with the OS so you only incur the cost at startup and shutdown. Maybe that's why it seems to take ten minutes to turn off a Windows machine.

There's also still this attitude of having "User" vs "Server" JVMs

So does .NET, except it's not a switch away. Do you think they use the same .NET VM in Windows Server as they do in Windows Home whatever?

Re:Improvements

[slack_justyb]

One could say the exact same thing about VTables in C++, lookup pointers in C or RT-Code in Objective-C. Which bring me back to my point we could debate this at about the same rate we could debate compiler vs JIT. Machines are state based, OOP is artificial no matter the platform, a CPU is not made to natively understand the concept of an object be it C++, C#, VB, or Java.

At some point a machine will not natively do everything a language requires and thus extra "fluff" will need to be added. That's why Interpreted vs JIT is defined as who sends the executed code to the machine and when, not what is executed or how it goes about it. C++ compilers add machine code abstraction layers for all kinds of stuff like virtual pointers and polymorphism, does this suddenly classify every C++ compiler as JIT?

Re:Improvements

[Lisandro]

No. C++ generates binary machine code. It is not portable. It is loaded directly into memory where it is executed directly by the CPU. There's no "just in time" there, at all.

Re:Improvements

[Waccoon]

Is that why Java installs so many "Quick Starters" as background processes and plug-ins in every nook and cranny it can?

Re:Improvements

[Jmc23]

Maybe king of the popularity hill. A lot of us still think that lisp is the king of elegance, and look, wow, java got some more lisp features.

Re:Improvements

[Lisandro]

I was referring to speed alone, where Java runs circles around Lisp. But yes, if we're talking elegance Lisp makes Java look like Flavor Flav.

Re:Improvements

[sgt101]

If I was doing this I would use an in memory database. I would talk to that database using Java.

I developed in C++ for 5 years, I have thanked Jesus and his angels every day since Java came to save me.

Re:Improvements

[m50d]

Haha, if java doesn't scale why is it the defact standard for any large enterprise?

Because 10 years ago it was the best tool for the job.

Re:Improvements

[SomeStupidNickName12]

Its still the best tool for the job, I agree that something like C++ has better scalability from a pure language perspective but java far more scalable from an environmental perspective.

There is no such things as a clustered app server in the C++ world, MQ servers that can push through millions of message a day within the bounds of a full XA transaction.You either build them yourself which would take years or you use Java.

And part from the 3 possible contenders to the enterprise crown (C++, java, .NET) nothing else even comes close.

Re:Improvements

[Rockoon]

So does .NET, except it's not a switch away. Do you think they use the same .NET VM in Windows Server as they do in Windows Home whatever?

I dont know what he thinks, but you are quite clear about what you think and its wrong. The CLR is the same between Server and Home versions of windows. There simply is not differing branches of the CLR because that would defeat its purpose.

Re:Improvements

[DrXym]

Java's UI is perfectly acceptable for a range of trivial and complex applications. The fact that tools like Netbeans use it should demonstrate that it is no impediment. And if you absolutely need faster performance, or a more native appearance (though Swing is close enough) then SWT could provide that too. Eclipse is built in SWT and is probably the most complex application from a UI standpoint that anyone is ever likely to see.

A bigger issue for Java is that it uses layout models extensively to ensure GUIs cope with differences in metrics, fonts etc. from one platform to the next. It can be a huge pain in the arse to program layout models. There are GUI editors (e.g. Window Builder, or Netbeans) and relative / group layouts but these editors never work 100% properly. Android inherits this same problem too but at least it's declarative. Java could really do with a standard declarative way to define layouts.

Re:Improvements

[DrXym]

Even Eclipse is fast unless you weigh it down with plugins. J2SE or J2EE Eclipse with a couple of plugins (e.g. Maven & source control) works perfectly well. IBM's WSAD (Eclipse + a massive amount of crap for websphere / rational / kitchen sink development)... not so much.

Re:Improvements

[Rockoon]

What you are saying is correct.

The problem is that you didnt understand anything he said, so when you thought that saying what you did was relevant, you were being a complete fucking idiot.

You are living proof that a little knowledge is a dangerous thing.

Re:Improvements

[DrXym]

Because 10 years ago it was the best tool for the job.

It's still the best tool for the job. And it scales extremely well assuming you bother to write apps correctly to cope with the dataload.

Re:Improvements

[bertok]

I can understand this poorly written application usually have very long start up times.

Nothing to do with code quality, unless you consider "using the standard libraries" poor programming practice!

You can precompile EE applications as well and have them start up in milliseconds.

Maybe, with some containers. I said that. My point is that 90% of Java environments don't or can't do this. It's certainly not the default.

In SE that is being addressed in Java 8

That's my point! Java 7, which is now 16 years old, still doesn't have minor, unimportant features like... fast start time, even though, as you put it, other people have solved the problem decades ago.

Dot NET is snazzy in the fact that the VM is loaded with the OS so you only incur the cost at startup and shutdown

Not true! The VM is only loaded if an application needs it. The operating system doesn't -- Windows XP and 2003 certainly don't, and even newer versions usually don't load it. Heck, Server 2008 R2 doesn't even fully install it by default for security.

It's also another difference between .NET and Java -- automatic sharing of DLLs between running processes. On Citrix or Terminal Servers, this makes a massive difference to resource usage. Java reloads and recompiles everything for every user! On a 100 user server, that's about 50x the overhead of a comparable .NET app.

Do you think they use the same .NET VM in Windows Server

It's the same install package and binaries, but there are some small differences, like the default GC mode. You can override it if needed with a configuration entry. Not that I've ever seen anyone having to do this, because the defaults are fine, unlike the Java workstation VM, which is too slow to use for some workstation GUI apps! One of my tricks is to switch to a 64-bit server JVM to run IDEs because the speed boost is quite noticeable.

Re:Improvements

[Xest]

Meh, not sure what you're used to but Eclipse is always slow, no matter how few plugins you use.

I don't disagree with the original comments- that Java being slow is a 90s argument, but Eclipse is a particularly poorly written piece of software that really doesn't demonstrate Java very well.

The GP pointed out why Eclipse is slow though, and why it's not a Java issue, but a poor design issue.

Compare Eclipse to other IDEs like NetBeans, JDeveloper, or Visual Studio and you can see how much of a joke it is. It's not even just initial boot up, even intellisense in it is too slow to be of much use a lot of the time really.

Re:Improvements

[silentcoder]

> I still change DIP switches on ISA cards at my work place.

Sheez, who do you work for ? The museum of retrocomputing ?

Re:Improvements

[silentcoder]

>To be fair here compared to other interpreted languages Java is still the king of the hill. By far.

By what measurement ? Both python and ruby can outperform it in at least some situations, both are more advanced and powerful languages with better features and faster development cycles.

Or do you mean back-office market share ? I'll grant you that one...

Re:Improvements

[Anonymous Coward]

OpenOffice is not a java app.

The java part is just here for macros and unecessary stuff.
The rest is coded in plain old C++

Re:Improvements

[MichaelSmith]

I don't find eclipse to be especially slow but it does everything it can to make software written under eclipse difficult to run outside eclipse. For example eclipse runs class files directly while deployments use jar files. Eclipse has its own classpath file format which is of no use in the outside world.

Re:Improvements

[m50d]

I know that. But IIRC it announces in the splash screen that it's using Java, and so it's still one of the things I think of when I'm trying to think of "java desktop app". Seriously, if it's possible to write a snappy, performant desktop app in Java, why can't I think of any?

Re:Improvements

[MichaelSmith]

assuming you bother to write apps correctly.

Thats quite some assumption you have there. The problem with java IMHO is that it gives the bright young things a lot of fun toys to play with and opportunities to create write only source code.

Re:Improvements

[MichaelSmith]

I still change DIP switches on ISA cards at my work place.

Hey I had to attack the backplane of a PDP 11/84 to install a SCSI card.

Re:Improvements

[DrXym]

I'm quick enough to rant when I hate something. Eclipse has its faults but performance is perfectly tolerable for me. I'm using it on a fairly crappy dual core box right now on a 30,000 file project and it works fine except when I fire up a couple of instances and physical memory has depleted. It's badly behaved plugins which hog memory or hook into much stuff that hurt performance. If you restrict yourself to the version of Eclipse that meets your needs you should be okay.

I'd add that Eclipse and Netbeans aren't really that different at the low level. Both implement RCPs over modular frameworks. Eclipse uses OSGi, Netbeans has it's own framework with an OSGi bridge.

Re:Improvements

[DrXym]

Thats quite some assumption you have there. The problem with java IMHO is that it gives the bright young things a lot of fun toys to play with and opportunities to create write only source code.

No, it's not an assumption, it's a requirement. If the requirement says "must scale", then you design and write your app to scale, depending on what that means in the circumstances. In many cases it just means being able to run extra instances of something in a cooperative fashion and externalizing settings for performance tweaking. In others it means using a scaling app server like Gigaspaces. I'm quite sure you can abuse Java in all sorts of perverse ways if you don't know what you're doing, but that isn't the point.

Re:Improvements

[angel'o'sphere]

What do yu mean with Java does not scale ?

Do you even knwo what scale in IT means? It certaily has nothing to do with millions of objects in memory ...

You do know that many larg scale internet companies run their business on JVMs? (Not necessaryly on Java, but Scala or other languages)

You don't tackle slowness or speed in general by the language or platform but with architecture and design.

A straight forward written C++ program hardly will outperform a well thought out Java solution. Ephasizies on "straight forward" and "well thought out"!

Re:Improvements

[angel'o'sphere]

To be fair here compared to other interpreted languages Java is still the king of the hill. By far.

Disclaimer: Yes, interpreted. Bytecode is interpreted, even with stuff like JIT.

Nitpicking: in an interpreted language the language is interpreted. Java is not and never was an interpreted language. Its bytecode is interpreted, so: the bytecode is an interpreted language.
In a truely interpreted language (today we don't have many anymore as nearly everyone makes a small compile pass and creates some intermediate code) the programm is basically executed/interpreted line by line. That means the interpreter will stop with an error as soon as it finds something it can not interpret. So it is possible that programs only run half:

10 PRINT "hello World"
20 GARBAGE
30 GOTO 10

In this example line 10 is "interpreted" and that means executed, but line 30 is never reached. Java on the other hand is compiled and an error like line 20 would be discovered during the compile phase.

Re:Improvements

[stdarg]

Shouldn't the implementation be in question, not the language as a whole? Javascript is usually interpreted, but I'm sure someone has written a Javascript compiler that emits executable machine code.

Re:Improvements

[Lisandro]

I was *almost* tempted to ask you to enlighten me there. Nice job! Now doze the fuck off please.

Re:Improvements

[Lisandro]

I don't think there's a single language today out there that isn't compiled to bytecode prior to execution on a VM. Even Perl does it AFAIK. The code is still being interpteted, just not from the text sourcecode directly.

Re:Improvements

[Mongoose Disciple]

Even Eclipse is fast unless you weigh it down with plugins.

The problem with that statement is: basically everyone who uses Eclipse seriously also uses a lot of plug-ins to provide all the functionality Eclipse doesn't out of the box.

In my career I've known over a hundred developers who used Eclipse as their major development tool, and not a one of them used less than three or four plug-ins with it.

Saying Eclipse doesn't run like a dog if you don't add plug-ins is like saying your car gets great gas mileage if you take the seats out and don't weigh it down with passengers or cargo: technically true and yet totally useless from a practical perspective.

Re:Improvements

[Anonymous Coward]

Try running your microbenchmarks with a million objects in memory...

I think you misunderstand the concept of scaling.

Scaling is what you do when you have a million * trillion objects. When you can no longer fit EVERYTHING into a single computer even if it is the "largest" computer you can buy.

Some systems might be faster and far superior when you can fit everything into one or a handful of computers. But they stop working well when you need to distribute everything over a hundred thousand computers or more.

Re:Improvements

[Anonymous Coward]

C++ can be JIT'ed.

http://root.cern.ch/drupal/content/cling

Re:Improvements

[LizardKing]

I agree that something like C++ has better scalability from a pure language perspective but java far more scalable from an environmental perspective.

Threading and locking are far easier to implement in Java rather than C++, as they're built into the language and libraries. The concurrent add ons that came with Java 1.5 improved things as well.

Re:Improvements

[GooberToo]

(Andriod comes close if you could even call it Java still).

We don't. Its not.

Android's use of Java and UI's have absolutely nothing to do with the topic at hand. Your reference is neither applicable or relevant.

Re:Improvements

[Lisandro]

I love Python, don't get me wrong, but it is nowhere near Java regarding raw performance. Even the developers acknowledge this, with stuff like the Google sponsored Unladen swallow and PyPy.

Haven't toyed much with Ruby these days though. I should :)

Re:Improvements

[silentcoder]

>I love Python, don't get me wrong, but it is nowhere near Java regarding raw performance.

I did say in SOME situations, in most cases you are right. Ruby - particularly the RoR setup beats it hand's down though, and I honestly do believe that zope holds up well against glassfish in all but the most strenuous environments.

Re:Improvements

[sproketboy]

sigh - so 1990's.

http://www.brackeen.com/javagamebook/

Grab chapter 12 and build it. It's a 3D game using only the Java 2D APIs. Not OpenGL, No DirectX. It's under 200k JARed with the resources.

Re:Improvements

[Hatta]

Arguments for slow Java are so 1990's. Every Java application, desktop or otherwise, I have written has been very snappy, very responsive.

Where do I find some of this snappy java?

Re:Improvements

[BotnetZombie]

Both python and ruby can outperform it in at least some situations

[Citation Needed]

Re:Improvements

[silentcoder]

First example that comes to mind: a command-line only program, unix style with a lot of standard libraries pulled in. Both python and ruby would be faster there since execution time is a minimal aspect of the running time of the program - java's slower startup time would be a much larger percentage of the total run-time and the java program would thus perform slower over-all.

Hell.. a BASH script would outperform java in this scenario.

I never said in all cases or for all jobs - I said SOME scenarios. This is an example of such a scenario - and such programs are a very large subset of the software in the world.
The unix approach to design of building lots of small tools that can interoperate and do complex tasks by being plugged together differently is almost impossible to achieve in java development because startup times on individual programs is so much higher. It works well with native code, the difference with languages like python, ruby and even bash is so small that users never even notice.

I'll tell you this though - if you replicated the standard unix user-space in java it would be an absolute and unusable nightmare to work with, the same clearly doesn't apply to bash or python since large parts of the contemporary unix userspace stack is ALREADY written in them. This is even true of the much older perl.

In short - there are use-cases where java performs worse than even wholy interpreted scripting languages, I've shown you own, that's enough.

Re:Improvements

[Jmc23]

,fter it's all beautiful an working properly you can throw in all your declarations to get performance on par or greater than C. I think most ppeople just don't learn that part, somethings still slower though. I'd rather the tradeoff of elegance with.the ability to get performance than having to write it ugly to begin with.Actually

Re:Improvements

[BotnetZombie]

I just did a small test on all three for the fun of it and you're right about the startup time. For a simple hello world on my machine, Ruby 1.9.2 takes on average ca 50 ms to execute, python 3.2 70 ms and Java 6 100 ms. That startup time difference is too small for user-detection and once the program starts doing anything the difference will be in the other direction.

Other things you talked about don't have anything to do with performance, so you haven't talked about use-cases in plural but only about the small amount of startup time difference.

Re:Improvements

[silentcoder]

Now take your python script and stick 100 include lines on top. The use 100 standard libraries in your Java app. No need to do anything. Just call them and compare the results. Java startup times increase exponentially the more libraries it calls. Python has no such issues. Bet its user noticeable now.

The Unix style of design is just as useful and powerfull in application development. Building a complex app out of lots of small specialized little apps makes your app much more powerful and scalable. If those little tools are executable program s then that itself is a feature. Users can plug them together in ways you could never have thought off or provided. That entire design philosophy and the myriad programs that use it is ruled out in Java. Even a 5% increase in startup times add up to an unacceptable load when normal operation will start hundreds of apps in unpredictable order. Especially if they can't share resources like Library memory or fully benefit from copy on write like.

  program

Re:Improvements

[Raenex]

Alternatively, why are bloated apps written in C++ just as slow to load?

Re:Improvements

[Raenex]

I did say in SOME situations

I've never heard of Ruby or Python outperforming Java, Rails included. Do you have a cite?

Re:Improvements

[shutdown -p now]

The point is that the only difference here is whether the compilation happens "ahead of time" or "just in time". End result is still the same.

Note that, in case of Java, the actual story is more complicated, since it also does have a true bytecode interpreter (as in, a loop that processes opcodes one by one and performs the corresponding operation), and switches from that to JIT only for "hot" methods. This is because JIT-compiling itself is not free, esp. if you do advanced optimizations, and for a method that's only called once or twice, you waste more time JIT-compiling than you gain from its faster execution.

Re:Improvements

[Chaos Incarnate]

There's not differing branches of the CLR proper, but there is a Client Profile version of the framework which omits some of the standard libraries.

Re:Improvements

[m50d]

The problem with java IMHO is that it gives the bright young things a lot of fun toys to play with and opportunities to create write only source code.

Exactly wrong. The big (in fact almost the only) thing java has going for it is that its strong typing and verbose, rigid syntax limit how clever you can be, and mean the structure of any piece of java code remains clear. You can do a much better job of write only source in either C++ (operator overloading, unmanaged memory) or dynamic languages (reuse the same variable for different types, play with all the funny-looking operators in the syntax).

Re:Improvements

[thsths]

> Arguments for slow Java are so 1990's.

Which is why it is such a shame that they are still true. In fact Java 1.0 would start in 3 seconds on my PC back then when it is up to date. Java 1.6 takes 10 seconds to start...

> Every Java application, desktop or otherwise, I have written has been very snappy, very responsive.

Once they are up and running that may be. But the start-up time is always terrible, and it seems to be getting worse with every new version of Java, even the ones that promise more speed.

Re:Improvements

[silentcoder]

I gave two examples in other posts replying to this one. Read more.

Re:Improvements

[Raenex]

You talked about command line apps, and that's only one example, unless you are talking about "particularly the RoR setup beats it hand's down though", which I find unbelievable unless you've got a cite.

As for the Unix command line, I'm willing to bet Java would do fine. Files are all cached in memory these days.

Re:Improvements

[silentcoder]

And if you think file access time has anything to do with java's slower startup times you are an idiot not worth debating with. File access is handled by the OS, whether the intermediary layer is a python interpreter or a JVM will make no difference to the time it takes too access files (the only thing affected by caching) - since neither does it (indeed neither CAN do it - it's a kernel-space activity).
The reasons why java slows down with library loads is completely unrelated to file caching - and has been clearly spelled out by other posters, it relates to how java loads the libraries into the JVM's memory base.

I also pointed out another problem - JVM's cannot share resources very efficiently with one another - notably two java apps that load the same library cannot gain full effect of copy-on-write. This means the library must be copied into memory TWICE, always. Both compiled and interpreted languages however do get copy-on-write and the library once loaded is already loaded for ALL programs that need access to it, only in the event that a program changes something in the library's own memory space does that chunk get copied into private memory and even then it's a memory-to-memory copy.

This is one reason why java is among the worst memory hogs around. I know it's become fashionable to treat ram as infinite and not part of performance but this is false - memory is always constrained - and java uses up more of it.
Even high-level enterprise systems have a limit of memory and it's often the first resource constraint reached. Long before CPU runs out even big iron servers are pushing RAM usage limits. I speak as somebody whose job i involves working on just that problem.

On a server with maxed out ram, I can show how 9/10 times 95% of the ram is tied up by the java portions of our stack - not the mod_perl or python parts (and this while java is the smallest part of the stack - even if you include glassfish as part of the java stack).

In any environment where the task of the applications require significant amounts of memory to be allocated, Java will perform worse than any other language because it will start swapping out first.

In benchmark tests where all things are optimal and all you measure is CPU times of execution and such - yes java outperforms python or RoR. In the REAL world where even 32 gigabytes of memory gets used up by big database apps during normal operation sometimes, java is frequently slower.
It's just a fact - first to swap out = last to finish.

Now I just hope I explained it in simple enough terms for somebody who thinks disk-caching has anything to do with why java has a slower start time than python apps. And even if it had you're wrong. File caching makes disk access more efficient, it sure as hell doesn't make it unimportant. At best it makes the files that are used the most accessed faster, it will never be so perfect that you can completely ignore seek times when building high-performance applications, and no programmer who does that for a living ever would.

Re:Improvements

[Raenex]

And if you think file access time has anything to do with java's slower startup times you are an idiot not worth debating with.

http://en.wikipedia.org/wiki/Java_performance#Startup_time

"It seems that much of the startup time is due to IO-bound operations rather than JVM initialization or class loading (the rt.jar class data file alone is 40 MB and the JVM must seek a lot of data in this huge file).[25] Some tests showed that although the new Split bytecode verification technique improved class loading by roughly 40%, it only translated to about 5% startup improvement for large programs.[58]

Albeit a small improvement it is more visible in small programs that perform a simple operation and then exit, because the Java platform data loading can represent many times the load of the actual program's operation.

Beginning with Java SE 6 Update 10, the Sun JRE comes with a Quick Starter that preloads class data at OS startup to get data from the disk cache rather than from the disk."

[25]: ""At the OS level, all of these megabytes have to be read from disk, which is a very slow operation. Actually, it's the seek time of the disk that's the killer; reading large files sequentially is relatively fast, but seeking the bits that we actually need is not. So even though we only need a small fraction of the data in these large files for any particular application, the fact that we're seeking all over within the files means that there is plenty of disk activity. "

Both compiled and interpreted languages however do get copy-on-write and the library once loaded is already loaded for ALL programs that need access to it, only in the event that a program changes something in the library's own memory space does that chunk get copied into private memory and even then it's a memory-to-memory copy.

You must be speaking of mod_perl in particular, because by default if you run two separate interpreters in two separate processes they will not share libraries unless they are native .so libraries.

And if it's a server you're talking about, then there's only one JVM anyways running multiple threads.

On a server with maxed out ram, I can show how 9/10 times 95% of the ram is tied up by the java portions of our stack - not the mod_perl or python parts (and this while java is the smallest part of the stack - even if you include glassfish as part of the java stack).

Java EE servers aren't designed to run as a small footprint because it takes an "everything and the kitchen sink" design. That said, if you are eating up all the ram on the server it's because of your app code, not Java.

At best it makes the files that are used the most accessed faster, it will never be so perfect that you can completely ignore seek times when building high-performance applications, and no programmer who does that for a living ever would.

Only if your "high performance application" entails starting up a new process every time that won't be in the cache.

Re:Improvements

[silentcoder]

You do realize that the cache is in MEMORY right ? The SAME memory where applications and data has to live ? So you realize that the first thing the OS does when memory use gets high is to shrink the cache ?
When the load on your apps from having ten-thousand concurrent connections each doing heavy-load transactions is pushing a 32Gb ram server to 95% memory use, for all matter of practice there IS no cache. This is why programmers who write the kind of software that has to perform under these kinds of loads and don't get the benefit of running on large clusters (and that is how it is in some fields) actually don't count on caching. In fact they base their performance metrics on worst-case-scenario (that would be zero cache and the highest possible seek and read times for the hardware types).
Since many of these servers also need 3-5 year uptimes hardware upgrades are infrequent and that means they are not reading from SSD's.

That's the real industry world - both my previous and current employer are in business that has to design around those kinds of constraints. In both cases java is very powerful and useful in many ways but it's the biggest single performance problem because these assumptions that other programmers can make don't apply in the world of high-vollume enterprise management systems.

So now I've given you TWO use-cases where java is not the optimal performing tool. That doesn't mean it's not powerful or useful, in both cases it gets used DESPITE that because the overall software stack is better with it than it would be without it and you can design around the performance issues, but make no mistake what I DO for a living is design server and OS platforms for high-vollume, heavy load applications to operate in. I know from daily experience what resources get used first, and I've done this on multiple stacks by different teams in different companies so I know that the problem exists across many types of applications.

You can argue theory as much as you want - I am telling you in the real world, it doesn't work that way. In the real world uptime requirements beat upgrade requirements EVERY TIME. Performance bottlenecks need to be dealt with and memory is ALWAYS the first to go and even when only 5% of the stack is written in java it's always chewing 85% or more of the memory.
None of this is meant to say java is bad, it's an excellent platform for many things - but to just blatantly assume that it will always outperform every other non-compiled language in every use-case is thoroughly naive.
I'm not talking from education, generic benchmarks or all-things-equal studies here. I am talking about what I get paid to find sollutions to in the real world every day for the past 5 years.

Making java not kill servers practically IS the job I get paid very handsomely for because it's a bloody hard job.

Re:Improvements

[Raenex]

You do realize that the cache is in MEMORY right ? The SAME memory where applications and data has to live ? So you realize that the first thing the OS does when memory use gets high is to shrink the cache ?
When the load on your apps from having ten-thousand concurrent connections each doing heavy-load transactions is pushing a 32Gb ram server to 95% memory use, for all matter of practice there IS no cache.

That's quite ridiculous. Nobody with a clue runs their server to 95% memory capacity, and even if they did, the cache required for a single JVM is going to be on the order of 100MB, not gigs.

And if you're talking 10,000 concurrent connections, startup time and caches are not the issue. This isn't a problem with Java, it's a problem with your app. You're not going to magically shrink the memory requirements where you are pushing the limits of 32 gigs by switching from Java to Perl.

but make no mistake what I DO for a living is design server and OS platforms for high-vollume, heavy load applications to operate in

So you say, but it doesn't mean you actually are an expert at it. Everything you've said so far leads me to believe the opposite.

Re:Improvements

[silentcoder]

>That's quite ridiculous. Nobody with a clue runs their server to 95% memory capacity, and even if they did, the cache required for a single JVM is going to be on the order of 100MB, not gigs.

Oh I agree, but if the customers want a system that can handle connections from 10000 users at a time - who am I to tell them they can't do it ? My job is to make sure it doesn't fall over, and since it never does - that's why I get called an expert.

>So you say, but it doesn't mean you actually are an expert at it. Everything you've said so far leads me to believe the opposite.

That's because your experience is obviously ... a bit more limited. When your customers are mostly the world's largest telcos - that's what you're dealing with. A server gets put down and is expected to stay stable even if it's pushed to 100% memory at times, and not upgraded for 3 to 5 years. That's the reality of the business. I don't like it, I would LOVE to agree with you - I don't get to say that.

At least in my new job those servers are running linux, the previous job had an overlapping customer base - but those servers were mostly running 10 year old versions of Unix, hell I actually had to maintain two original 30 year old DEC Alpha's - indeed being run to maximum capacity.
These people don't overbuy, if they need 8Gb of ram for a machine, they expect it to be using 8Gb. They will not buy 10. It's not how they operate. There's good money in making things work despite that.

I'm tired of arguing with somebody whose view is so limited. You know one side of IT and don't realize how truly pervasive it is - it operates in many places and a lot of us deal with worlds where we don't get ideal setups to support us. We cope with the shortcomings and make things work anyway. I would love to put 64Gb of ram in a server if I know the average use will be 30Gb. The reality is that the only reason my customers even gives me the 2Gb buffer is because 32Gb is the LOWEST you can go over 30Gb.

Get real dude, we don't all get to design hardware around software requirements. Many of us are designing software and OS configurations around hardware limitations.

Re:Improvements

[Raenex]

Oh I agree, but if the customers want a system that can handle connections from 10000 users at a time - who am I to tell them they can't do it ?

Who said not to? That doesn't mean you push the server to 95% memory capacity where a small amount of variation will put you over 100%. Either get more memory, another server, or figure out why you are using so much memory. Blaming the JVM footprint when you've got 32GB while also talking about Perl tells me that you just don't know what you are talking about.

A server gets put down and is expected to stay stable even if it's pushed to 100% memory at times

This is truly idiotic. Even the kernel has variable memory usage. Once you go over 100% your machine is going to start thrashing and your performance is going to go all to hell.

That's because your experience is obviously ... a bit more limited.

Why, because I'm not huffing and puffing like you are? I judge you on your technical statements, not some e-peen Slashdot resume.

Devs can now be more lazy

[nzac]

Along with promoting an easier multithread API the artical also contain the paragraph:

Project Coin's diamond syntax for constructor calls lets the compiler infer type arguments, and the try-with-resources statement helps the compiler make reliable code by automatically closing files, sockets, and database connections when developers forget to do this, Ratcliff says: "That's something that's been tripping up developers -- especially young developers -- for years. That'll be a good productivity improvement and will reduce bugs."

This is almost like programming language lock in, once you have programed in Java for a few months you are incapable of writing functional C++ code and if you lean to program in java you have no idea why your non java programs fail.

Re:Devs can now be more lazy

[ApplicativeJones]

Yes. Let's shun all advances in programming language design, because they make it too hard to use languages without them.

Man, imagine what'd happen if you ever ran into a programming language with a good design. There are some out there that are actually pretty good. Of course, no language is perfect - or even close. But people who resist making things better just because it makes defects in existing languages more obvious is doing themselves, and the entire field of software engineering, a disservice.

Re:Devs can now be more lazy

[slack_justyb]

once you have programed in Java for a few months you are incapable of writing functional C++ code

Having been a Java developer for eleven years now, I still write C++ with few memory leaks and a couple of passes through a debugger usually fixes that. I am not sure why people believe Java makes you a bad programmer. Java, C#, and C++ all follow the same design patterns, they just use different methods on getting there. It is really not that hard to remember, hey in this language the object is GC and in this one it isn't. A singleton design pattern in C++ and Java look exactly alike and function exactly the same. Java you don't have to worry about cleaning the mess up and in C++ you clean it up in the destructor, c'mon some people make it out to be the difference between gutting a fish and brain surgery. It's all syntax sugar, a lot of people need a new argument.

Re:Devs can now be more lazy

[nzac]

I did not say its currently the case, looking at the article I suggested/said it could be going there. (I do think that some of Javas features unnecessary make it easy for people to write programs that could easily preform better.)

Do you believe, not having to close unlock things makes you a better programmer? or that developer of Java will magically make it so there are no issues like (unnoticeable but cumulative) effects on performance, keeping the file open longer than it needs to be or having to reopen it?

Re:Devs can now be more lazy

[dummondwhu]

I don't know about you, but when I walk into a convenience store, I pull the door open and walk in. From there, I don't turn around and pull the door closed behind me because it does that by itself. I don't think that makes me a better or worse shopper, but I think it's one less thing for me to worry about. There are no points awarded in life for having a bigger pile of stuff to worry about.

Re:Devs can now be more lazy

[nzac]

Are these really meaningful advances? (If they are then yes i would agree with you)

Though i have no idea what they added to thread module if it was an advancement i would think you could sell it a bit better than it makes things easier. There has got to be a performance hit for "extending" garbage collection to files, sockets, and databases. How hard is it to realise you no longer need a resource and free it.

Sure its fine if you don't need it to be faster than python (or pypy) but changes like these (yes you could pretended they don't exist and then it may not matter) were to accumulate it could hurt the language rather than make it better. Assuming that Java programs do run (insignificantly) slower, it makes C++ and its dev's all that more important.

Re:Devs can now be more lazy

[Anonymous Coward]

shoppers are fine with that but architects have to make sure that said door does close.
be careful not do degenerate from a programmer into a user.

Re:Devs can now be more lazy

[sjames]

Can you believe these so-called programmers? Always going on about their infernal structured whatsises with their new-fangled compilers and crap! Real men program directly in binary and enter the code with toggle switches. How will the program layout ever be right if you let some so-called "linker" do it? IOf that wasn't bad enough, now they want to ling AT RUN TIME fercristsake!

Now GET OFF MY LAWN!

Re:Devs can now be more lazy

[The Dawn Of Time]

In your first sentence you explain you have no idea what you're talking about, then you proceed to spout off in the remainder of your post anyway. You're pretty clearly the voice of inexperience. You should learn to lurk more and talk less.

Re:Devs can now be more lazy

[slack_justyb]

Do you believe, not having to close unlock things makes you a better programmer?

No and that's not the point of these features. A car can have a manual or automatic transmission. Either one won't prevent the driver from being an ass to me on the road or make them a safer driver overall. Likewise, the features aren't there to make one a better programmer or a programmer who is bad at resource handling suddenly better. The features are there to handle certain cases automatically, cases where we've already had a solution (using finally) but would have preferred it to be less verbose.

Likewise, GC has been a favorite subject of C++. Should we have GC in the core of C++ or not? There is always a third party library that can add GC to your C++ project. Does using that library make you a bad coder?

Making your job easier is not equal to making you a bad coder. A bad coder *is* no matter the language, platform, or libraries used. When I develop applications that need to talk to a DB, I have to think about when I need to let that connection go, it doesn't matter if I am using Java or C++ or Python, when to let go of a connection is part of the design, not the language. The language part only dictates how many lines of code it will take to let the connection go, not when. If you are not thinking about how you handle resources it is not a problem of the platform so much as it is the design phase. Even in GC environments you have to keep track of what is happening to your resources, you just keep track of them in a different manner.

As a rough example: I open a file in Java or C++, I still have to think about how that file will be used and when I need to close it (no other option in C++) or just let it close by itself (an option in Java but not usually the best one.) If we are talking about a text file that only the current running application is going to use then yeah let it close by itself in Java and close the file in the destructor of the main delegate (or whatever you may have used to open the file) in C++. Both of those options function the exact same way, the file doesn't close until the application does. It's just syntax sugar that separates them, either way I've got to remember that I have a file open.

I did not say its currently the case, looking at the article I suggested/said it could be going there.

That's been an argument for decades for everything. Again, making something easy does not make a bad programmer. Bad programmers tend to not think things out fully and giving them a manual or automatic isn't going to change that.

Re:Devs can now be more lazy

[Joce640k]

Are these really meaningful advances?

Making it easier for people to close files? I'd say that was an advance.

At least somebody is finally admitting that garbage collection causes as many problems as it solves.

Re:Devs can now be more lazy

[nzac]

I don't like your metaphor, you have simplified the issue too far and it hides the numbers needed to compare things to see if the tradeoff is worth it and I never said there is a problem with the part you described.

But to carry it on what happens when you go to another store and the door does not close and something goes wrong (say something gets blown over and you have to pay for it) or when to cover the cost of putting the door they markup your prices. (I assume the door is hypothetical as here the door would both open and close for me.)

Re:Devs can now be more lazy

[Joce640k]

Java you don't have to worry about cleaning the mess up and in C++ you clean it up in the destructor

If you're doing it right C++ needs very few destructors and memory leaks only happen once every blue moon.

Re:Devs can now be more lazy

[dummondwhu]

Certainly, but in this case, I am a user. The architects at Oracle (hopefully) made sure that the doors close correctly. I don't know that to be a certainty, as I haven't tried Java 7 yet, but you get my point. It doesn't mean that I've devolved into an end-user. It's just that my job was made easier.

At some point, farmers mostly stopped planting fields with the help of a hoe and they hooked up plows to oxen or some other beasts. Then, the tractor was invented, making life even easier. Advance after advance after advance, and no one would think to say a farmer today is less capable. Sure, he could do his job with hand tools. But how many people would he be able to feed that way?

Re:Devs can now be more lazy

[tsotha]

After using java for a decade or so I can't go back to C++. It would be hard to program anything after gouging my eyes out.

Re:Devs can now be more lazy

[dummondwhu]

The example was intentionally simple because I'm only pointing out that there's nothing inherently wrong with, as a programmer, letting technology make life a little easier. Certainly we can take the door example or even the real world example of people not closing files/sockets properly in all sorts of directions, but in general, it's OK if things are made easier. Generally, it doesn't turn programmers into simpletons because for every new little nice short cut and helpful feature, there is more and more room to do bigger and better things without being encumbered by so much of the small stuff (especially forgetting the small stuff here and there and spending an inordinate amount of time trying to figure out what went wrong).

Re:Devs can now be more lazy

[ApplicativeJones]

Let me just make one suggestion: Learn another programming language. Learn something fundamentally different. Learn it thoroughly. Then decide if there have been advances made in the design of programming languages since C++.

I'd recommend Haskell, myself. It's the furthest you'll get from the mainstream, while still having incredible support for writing real software. But if you learn it, make sure to learn it thoroughly.

Understand what the IO type really is. Not how it's implemented, that's boring. Not what type classes it implements, that's still relatively boring. Understand the consequences of it being a higher-kinded type that describes IO operations as a first-class type. Understand what a type like "IO (IO (), IO ())" means, and why IO is far more interesting than just a tag on impure functions. Understand what a type like "FilePath -> IOMode -> (Handle -> IO r) -> IO r" means, and how it's related to the original point here.

And that's just scratching the surface. Is Haskell perfect? Far from it. Very far from it, in fact. But there are a lot of things it does better than any other language you can build real software with. It's worth learning what those things are. Once you see that there are fundamentally better ways, you might begin to welcome advances to mainstream languages.

Re:Devs can now be more lazy

[nzac]

Thus we have scripting languages (for performance CPython or pypy) which is this taken to the extreme.

I said that due to the tone of the article and the quote (i don't know who he is) that making the language easier (rather than simpliler) would make it make it harder to move to another language (others have said this is nothing new) and that it could be intentional.I think i left it up to the reader to decide the extended consequences of this.

Re:Devs can now be more lazy

[nzac]

I think the design focus should be simpler rather than easy (using the word easy over simple just screams bad deign to me, maybe the article writer just chose the other work). I tried to make it obvious that my one line was based of the paragraph from the articular. I don't think anyone who has much influence has ever wanted GC directly built into C++. It just does not fit to have automatically included in Native Code.

I never said this would make you a bad programmer just that it would be frustrating/difficult to move to an alternative language.

That's been an argument for decades for everything...

Fair call but then i would have just be modded off topic.

Re:Devs can now be more lazy

[slack_justyb]

If you're doing it right C++ needs very few destructors and memory leaks only happen once every blue moon.

Exactly. Usually deep in the code internals you'll see a couple of d-tors that do all the delete's. Everything else just seems to auto-magically happen and delete itself, sorta like Java.

Re:Devs can now be more lazy

[ispeters]

Are you trolling? You said:

There has got to be a performance hit for "extending" garbage collection to files, sockets, and databases. How hard is it to realise you no longer need a resource and free it.

They haven't "extended garbage collection", they've introduced syntactic sugar. Instead of this (with real indenting in real life because you're not limited by Slashdot's lame commenting system):

File file = null;

try {
file = openAFile();

// operate on file, possibly causing an exception
}
catch (IOException e) {
// do whatever you like with e, possibly rethrowing
}
finally {
if (file != null) {
try {
file.close();
}
catch (IOException e) {
// what the hell do you do here?
}
}
}

You can have something like this:

try (File file = openAFile()) {
// operate on file, possibly causing an exception
}
catch (IOException e) {
// do whatever you like with e, possibly rethrowing
}

// file is closed here because the compiler has inserted
// the right epilogue for you, saving you boilerplate, preventing
// you from inserting the wrong boilerplate, and not impacting
// the GC in the slightest

So either you're trolling or "The Dawn Of Time" is right: you have no idea what you're talking about.

Ian

Re:Devs can now be more lazy

[SJS]

The problem you describe isn't one of developers being lazy... it's a problem of developers being *stupid*, and failing to learn anything from the languages they've previously programmed in. Every language you use in anger should inform you about viewpoints and techniques for every subsequent language, even if they don't directly apply.

This is why all programmers should start with a language like Pascal, so they learn the basics of structured programming, lexical scoping, and what the hell the difference is between pass-by-reference and pass-by-value. It would be best if at least one other language were to be learned before the programmer attemps to learn Java.

I would never recommend that any programmer learn C++, except as an example of what NOT to do when designing a language. Learning C is a good idea, so the programmer can learn what a high-level assembler looks like.

A language like Smalltalk or Self should be thrown into the mix somewhere, just for contrast.

Some sort of prolog should prove useful as well. (Although, if you seriously think that adopting the prolog viewpoint for general computing, you need to be shot in the face.)

And if trying all these languages doesn't improve your code... you're in the wrong job.

(As for laziness... that's a virtue, according to Larry Wall, and he's likely right.)

Personally, I found that once Generics and Annotations were imposed on Java, the language became a lot harder to read and maintain. They might as well just gone ahead and mandated the abomination that is hungarian notation and made the language completely stupid.

But then, Java was something like language #11 that I learned. So my viewpoint is biased.

Support for other languages in the JVM might be nice, but I really don't see the point.

Re:Devs can now be more lazy

[bonch]

Do you believe, not having to close unlock things makes you a better programmer? or that developer of Java will magically make it so there are no issues like (unnoticeable but cumulative) effects on performance, keeping the file open longer than it needs to be or having to reopen it?

I believe not having bugs makes you a better programmer, and if the language helps enforce that by design, even better. If you're trying to prove yourself by doing things manually that computers are capable of handling for you, you're programming for the wrong reasons. Users don't give a shit how you made the product; just that it doesn't crash or leak.

Re:Devs can now be more lazy

[bonch]

Just look at those silly C++ programmers letting the compiler manage the stack for them. Once they've programmed in C++ for a few months, they'll never be able to manually set up call stacks in assembly across multiple operating systems and instruction sets.

Re:Devs can now be more lazy

[phantomfive]

Performance hits for closing files is extremely minimal. By far the slowest part of writing a file is the time it takes to transfer it to disks. It is in fact often on the order of a million times slower than any other part. Worrying about the performance hit of a few extra instructions to close a file is silly in that context. There is a law related to this point, but I can't find it right now. It is described under The General Task of Code Optimization.

Re:Devs can now be more lazy

[dkf]

There has got to be a performance hit for "extending" garbage collection to files, sockets, and databases. How hard is it to realise you no longer need a resource and free it.

Garbage collection can take some time to realize that a resource is no longer needed and release it. For memory, it's mostly not a huge problem (and you can tune how often the garbage collector runs) but many other resources come from really rather small pools so releasing them earlier is really important. This is especially so for anything connected to a file descriptor and/or process, such as all those that you list.

Releasing a resource early means doing some kind of close operation on it, and requires the programmer to do something (GC is the fully automated approach, and that releases late). In Java up to 6, that operation was typically an explicit close() method call, and while the language did provide a try/finally construct to help with it (itself a big advance over older languages like C) it was still rather verbose. The technique of binding lifetime to a syntactic scope came later (well, it was earlier in Lisp but too many people forget to raid that treasure trove of techniques) and has now been adopted in Java 7. It was around earlier in C#, but in many ways Java is a very conservative language — it simply does not change quickly (and that's mostly a good thing; a platform that is changing rapidly is not a great thing to build production code on). In many ways it's just syntactic sugar as it does not add any fundamental capability to the language, but it makes it enormously easier to write correct and efficient code. (The new-style for loops in Java 5 were another example of this tendency.)

Improving the ability of programmers to write correct and efficient code is indeed an advance.

Re:Devs can now be more lazy

[Anonymous Coward]

karen millen stores
karen millen coat
millen karen
karen millen dress
karen millen one shoulder
Karen millen online

Re:Devs can now be more lazy

[nzac]

Sorry was not clear i meant to imply they were applying the concept of GC to resources other then memory. Java decided you no longer need the resource and frees it. This is simplified situation say you make an object that opens a file (or other resource) but then still need the object without the file then the VM would recognise this and close the file. Its more complex than just SS.

And you raised the issue of what happens if you cant close/save the file, it would be come more complex to handle the only way this is easier is if you happy for java chose what to do in this case.

Dawn of time is right i don’t know shit about java but still missed my point (yes everything past the first sentence is shit invented on this spot when i look back on it, i could justify some of it but not the important parts). Is intrenching GC concepts in modern programming a clear advancement that most future languages will use? I thought it was clear my comments came from the language used in the article.

Re:Devs can now be more lazy

[silentcoder]

> You should learn to lurk more and talk less.

Dude, this is /. not 4chan...

Re:Devs can now be more lazy

[silentcoder]

>Generally, it doesn't turn programmers into simpletons

Nope COBOL took care of that decades ago...

Re:Devs can now be more lazy

[Anonymous Coward]

So exact what problem do GC solve? It is not hard to deallocate what you have allocated. That is what the destructor method on objects normally are used for. Now, Java removed the destructor method. Why? What this good language design?

And yes, I am a Java developer since 10 years.

Re:Devs can now be more lazy

[silentcoder]

I must commend you good sir, for the most convoluted and twisted slashdot car analogy I have ever read. That is one hell of a high bar.

Re:Devs can now be more lazy

[silentcoder]

According to XKCD real men hold their hard drives in the air and wait for cosmic raise to randomly magnetize the right bits for the program they wanted to write (which chaos theory says must happen if you hold it long enough).

Also - there's an emacs command for that...

Re:Devs can now be more lazy

[ggeens]

So exact what problem do GC solve?

Manual memory management is tedious and error-prone. You need to add your destructor calls in all the right places, taking into account all possible program flows. Any mistake results in a memory leak or a crash.

It is not hard to deallocate what you have allocated.

Not if you have shared objects.

And yes, I am a Java developer since 10 years.

And you still don't understand the environment you're working on? That's sad.

Re:Devs can now be more lazy

[maxume]

ecode gives you arbitrary indentation:

blah
    blah
        blah

code also falls through the filters:

blah
    blah
        blah

(this is with the tags dropped into "Plain Old Text", not sure what the other formatting options would do)

Re:Devs can now be more lazy

[Anonymous Coward]

It looks to me as if they just dicovered RAII. Granted, now the compiler does the job for you, but how freaking hard is it to do it manually ?

Re:Devs can now be more lazy

[Anonymous Coward]

Yes, they are.

It is just like C# try with resource pattern.

Its more like calling a destructor that closes (or returns to pool) the database connection/file/whatever when the var goes out of scope.

I for one will not miss the 42 layers of nested try/catch blocks required to close a file.

Re:Devs can now be more lazy

[tigersha]

cat > a.out

Re:Devs can now be more lazy

[Anonymous Coward]

Sorry was not clear i meant to imply they were applying the concept of GC to resources other then memory. Java decided you no longer need the resource and frees it. This is simplified situation say you make an object that opens a file (or other resource) but then still need the object without the file then the VM would recognise this and close the file. Its more complex than just SS.

And you raised the issue of what happens if you cant close/save the file, it would be come more complex to handle the only way this is easier is if you happy for java chose what to do in this case.

No, you do not understand. Unless you use the new try-with-resources syntax and declare the resource in the parentheses after the try nothing happens. So if you have a resource for which this is inappropriate you do not have to use it. It really is just syntactic sugar. Java does not 'notice you no longer need the resource.' The compiler (not the runtime) inserts code based on your use of the try-with-resources statement.

Re:Devs can now be more lazy

[EdgeCreeper]

HTML Formatted with ecode does not give you indentation, and elements will not help either. Plain old text mode with ecode does give indentation. This has saved some time. Thank you.

Re:Devs can now be more lazy

[Bill_the_Engineer]

Sure its fine if you don't need it to be faster than python (or pypy) but changes like these (yes you could pretended they don't exist and then it may not matter) were to accumulate it could hurt the language rather than make it better.

Java 7 is significantly faster than Python 3, so I don't know where you are getting your information.

Assuming that Java programs do run (insignificantly) slower, it makes C++ and its dev's all that more important.

If speed is really an issue then I would write those portions in C. Anyway I have many lines of C++ code floating around in a lot of embedded systems, and I haven't been harmed while programming in Java (or any other language).

If portability was important and I could take a slight hit in speed, then I would choose Java.

If speed was important and resources are low then I would choose C.

If speed was important and there's a need for OO to manage the complexity then I would chose C++.

If "glue" code needed to be created and speed was not being considered then I would pick Perl, Python, or Ruby (Perl is the language most used for this).

If I needed to make a dynamic website and I wanted to use a web framework to keep my workload manageable I would pick Python or Ruby.

Re:Devs can now be more lazy

[Bill_the_Engineer]

Real men program directly in binary and enter the code with toggle switches.

I know what you mean. I fell for the columnated paper to write out the fortran 77 code years ago, and after being stuck with all those pads I decided to wait and see how long the text editor fad lasts. ;)

Re:Devs can now be more lazy

[cowdung]

So exact what problem do GC solve?

It makes mem management less error prone. Also in some cases it can reduce the memory management overhead and make your app have a higher throughput rate!

It is not hard to deallocate what you have allocated.

It is not hard to write a program in Assembly either. However high level languages give you convienences to help reduce your bug rate.

That is what the destructor method on objects normally are used for.

Destructors are like finalizers (except deterministic). The big problem with destructors is that they make object deallocation SLOWER so you can't get the higher throughput I mentioned above because you have to process all your garbage. A copy collector doesn't have to deal with your garbage it simply ceases to exist.

Now, Java removed the destructor method. Why? What this good language design? And yes, I am a Java developer since 10 years.

I had that question 13 years ago. I have since discovered the answer to it. I don't believe you're a real Java developer if you don't understand this.
I liked destructors, but finally + efficient memory deallocation is something worth losing destructors for.

Re:Devs can now be more lazy

[Unequivocal]

You've just effectively summed up and answered about a decade (or more?!) of slashdot comment-chatter. Not that I expect this to change anything, but +1 from me. :)

Re:Devs can now be more lazy

[Bucky24]

You need to add your destructor calls in all the right places, taking into account all possible program flows. Any mistake results in a memory leak or a crash.

Personally I think this causes people to write better code, forces programmers to think ahead when they are developing, to avoid those problems, and in general improves the skill of the programmer.

Is that a bad thing?

Re:Devs can now be more lazy

[Bucky24]

You're using the java api, certainly, but that makes you a developer, not a user. Just like the architect is using the laws of physics to design a door, but that doesn't make them an end-user. It makes them an architect. (yes it's a weak analogy I know but it's the best I could come up with)

Re:Devs can now be more lazy

[sjames]

There is only one true text editor!

Re:Devs can now be more lazy

[Anonymous Coward]

I think this is somewhat like extending GC to files, but dear lord I like the idea, I can't wait for Python to pick it up (since my work is done in Python and I really can't change that).

I get a buzz from syntactical sugar, making sure I close files is just plain annoying, IMO.

Re:Devs can now be more lazy

[NoOneInParticular]

Ah well, after using java for a decade or so, I still go back to C++ now and then to feel a breadth of fresh air. Code where you actually don't pay for what you don't use; no per object overhead when you don't need it; no garbage collector that needs to be tuned independently from the program; no runtime environment + jit that optimizes away the errors of newbies, not the needs of the proficient. No magic, just a program that you can understand.

Re:Devs can now be more lazy

[jgrahn]

Likewise, GC has been a favorite subject of C++. Should we have GC in the core of C++ or not? There is always a third party library that can add GC to your C++ project. Does using that library make you a bad coder?

Yes, if you use it for things where C++ has better mechanisms, i.e. most of the cases.

... As a rough example: I open a file in Java or C++, I still have to think about how that file will be used and when I need to close it (no other option in C++) or just let it close by itself (an option in Java but not usually the best one.)

Have you ever done any C++ programming? Does RAII ring a bell? A file gets closed when its object goes out of scope. (Of course no matter what the language, if you've written to the file it's usually prudent to check it for I/O errors at closing time.)

Re:Devs can now be more lazy

[tsotha]

I still go back to C++ now and then to feel a breadth of fresh air.

Well, okay, I suppose, as long as you don't have to maintain other peoples' code. I spent years chasing intermittent memory bugs in C++, and I'll be forever grateful to the java designers for freeing me from that task. About six months ago in a C++ project at my company someone found, by accident, one such bug. They'd been looking for it for more than a decade, finally giving up and writing a bunch of code to detect when it occurred and clean up the mess. I've never seen that in a java project, even one with junior and/or incompetent programmers.

Re:Devs can now be more lazy

[NoOneInParticular]

Ah okay. Yes ... maintaining other people's C++ code. Especially that of someone who just figured out how static variables could work together with operator overloading and templates. Shudder. You're right, Java is a godsend for that. I've seen some pretty brutal Java code too, but if you can't toss it, you can usually wrap it and hope it would not make too much of a mess later on. Uncontrolled C++ is a whole different beast. Don't let amateurs code, but.... no choice.

Re:Devs can now be more lazy

[slack_justyb]

Have you ever done any C++ programming? Does RAII ring a bell?

That's almost offensive. You use close in the destructor you idiot. Yes I know what RAII is since I made an example of its usage in the part of my comment that you did not quote, ye of limited sight and even shorter span of memory.

Yes, if you use it for things where C++ has better mechanisms, i.e. most of the cases.

Obviously that is that limited sight thing. Yes standard is good, but I would dare say not *most* of the cases. Boost comes to mind. However I doubt that to actually sink into your head based off of what you have thus far said. No matter if I wasted another five to six hundred words making my case. If you want to be arrogant that is fine. However, I have programmed sixteen years in C++, so please do me a favor and if you don't know me, don't try to comment on me or at least expect the same poor assumptions to be tossed in your direction, as I have done so in this reply.

Finally do your self a favor and get out whatever pent up aggression you may have here on this thread, since I have little time to reply back to an absolute single minded bigot such as yourself. I would hate for your vile language to be wasted on a thread that someone may actually reply back to.

I think I speak for many when I say...

[mattcsn]

...please don't let all these fancy tech buzzwords stop Minecraft from working.

Re:I think I speak for many when I say...

[Anonymous Coward]

...please don't let all these fancy tech buzzwords stop Minecraft from working.

Well... in a way I guess you DO speak for many. The jest you're making has a lot of truth. It definitely appeals to the anti-intellectual instant-gratification sentiment that's so damned common. They just want their shiny. They'd never voluntarily learn anything about how their shiny works. All that looking beneath the surface kind of shit would be too much work.

Re:I think I speak for many when I say...

[DeeEff]

Why'd you post as an AC? I think "looking beneath the surface" is what programming is all about, and what they're doing here with Java 7 is just silly.

Geez, catering to "young programmers" seems silly. If they don't learn it properly while they're young, it'll only get harder to learn once you get older.

COBOL -Basic-Apple ][

[Anonymous Coward]

Ah yes. The old "blame the language for the lack of a developer's skills" ploy. It's a sad carpenter who blames his tools for his incompetence. It's a sadder carpenter who blames a tool for other carpenters' incompetence.

You tell'em AC!

I once wrote an operating system in COBOL that was interpreted by Apple Basic. It was slick, man! The Apple ][ would boot up with its prom BASIC interpreter which would load the COBOL interpreter which would then load the OS that was written in COBOL! Man, it was AWESOME! (It is still starting up 'Hello World' which I started in 1984 butt ROCKS!) It PROVED with out a doubt that I was God's gift to CS AND Programming! Jim Gosling has an alter set up to me - he'll deny it, but he does! He prays to me on a daily basis as HIS personal God. I inspired him to write Java. Although, he couldn't achieve my Godliness, he tried with Java.

He is a disappoint, though - he never measured up to Stroustrup. Although, Stroustrup is a disappoint with his bastard child, C++0X or whatever the fuck he calls his demon spawned shit.

I will have to smite him with my COBOLx00xx0xxABCDx0 object oriented parallel quantum multidimensional language for light quantum parallel programming.

I have said and will say, COBOL is the future of CS!

Compatible with Andriod SDK

[Billly Gates]

How compatible is Java 7 with Java 6? Can I run the Andriod emulators? Is it more secure than java 6? I would like to use Chrome but it always runs Java by default and I got owned a month ago from this exploit. I hate using IE as it is the only browser I can disable Java from

Re:Compatible with Andriod SDK

[Anonymous Coward]

I'm confused. Just go to about:plugins in Chrome and click disable.

Also I'm certain there was a way to do it in Firefox aswell.

Re:Compatible with Andriod SDK

[vawwyakr]

You can install the notscripts add-on in chrome and then you can selectively enable JS based on the source.

Re:Compatible with Andriod SDK

[Bucky24]

Java != JS

SELL !! AAPL !! SELL NOW OR LOSE IT ALL !!

[Anonymous Coward]

It's heading for the tank, then it's headed for the bottom. MSFT !! Move Over !! AAPL Is Coming Down !!

Three Days of the Condor !! Oh, wait, Three Days of the Candor !!

What's in It for Developers?

[microphage]

Well going by previous statements by Larry Ellison and Oracles actions in regards to Red Hat Linux. They'll wait until your stuff is popular and then just take it and start charging support fees for your stuff.

"If an open source product gets good enough, we'll simply take it" link

Re:What's in It for Developers?

[Lennie]

That was one of the questions I wanted to ask. So how open (source) is it now ?

I just know OpenJDK exists, I even know where to download it:
http://download.java.net/openjdk/jdk7/

"Java 7: What's In It For Developers"

[jordan_robot]

A bag of hurt.

Re:"Java 7: What's In It For Developers"

[mrmeval]

Can we get it reviewed by someone who isn't a fanboi and butt licker?

Re:"Java 7: What's In It For Developers"

[phantomfive]

Yeah. Basically it's this:

There were a number of proposals for how to improve Java. Some of them were controversial. The controversial ones got moved out to Java 8, and the ones that everyone agreed on made it in to Java 7.

In essence, this is a good, solid, incremental update.

My idea of a perfect programming language is somewhat different, but I can respect this as a solid improvement.

Re:"Java 7: What's In It For Developers"

[jordan_robot]

This is your sense of humor calling to tell you -- calm down, its just a joke. Jeez-luise.

Re:"Java 7: What's In It For Developers"

[mrmeval]

OK this is not fanboi spew it is succinct and informative and told me what I'd want to know. It's not the masturbatory glee of the article that tried to slather me with vapid goo.

Thank you.

Poor Ol' .NET Dev--A Pity Party Next To Java 7

[curmudgeon99]

People, People, calm down, put a lid on it.

Look at yourselves... having a big jolly party. There are already so many fantastic features in Java--we're jaded in our big happy family. So many open-source offerings court the Java developer, we forget that we could be going back to Ol' Mamma Redmond night after night. Horrors!

Look at the poor, pathetic .NET developers. Unloved by Microsoft. Uneaten dogfood. Jilted in Windows 8. Told that .NET experience on a resume is a black mark with startups. They need an intervention.

Gentlemen and Lady, how can you Java Developers be so insensitive? .NET developers are weeping. A decade of hard-won knowledge lost and back with that FoxPro DBA textbook. They lay down with the Evil Empire and woke up with fleas. Go figure!

Re:Poor Ol' .NET Dev--A Pity Party Next To Java 7

[Kensai7]

It won't be jilted in Windows 8. Why you people keep perpetuating this myth? Just because C++ is making a comeback (it was about time) and JavaScript/HTML5 is finding a new home, doesn't mean that we throw away .NET Framework 4.5.

Re:Poor Ol' .NET Dev--A Pity Party Next To Java 7

[Anonymous Coward]

Why you people keep perpetuating this myth?

Schadenfreude mebbe?

Scam the scammers, FUD the Fudders. Life is sweet.

Re:Poor Ol' .NET Dev--A Pity Party Next To Java 7

[Anonymous Coward]

You need serious attention of a psychotherapist. Hurry!

Re:Poor Ol' .NET Dev--A Pity Party Next To Java 7

[Anonymous Coward]

This pathetic's own home page is developed using .NET (not that .NET has problem)

http://www.allegient.com/Pages/solutions.aspx

Re:Poor Ol' .NET Dev--A Pity Party Next To Java 7

[slack_justyb]

I am not sure why people keep saying this even in the light that Microsoft has said that they are bringing .NET even closer to the core API here.

HTML 5/JS is just being added onto what is already there. The fact that no one has heard about Silverlight has made everyone worried. Microsoft has talked about Silverlight just not to the degree that everyone had hope for. So since no one likes waiting until September, we'll just spread rumors and make Microsoft pay for suddenly wanting to do things like Apple and keep quiet.

Re:Poor Ol' .NET Dev--A Pity Party Next To Java 7

[Anonymous Coward]

What the hell kind of moderator actually modded this drivel insightful?

Do these developers include Android developers?

[bogaboga]

"...Paul Krill surveys the new capabilities that matter most for Java developers..."

Do these developers include Android developers? Well, that's the question. After all, Java code will run on Android's Dalvik VM without modification, right?

Re:Do these developers include Android developers?

[renrutal]

Since current Java SE code isn't expected to run and have the very same behavior in Android without modification in previous versions, I don't think it the current version would be any different. BTW, are Android developers considered to be Java developers by Oracle?

Re:Do these developers include Android developers?

[Anonymous Coward]

are Android developers considered to be Java developers by Oracle?

Only if Oracle wins some lawsuits and someone pays up. Otherwise, no.

Re:Do these developers include Android developers?

[angel'o'sphere]

After all, Java code will run on Android's Dalvik VM without modification, right?

What do you mean with Code in this case? Sourcecode? Or bytecode? The JVM bytecode won't run on a Dalvik VM. As the compilation way for Android is to create ordinary bytecode classfiles and cross tranlate those bytecode files then into Dalvik VM bytecode files, I assume you can use any "language" and only the libraries are an issue.

What Java really needs

[Anonymous Coward]

1. C#'s 'using' block so I don't have to use try/finally everywhere.
2. C#'s 'out' and 'ref' parameters so I don't have to allocate memory to return more than one value from a function.
3. C#'s 'struct' for "pass by value" data structures, or at least strong typedefs, so that a variable of type "typedef int A" cannot be implicitly converted to "int" or "typedef int B".

But honestly, I'd settle for a C# cross-compiler that targets the JVM.

p.s. Why oh why did I start a year-long game development project in Java? The hoops I have to jump through to get half-way acceptable performance are maddening. Someone please kill me.

Re:What Java really needs

[Anonymous Coward]

As someone who develops daily in both Java and C# (and Scala, C++, sometimes Smalltalk), I agree with #1 and #3. I write games and graphical or database intensive apps all the time. Regarding games, I would never use anything but C++ (maybe now C++0x), it's just a painful fact that most people aren't willing to accept.

#2 though, I am not sure you need this. As far as memory, if you learn how the GC works, things tend to work out just fine if you are returning objects from a function call. Smalltalk doesn't have either and it's in many ways the most practical and pure OO implementation out there. IMO, "out" and "ref" are symptoms of bad design. I rarely need them except when calling APIs (DirectX) that use them and with P/Invoke or COM programming. They're nice to have, but I find most bad programmers abuse the hell out of them. Most functions should do 1 and only 1 thing. Keeping things atomic is better all around for writing stable, maintainable, and multi-threaded/parallel code. "ref" and "out" lead to huge messes and are crutches for a lot of people who cut their teeth on C++ but haven't learned much. I was raised on C and ASM and later C++, but I certainly don't feel the need for either very often. I can see your need if you're constantly running out of memory, but I think you're likely wishing for something that will create more problems than it solves. There are better ways of optimizing memory.

Re:What Java really needs

[Homburg]

1. C#'s 'using' block so I don't have to use try/finally everywhere.

That's in Java 7, in the form of the try-with-resources statement.

Re:What Java really needs

[master_p]

This new Java statement, C#'s blocks and C++'s destructors are all hacks that solve a problem that would not exist in the first place if those languages had lazy evaluation: the code that uses those resources could have been passed as a functor to another function that opened the resources, called the functor and then closed the resources.

It it amazing that in this day and age, language designers ignore language design and compiler basics this much.

Re:What Java really needs

[Anonymous Coward]

You can do that in old Java . The problem is that it is too verbose.

Re:What Java really needs

[sourcerror]

JPA has pretty much lazyness.
Also, you can pass "functors" with anonymous classes.

Re:What Java really needs

[master_p]

But anonymous classes is not a convenient way to do it. They require the definition of a super class or an interface, they require typing the super class or interface they implement, etc.

Re:What Java really needs

[shutdown -p now]

This new Java statement, C#'s blocks and C++'s destructors are all hacks that solve a problem that would not exist in the first place if those languages had lazy evaluation: the code that uses those resources could have been passed as a functor to another function that opened the resources, called the functor and then closed the resources.

It seems that by "lazy evaluation" here you mean closures/lambdas. C# has them for 6 years now, and there are libraries that do precisely as you want, i.e.:

DoSomethingAndCleanup(x => {
...
}); // x is freed automatically here

There are two basic reasons why IDisposable/"using" is still preferred. The first one is perf - calling a lambda is a virtual call, and any local variables captured are lifted onto the heap. This is theoretically fixable by a better optimizer with escape analysis. The second problem is that many language features do not work across the boundary of the lambda - e.g. you can't goto into or out of it; if it's in a loop, you can't break/continue; and you can't immediately return from the enclosing function.

The other reason is that the wrapper-with-lambda approach can only handle the same as "using", but there are more cases than that. In particular, the case when one object owns another, and they should be freed together. You have to do this manually in C# (by implementing Dispose in owner, and calling the same on the owned object), but at least you can do it. If the only way to clean up the owned object is with a wrapper, you can't do that.

C++ can clean up owned objects fully automatically, so there's even less reason for using that pattern there (though in C++11, with its lambdas, you can if you want to).

Meh.

[jlarocco]

As a developer I could care less about Java itself. It's the new Cobol.

It's in an awkward spot. For anything high level I'd rather just use Python. And for the few cases where Python's not fast enough, it's easiest to jump down to C++ and write a module I can call from Python.

The best thing about this new release are JVM improvements for dynamic languages, which should help out projects like Jython, JRuby and Scala.

Re:Meh.

[RightSaidFred99]

Python is still a scripting language and has all the baggage that comes along with such for larger programs. Let me guess - you come from a system admin background?

Re:Meh.

[Anonymous Coward]

Scala isn't a dynamic language. And Java 7 isn't much help to it.

Re:Meh.

[Anonymous Coward]

A Python fan trolling other languages? Say it ain't so!

Re:Meh.

[mario_grgic]

Python is a nice language, but I'm not sure how it scales to tens of millions of lines of code? Java with its mature tools scales really well. It's not hard to maintain and add new features.

So, yes, if your project is small and runtime speed is not an issue develop in Python/Ruby or what ever. But if you hit critical code base size, scaling further might not be as easy. Also, tool support for dynamic languages can never be as good as for statically typed ones with reflection like Java or C#.

Re:Meh.

[slim]

Python is a nice language, but I'm not sure how it scales to tens of millions of lines of code? Java with its mature tools scales really well. It's not hard to maintain and add new features.

This would make more sense if you could mention some features of Java, pertaining to large codebases, that Python doesn't have.

It seems to me that whether you're using Java or Python, or anything else with a module mechanism, you write modules of a manageable size, and have them import one another.

Re:Meh.

[Anonymous Coward]

We have applications that are millions of lines of Python code at Google. This "baggage that comes along for larger programs" is a myth spread by poor programmers. We also have millions of lines of Java, C and Common Lisp (which was acquired through the ITA purchase) and none of them are difficult to maintain as long as you work with competent people.

Since apparently you surround yourself with incompetence, you'll have issues no matter what language you use. They'll just be slightly different issues.

Re:Meh.

[Anonymous Coward]

What foolishness. I'm going to actually totally agree with you, 100% and still call you a fool.

We've got these guys at work who designed their own RPC mechanism for Java about 10 years ago. It uses some non-XML (but XML like) language over a network pipe. Sure, it (lol) trusts the client for security and they wrote it in house, but it works fairly well overall at this point. I would rate these guys excellent Java programmers, very very good.

Unfortunately, they WROTE THEIR OWN FUCKING RPC LAYER. Yes, it's 2011, and they wrote their own when there is a glut of shit to choose from. They continue to use it for even some new systems they develop. Of course, they can - their team is growing, they have lots of resources and some very good Java developers.

I, not being an asshole, wouldn't do that _especially_ the part about proliferating it more widely in new apps. Then instead of sucking up the resources of 10 really good Java developers, maybe they can support and develop their apps with 8 people. Shit, maybe even 7.

And therein lies your problem. You're an asshole who doesn't realize that just because you _can_ do something, it doesn't mean you _should_.

Re:Meh.

[jgrahn]

Python is a nice language, but I'm not sure how it scales to tens of millions of lines of code? Java with its mature tools scales really well. It's not hard to maintain and add new features.

This would make more sense if you could mention some features of Java, pertaining to large codebases, that Python doesn't have.

He did, in the part you didn't quote: static typing. I really like the way Python handles this for small programs, but for anything a bit larger I really want a compiler, not myself, to do the static checking.

Re:Meh.

[slim]

I really don't believe that static typing is something that helps you with large programs.

I certainly see the value of strong static typing for certain jobs, but plumbing modules together into a large system isn't it.

Indeed, I like static typing for little fiddly components, and something more dynamic for the broad brush strokes.

For example, I recently put wrote an application in Groovy. I believe Groovy saved me days of work, and oodles of bugs, compared to writing it in Java. But, one core part required some encryption and some bit twiddling. Having the compiler help me with those fiddly bits was useful.

Here's a reason why it is not on http://java.com.

[antdude]

http://www.java.com/en/download/faq/java7.xml -- "Why is Java SE 7 not yet available on java.com?

Java SE 7 is the latest release for Java that contains many new features, enhancements and bug fixes to improve efficiency to develop and run Java programs.

Why is Java SE 7 not yet available on java.com?

The new release of Java is first made available to the developers to ensure no major problems are found before we make it available on the java.com website for end users to download the latest version. If you are interested in trying Java SE 7 it can be downloaded from Oracle.com..."

It sounds like even Oracle, itself, doesn't think Java 7 is ready for the public!

Riddled with errors

[Samantha Wright]

Among the delayed capabilities are adding Lambda expressions, or "closures," to Java for multicore programming, ...

Lambda expressions are not closures, and neither enable parallelization. Yes, the Wikipedia articles for both are dense swamps, but couldn't you have at least tried to ask someone? Please?

Re:Riddled with errors

[MischaNix]

I know better than to dare read the actual articles nowadays. It's never anything but disappointment.

Re:Riddled with errors

[Animats]

Lambda expressions are not closures, and neither enable parallelization.

I noticed that too. Somehow, in the Java community, closures somehow became connected to lambda expressions. Whether you have a syntax for anonymous functions is completely separate from whether you have closures.

In a reasonably static language like Java, adding closures makes the concept of the "stack" a lot more complex. A closure can contain a binding to a local variable outside the closure. That binding can outlive the scope of that local variable. So local variables now have to be handled in a more general (and slower) way. The semantics of local variables gets a lot more complicated, too.

Perl, Python, and Javascript have closures, although most programmers who use those languages don't know it. In those languages, any nested function can potentially be a closure. (Well, in Perl, there's a warning if you do that.) The Java people don't seem to have taken that route, possibly because they don't want to incur the overhead of a closure unless the programmer really wants one.

Re:Riddled with errors

[Anonymous Coward]

Java 6 (and before) does have closures with "bindings" to local variables. They are done using anonymous classes. Most Java programmers routinely use them (listeners) without even knowing they are closures. The syntax is a bit verbose but much clearer than the proposed lambda expressions for Java.

Re:Riddled with errors

[Anonymous Coward]

The "delay" referred to in "delayed capabilities" is not the delay between Java 6 and Java 7, but rather the delay between Java 7 and Java 8.

Re:Riddled with errors

[moonbender]

That only works for finals.

JLS 8.1.3: "Any local variable, formal method parameter or exception handler parameter used but not declared in an inner class must be declared final. Any local variable, used but not declared in an inner class must be definitely assigned before the body of the inner class."
  (source w/ discussion)

Re:Riddled with errors

[Anonymous Coward]

You mentioned that adding closures makes the stack a lot more complicated. Now I don't know if this is still the plan for Java 8 but the last I heard was that the semantics for scoping in closures would be the same as anonymous inner classes. Java already does a decent amount of work to determine what should get stack allocated, thrown into the heap, or reference an existing cached object.

Closures got removed from Java 7 as adding them requires a significant reworking of a large portion of the standard Java API. The options were: rush closures in 7 with an additional several month+ delay, or delay for 8 to make sure closures are done "right". Especially due to the changes in javac and the API, there was an agreement that it was in everyone's best interest to make sure everyone takes their time on closures. There is only one opportunity to get closures right, after that you are stuck supporting it for years and potentially break future backwards compatibility.

Re:Riddled with errors

[Anonymous Coward]

Huh? since java is onl pass-by-value, you can just copy them.

Re:Riddled with errors

[kervin]

Somehow, in the Java community, closures somehow became connected to lambda expressions.

Because Java's lambda expression feature is a closure....?

It didn't have to be implemented that way, but it is. So using Lambdas and closures as the same thing in conversation makes sense for Java ( and C# ).

Re:Riddled with errors

[Anonymous Coward]

I noticed that too. Somehow, in the Java community, closures somehow became connected to lambda expressions. Whether you have a syntax for anonymous functions is completely separate from whether you have closures.

That is probably because no common programming language implements a closure without a lambda expression. If you can name a language that does closures without lambda expressions, feel free to mention it.

Re:Riddled with errors

[sproketboy]

So?

Re:Riddled with errors

[benjymouse]

So using Lambdas and closures as the same thing in conversation makes sense for Java ( and C# ).

Speaking of C#, no, lambdas and closures are definitively *not* the same thing. A C# lambda may be a closure (if it captures any variables from the lexical scope), it may be just a function (if it doesn't close over any variables), or it may be an expression tree which is totally not a closure at all.

Likewise, a closure need not be created through a lambda expression, an anonymous method may also be a closure.

Re:Riddled with errors

[Just Some Guy]

Is Python common enough for you? It supports named functions as closures, not just lambda expressions.

Re:Riddled with errors

[shutdown -p now]

A closure is supposed to close over local variable bindings, not values of said bindings. This distinction is irrelevant in a language like Haskell where bindings bind directly to values, but it makes all the difference in e.g. Scheme or Java, where bindings bind to mutable locations.

Re:Riddled with errors

[shutdown -p now]

I noticed that too. Somehow, in the Java community, closures somehow became connected to lambda expressions. Whether you have a syntax for anonymous functions is completely separate from whether you have closures.

The reason for the mix-up is because lambdas are most useful when they can also be closures; and, conversely, closures are most useful when they can be defined inline. It just works better with most common patterns where they are used (e.g. task continuations).

In a reasonably static language like Java, adding closures makes the concept of the "stack" a lot more complex. A closure can contain a binding to a local variable outside the closure. That binding can outlive the scope of that local variable. So local variables now have to be handled in a more general (and slower) way. The semantics of local variables gets a lot more complicated, too.

Perl, Python, and Javascript have closures, although most programmers who use those languages don't know it. In those languages, any nested function can potentially be a closure. (Well, in Perl, there's a warning if you do that.) The Java people don't seem to have taken that route, possibly because they don't want to incur the overhead of a closure unless the programmer really wants one.

It's not as bad as it sounds. You don't need to make all locals more expensive, but only those which are closed over (and even then only if you can't statically prove that local is not mutated after the closure is created) - which, in a language with lexical scoping, is trivially determined in advance. So you wouldn't incur any overhead for a variable unless that overhead is made necessary by the fact that it's closed over.

Re:Riddled with errors

[Anonymous Coward]

What Java is implementing are indeed closures (not just lambda expressions) but limited ones. The current route being taken in Java is that closures/lambda expressions can only reference local variables which are 'final' and whose values can therefore be 'snapshotted' at the moment when the closure is created.

Re:Here's a reason why it is not on http://java.co

[MischaNix]

I believe this is actually because the JVM for 7 hasn't made it to the Mac yet.

Scala is static, not dynamic

[Anonymous Coward]

Just to correct the article: Scala is not a dynamically typed language. It uses type inference (at compile time) to create a highly expressive language which still benefits from static typing.

What's In It For Developers

[codepunk]

What's In It For Developers? Lawsuit

Re:Here's a reason why it is not on http://java.co

[Lisandro]

It sounds like even Oracle, itself, doesn't think Java 7 is ready for the public!

And they are right indeed...

Re:Here's a reason why it is not on http://java.co

[antdude]

If it is that bad, then don't release it!

Did update #1 even fix it?

Re:Here's a reason why it is not on http://java.co

[Lisandro]

AFAIK it is planned to be fixed on update 2. Which is kinda retarded - even for Oracle standards.

Re:Here's a reason why it is not on http://java.co

[antdude]

Wow, that is seriously messed up if it is true. I will stick with the older stable version (v6u27) that just got an update last week. ;)

Regarding multicore usage...

[Anonymous Coward]

... is there something you can't do with Threads, but you can with Fork/Join?

Re:Regarding multicore usage...

[shutdown -p now]

No. Fork/join is a higher-level thing that still (usually) works on top of threads, and usually helps you avoid fragile explicit locking.

Your question is, basically, akin to "is there something you can't do with assembler that you can do with C"? The point of C is to be a convenient higher-level abstraction, not to provide completely new functionality.

Skechers UK

[xjb8132]

A heath shoes are good for people to keep fit, Here we have offered our Shape Ups Skechers shoes, you can have a try when you are walking for a walk, our MBT Shoes Skechers UK shoes may make you more strengthen, on the other hand, this summer the he Skechers Shape Ups Sandals are also necessary for you.

No Thanks!

[Greyfox]

I've been playing with C++ again recently and had forgotten how much I really liked the language. I have real destructors again! That, along with oracle's recent abusive behavior toward Android leads me to dance the "Oracle can Blow Me" dance! Here I go! Oracle can blow me! Oracle can blow me! Yeah! Shake it!

Google just needs to re-implement all their shit in C++ and we can get an "Oracle can Blow Me" congo line going. Having a native mode executable build down to 20 *kilobytes* and actually run in 20 kilobytes is freaking awesome. Having real system level control over your hardware, awesome. As long as you're not seduced by template fuckery (You know who you are, "lets factor prime numbers at compile time" template people!) or dynamic link libraries, it's a fine language!

Re:No Thanks!

[Mr Thinly Sliced]

As long as you're not seduced by template fuckery (You know who you are, "lets factor prime numbers at compile time" template people!) or dynamic link libraries, it's a fine language!

I agreed with you until you discourage dynamic link libraries.

I'm someone currently making the move back to C++ from Java (reason - predictable scheduling) after 10 years in the J jungle. If you don't have dynamic libraries how would you do plugins? (Never mind that dynamic libraries are necessary for anything larger that a simple standalone application.)

Admittedly the tooling for building is still messy (autotools work, sure, but are a pain to have to deal with).

As an aside, the new c++0x features have really changed C++ from the "new" "delete" fiasco I remember from 1995. STL plus boost makes C++ rather natural and use of threads is pleasant after I previously had to jive with pthreads.

Re:No Thanks!

[SplashMyBandit]

20 kB. You clearly are not building applications that are hundreds of thousands of lines with dozens on people working on it. If you were you would be looking at things a little differently (and yes, sure you can do stuff in C++, as I did for a decade, but you are not nearly as productive as you are in Java).

Re:No Thanks!

[mario_grgic]

Google will never do that. Being a good C++ requires Buddhist monk discipline and restraint to not misuse the language features (and C++ makes it really easy to do that), experienced language designer knowledge to really understand some finer points of C++ committee design decisions, and unbelievable amount of patience when working on code base written by people who don't fit the criteria. Did you ever notice how developers in higher languages spend 90% of the time talking about the problem domain. C++ developers spend 70% of the time talking about C++ language and design issues.

This is why Google won't "punish" their platform by requiring everyone to develop in C++ for it. That would be suicidal.

Re:No Thanks!

[devent]

Yeah, destructors in which you cannot throw an exception. I'm living in Europe and using OpenJDK, so Oracle can blow me, too. In addition, can you explain why a 20 kbytes executable is "awesome"? I have 4GB of RAM, I really don't care how much an application is using as long as it can do the job.

Furthermore, you don't want to use templates and dynamic linking? So no STL and boost, and no other libraries at all, because you want your executable be 20 kbytes.

I think Google already re-implemented all the shit in C++ anyway, how do you think they can write the DalvikVM? Plus, software patents are not tied to a particular implementation or language. So even if Google would implement Android in their Go language, Oracle can still sue them.

Re:No Thanks!

[shutdown -p now]

Yeah, destructors in which you cannot throw an exception.

You can if you want to. You can even catch that.

It's just that it's almost never a good idea - what, exactly, do you expect the compiler to do when a destructor is automatically executed during stack unwinding because of some existing exception, and throws another one? silently override it, like Java does for return values with return-inside-finally?

Re:No Thanks!

[devent]

I never understood the need for a destructor. For 99% the GC is just fine and for other resources besides memory I have a close method. If you really need a custom memory management, then you can hack the OpenJDK.

http://www.parashift.com/c++-faq-lite/exceptions.html#faq-17.9
"[17.9] How can I handle a destructor that fails?
Write a message to a log-file. Or call Aunt Tilda. But do not throw an exception! "

So RAII is completely useless for any kind of resources. That's why I also don't understand the hype about RAII.

From Wikipedia:

~file() {
                if (std::fclose(file_)) { // failed to flush latest changes. // handle it
                }
        }

void example_usage() {
        file logfile("logfile.txt"); // open file (acquire resource)
        logfile.write("hello logfile!"); // continue using logfile ... // throw exceptions or return without // worrying about closing the log; // it is closed automatically when // logfile goes out of scope
}

And what if the std::fclose method of the log throws an exception? Where should I log that? In the worst case nothing is flushed to the file and the log is empty. The exception is not logged so you can spend hours to find your bug. That is true for all other kinds of resources, be it sockets, pipes, etc.

"Using RAII-enabled resources simplifies and reduces overall code size and helps ensure program correctness."

Except where the methods in the destructor throwing an exception in this case almost all developers just ignore it, how is that to "ensure program correctness".

Re:No Thanks!

[shutdown -p now]

I never understood the need for a destructor. For 99% the GC is just fine and for other resources besides memory I have a close method.

close() method is not the antithesis of RAII. The point of RAII is that close() method should be called automatically inasmuch as possible, by having well-defined object lifetimes and object ownership relations.

And what if the std::fclose method of the log throws an exception?

fclose() cannot throw an exception, because it is a C function. It can fail otherwise, by returning an error code. But, what, exactly, do you propose to be done then? Not being able to clean up the resource is, frankly, a design bug for that resource. Handling an error properly normally requires tearing down resources - if that can also fail, then you're in a situation where you plainly can't proceed, since you can't clean up to move on to other stuff.

This is by no means unique to RAII, but is a general problem with resource management. In Java 6, suppose you have a try-finally, and you call close() explicitly in finally - And that throws. What do you intend to do in that case, considering that there may still be a pending exception thrown from try? You can either suppress the one from close(), or let it override the one from try. You are arguing that the first is bad because it loses an exception; but so does the second, and it loses a far more important one!

Java 7 try-with-resource blocks chain exceptions in that case. That's a nifty trick, but isn't 100% foolproof. On the other hand, it does show that RAII itself is fine (since try-with-resource is RAII).

Where should I log that? In the worst case nothing is flushed to the file and the log is empty. The exception is not logged so you can spend hours to find your bug.

If things are so bad that you can't even log exceptions, your best bet is to terminate the process immediately and loudly (e.g. by throwing that exception after all). Of course, there are also asserts etc.

So RAII is completely useless for any kind of resources.

Really? Do you often have failures while releasing resources? How come that numerous C++ programs (to remind, still the vast majority of desktop apps are that) use the "useless" RAII heavily to manage all resouces?

Re:No Thanks!

[devent]

"This is by no means unique to RAII, but is a general problem with resource management. In Java 6, suppose you have a try-finally, and you call close() explicitly in finally - And that throws. What do you intend to do in that case, considering that there may still be a pending exception thrown from try? You can either suppress the one from close(), or let it override the one from try. You are arguing that the first is bad because it loses an exception; but so does the second, and it loses a far more important one!"

In Java it's very easy (and in C++ if not using the RAII). You just re-throw the exception to a higher level, maybe up to the View layer and show the exception to the user in a nice error dialog. With RAII that is not possible, because the destructor cannot throw an exception. So either you call a method to the outside in the destructor, or you just ignore the exception.

try-with-resource is not like RAII, because there the close() method of the AutoClosable/Closeable interface is called, which can throw an exception. The exception can be then retrieved and logged/presented to the user.

That is the nature of resources, they can fail at any time and with all resources you can recover from it in a graceful way. Except of course for memory resources, that is why RAII is only useful for memory, but in Java I have the GC.

"Really? Do you often have failures while releasing resources? How come that numerous C++ programs (to remind, still the vast majority of desktop apps are that) use the "useless" RAII heavily to manage all resouces?"

That is my personal opinion about destructors and RAII in C++. Of course you can use it, like you can use templates to calculate the fibonaci numbers at compiler time. But my personal opinion is that mixing memory management and resources management (what RAII is all about) is just stupid because of the fact that you cannot throw an exception from the destructor.

Re:No Thanks!

[shutdown -p now]

In Java it's very easy (and in C++ if not using the RAII). You just re-throw the exception to a higher level, maybe up to the View layer and show the exception to the user in a nice error dialog.

This does not answer the question. If your close() throws while the stack was unwinding, you have two exceptions - one that caused the stack to unwind and your finally-block to execute, and the other that was thrown by close(). Which one do you choose to report?

With RAII that is not possible, because the destructor cannot throw an exception. So either you call a method to the outside in the destructor, or you just ignore the exception.

As noted several times already, this is plainly false, and you can throw exceptions from destructors to your hearts content, catch them, and report them. The reason why it's not recommended to do so is because destructors happen to run when an exception is already pending, and there's no reasonable thing for the compiler to do with that other exception then, other than let the process die. If you always wrap points where destructors run in try/catch, you can throw from them with no problems whatsoever - same as in Java. If you don't wrap them in try/catch, then there's nothing analogous to that in Java (until v7), since it doesn't auto-run close().

"Destructors shouldn't throw" is not a language rule, it's a proper API design rule. It's very hard to write a library that correctly deals with objects which can throw when they are being released. Hence, the standing advice to the library authors is to not even try to do so, and the standing advice to the users is to not throw when cleaning up, and do "best effort" cleanup. This works wonderfully in practice.

That is the nature of resources, they can fail at any time and with all resources you can recover from it in a graceful way. Except of course for memory resources, that is why RAII is only useful for memory

Can you explain the difference between "cannot close a file handle" and "cannot release a block of memory", and why you can recover from one but not the other?

Also, how, exactly, do you gracefully handle not being able to close a file?

whats in it for users /Administrators ?

[Anonymous Coward]

Oh yeah more crappy toolbar of the week installers!

We have made a concerted Java from all of our machines as a toolbar install system wasnt what we had in mind
for business, it was easier/cheaper to purge the company of Java, its toolbar installers, and all its security flaws than have it on the machine and constantly deal with headache of support

No hit

[SuperKendall]

There has got to be a performance hit for "extending" garbage collection to files, sockets, and databases.

No, there does not. All that is happening is the compiler is writing correct code for you that is commonly used, so that you don't have to try and get it right.

god

[Anonymous Coward]

karen millen dresses sale
karen millen dresses UK
karen millen outlet
karen millen online
karen millen coats

fashion

[Anonymous Coward]

chloe fashion
authentic chloe outlet
chloe paraty python
Chloe online shop
shop chloe
chloe clothes
chloe bags

Hey guys

[Anonymous Coward]

.NET called. It says welcome to 2006.

Where is J7 Update 1 ?

[Anonymous Coward]

Where is this Java SE 7 update 1 at since you say it has been released?

It's not on Oracles Java download page:

http://www.oracle.com/technetwork/java/javase/downloads/index.html

Re:Where is J7 Update 1 ?

[mark_dot]

I noticed the same thing. According to http://blogs.oracle.com/java/entry/java_7_questions_answers, the fix is only in "current builds of JDK 7 Update 1". I imagine you can download it from the OpenJDK site somehow, but it does not seem that JDK 7 Update 1 has actually been released yet.

Scala is not dynamic!

[EvilRyry]

FTA:

A key feature of Java SE 7 is its accommodations for dynamic languages, which are becoming prominent on the JVM lately, thanks to the emergence of languages such as JRuby and Scala.

Scala is _NOT_ a dynamic language!

Fork-Join in Java 7 is a calamity

[cooper6]

The fork-join framework pushed in Java 7 as the "way to parallelism for applications" is seriously flawed, http://coopsoft.com/ar/CalamityArticle.html

New Java Developer Advice?

[jon3k]

I've been considering using some free time to play around writing Android apps for fun (I have no ambitions of trying to make any money at it) but I'm really nervous about the time investment with all the uncertainty around java. I have literally zero experience programming in Java, but I've played with C++ a little bit and several other higher level object oriented languages.

Can anyone give me some advice here? Is my time better spent just brushing up on HTML5 and Python?

Re:New Java Developer Advice?

[slim]

Very little of your time spent learning Java will go to waste.

1. It's a very marketable language, and looks good on your CV even if you don't end up using it
2. Most of the concepts are transferable

'Effective Java' is a good book. A lot of the advice applies to every OO language.

Re:New Java Developer Advice?

[bobaferret]

Everyone will have their own opinions, but here is mine. The nice thing about java is that you can run the code just about anywhere. There are great libraries out there for free to help you accomplish almost anything. The web is filled with examples and documentation for Java. Lots and Lots of enterprises use it for critical things. Java projects are fairly easy to maintain. Eclipse is a very capable editor, and does re-factoring pretty well. My understanding is that python can have some complicated version issues. Java has maintained backward compatibility fairly well. I like being able to develop on any platform in the same IDE and run it on any other platform w/o really worrying about compatibility issues. If you were talking about writing GUI apps as opposed to web apps, I'd suggest you might want to go someplace else though, as I've never had much luck with any of the visual form editors, and doing it by hand is tedious. JavaFX has some buzz around it, but I'm not going to hold my breath. I think there is a lot of potential with HTML5/and SVG canvases, XML/XSL, and Java which when using Saxon's XML libraries can do some crazy things. Java Servlets handle interaction with AJAX pretty well too.

Re:New Java Developer Advice?

[sourcerror]

"but I'm really nervous about the time investment with all the uncertainty around java."

It's very unlikely for Google to abandon Dalvik.
Microsoft paid for the same patents (to use it in .Net), and I expect Google to do so as well:

"Under the 10-year pact with Microsoft, the software company will pay Sun $700 million to resolve antitrust issues and $900 million to resolve patent issues, the companies said. The companies will pay royalties to use each other's technology; Microsoft is paying $350 million now, with Sun to make payments when it incorporates technology later"

Read more: http://news.cnet.com/2100-1014_3-5183848.html#ixzz1W4P96FFM

But the worst case is, that you learn some Java, and OpenJDK isn't going anywhere.

Re:Here's a reason why it is not on http://java.co

[Anonymous Coward]

Either that or they forgot to get the server password when buying Sun.

Java...Yawn. I care about the JVM.

[TheTyrannyOfForcedRe]

Java the language is dead to me. I could care less. What I do care about are JVM improvements that speed execution of the alternate JVM based languages: Scala, Rhino, jRuby, Clojure, Groovy, and to a much lesser degree Jython. The alternate languages are where all the action will be over the next ten years.

If you're a Java-only guy and haven't looked at Scala, run don't walk! You will love it, especially if you've played with any of the functional languages at Uni or on your own time.

I can only hope that someone will do a JVM Haskell and that the OCaml-Java project will mature into a stable platform.

Apple and Java SE 7

[monzie]

Now that Apple is moving away from Java and we dont have Java SE 7 downloads from Apple I do not see Java SE 7 downloads on Oracle's page as well. Is building OpenJDK on mac the only option left?

Question

[warrax_666]

What happens if, say, a close() fails during the destructor call?

Re:Question

[shutdown -p now]

Destructors should never throw (in C++11 this is further enforced by marking them noexcept by default). A well-written destructor will wrap any potentially-throwing operation into a swallowing try.

Note that this is not just a C++ issue. Generally speaking, any unconditional, unparametrized cleanup operation must not throw in any language, because, well, what is the caller supposed to do when cleanup fails? He's now holding a resource that he is, on one hand, obligated to release (since he's the owner), but, on the other hand, cannot do so because it's failing.

Wrong.

[sidragon.net]

One tool is better than another when it helps you accomplish the same task with less effort.

No.

[warrax_666]

An intermediate representation is being interpreted.

If you have only

[warrax_666]

simply scoped resources that is.

Lazy evaluation

[warrax_666]

Lazy evaluation has nothing to do with it.

Not even lambdas are needed, nor anonymous classes. All you need is the ability to instantiate objects (with state) dynamically (aka. "new").

Of course anonymous classes and (especially) lambdas make such an API much nicer to use.

Re:Java...Yawn. I care about the JVM.

[shutdown -p now]

I can only hope that someone will do a JVM Haskell

No can do. JVM doesn't guarantee tail call optimization for method calls, which is a must for Haskell (and most other FP languages). It's why Clojure has that ugly explicit "recur" hack.

Unfortunately, JVM wasn't really originally designed for languages other than Java, and it shows. They're trying to patch it up now with things like invokedynamic, but it needs far more than that.

Isn't this just a scoping trick?

[greed]

It's just scoping, really. You can do it in C++ if you like, here's one way to DIY (without the error checking):

#include <cstdio>
struct myFile {
FILE *file;
myFile(const char *name, const char *mode) { file=fopen(name,mode); };
~myFile() { fclose(file); };
};

Note that C++ only guarantees destructors are not run before something goes out of scope; exactly when after is Implementation Defined. So if a file MUST be closed (say, because you just wrote it and want to pass it to another program), you still need to invoke the close method explicitly.

Perl does much the same thing when a reference to an IO::File class or a filehandle gets garbage-collected. This Java feature just makes it part of the language syntax, rather than having to glom on yet another library.

Re:Java...Yawn. I care about the JVM.

[kirkb]

Ah, the impetuousness of youth. All of those "alternate languages where all the action is" are great toys ... until you need to get a job (or leave academia).

PS - Java ain't dead til netcraft says so!

The new Java 7 resource statement

[warrax_666]

The new Java 7 resource statement does something more useful here. It catches the exception and attaches the stack trace to the original exception (if there was one). If there wasn't a pending exception when the close failed, it actually throws.

That's not something which can be done in C++ because destructors (as you say, and of course, I knew before asking :)) cannot throw. ... but this also means that if a file fails to close() during normal RAII (perhaps because of a failing flush), there is absolutely no way to tell the user code. So you end up with subtly broken behavior.

In Java (7 or earlier) your code WILL get an exception and won't fail silently. ... and that is why RAII is broken (in C++ at least).

Re:The new Java 7 resource statement

[shutdown -p now]

The new Java 7 resource statement does something more useful here. It catches the exception and attaches the stack trace to the original exception (if there was one). If there wasn't a pending exception when the close failed, it actually throws.

That's not something which can be done in C++ because destructors (as you say, and of course, I knew before asking :)) cannot throw. ...

Destructors in C++ can throw. You're going to break a lot of libraries if you use them with destructor-throwing classes, but you can make it work if you really want. The language lets you do this, and the behavior is well-defined (even if you throw while unwinding). You can even check for std::uncaught_exception, and implement something like the logic you've described for Java 7 (i.e. only throw if safe), though you wouldn't be able to chain exceptions directly.

Re:The new Java 7 resource statement

[warrax_666]

I was basing my information on this:

      http://www.parashift.com/c++-faq-lite/exceptions.html#faq-17.9

but apparently I hadn't read it thoroughly enough :). Good to know that it's a least technically possible.

Still, even if it is technically permissible to throw in destructors, it seems too fraught with danger to actually contemplate seriously. I wonder if the standard fstream classes do something like this if running in "exception mode"...