News for hackers. Stuff that matters.
Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by sek on Friday March 30, 2012 @08:42AM (#3775650)
Why don't they start now and build Java 2.0 from ground up instead of Java 10 for 2017?

That would be way faster and they learned so much by now to make a great successor. Who wants a Java 1.x in 2040?

Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by francoisdevlin on Friday March 30, 2012 @09:40AM (#3775851)
Because they learned from netscape's mistake, that's why.

http://www.joelonsoftware.com/articles/fog0000000069.html

Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by InclinedPlane on Friday March 30, 2012 @05:14PM (#3778119)
That article is an incredibly useful warning against the temptation for casually taking code rewrites, but it's incomplete.

Sometimes full rewrites are necessary and good. The trick is doing it correctly. Rewrites are riskier, more difficult, and require more development resources than greenfield development. More so when you consider that you can't just abandon the old code until the new code is mature and has proven itself.

Most people do rewrites the wrong way, and they get into trouble, but that doesn't mean there isn't a right way. There are many examples of unsuccessful rewrites in history, but also many examples of highly successful ones.

Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by lhnz on Friday March 30, 2012 @09:56AM (#3775923)
"You are wasting an outlandish amount of money writing code that already exists."

On the contrary, there has been a number of times that I've completely rewritten some code to use a framework or library that was already battle-tested and more fully-featured than the previous effort. I ended up saving myself from writing code that already exists.

Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by anonymous on Friday March 30, 2012 @03:28PM (#3777673)
Right, but you're one person and you're redoing the plumbing.

At this point oracle can't rewrite Java. If they don't support the current programs, nobody would use it, if they do, they will really be rewriting code that already exists.

Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by moonboots on Friday March 30, 2012 @03:06PM (#3777561)
The netscape rewrite became Firefox.
Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by shangrila on Saturday March 31, 2012 @04:10AM (#3779770)
Yeah no kidding. That's one thing people seem to forget about that Joel article ... the new code base he's mocking went on to become the only browser capable of taking on Microsoft's juggernaut for many years. It was faster & better than everything else out there. Eventually the only thing capable of overtaking it was WebKit ... another from-scratch code base!
Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by nknight on Saturday March 31, 2012 @06:35AM (#3780004)
That new codebase was iterated on for five years before a viable browser was released, and two more before Firefox 1.0 appeared.

The history of the WebKit codebase stretches back as far as Gecko. The earliest KDE HTML work I can definitively establish is in 1997. We got Konquerer in 2000, but Safari didn't emerge until 2003.

5-7 years before something other than IE could again be competitive... Do you really think that disproves Joel's point? I think it may be quite the opposite...

Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by sek on Friday March 30, 2012 @10:13AM (#3775991)
I didn't say they should rewrite everything, but to make a new Java version with backward incompatibilities. Drop a new 1.x version on java for decades can't be the solution.
Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by protomyth on Friday March 30, 2012 @10:38AM (#3776113)
To be fair, if you were researching computer languages and rewrites, you would be looking at Python 3.0 and Perl 6.0. I believe both will be successful in time, but for business planing, it looks like a lot of problems and a slow evolution will work better. Oracle is pretty comfortable with the slow evolution route.
Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by kbd on Friday March 30, 2012 @11:04AM (#3776247)
There's no way I'd put Python 3 and Perl 6 in the same sentence.

Also, IMO there's no chance of Perl 6 being successful in time (which makes me sad, because 10 years ago or so I was really hopeful about it).

Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by protomyth on Friday March 30, 2012 @11:29AM (#3776399)
If you are some manager in a big company and looking at the press, there is little distinction. In fact, more stories have been posted about Python 2.x to 3.x conversions (mostly because Perl 6 is not a story). Heck, I would imagine a couple of people on HN have run into the "can't use Python 3 because it isn't compatible with anything"-meme. Carefully considered logical analysis with realistic risk mitigation gets trumped by headlines in ComputerWorld and InfoWorld quite often.

I still have quite a bit of hope for Perl 6. I use Perl 5 as my goto short scripting language. I really want it to work.

Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by kamaal on Friday March 30, 2012 @10:23PM (#3779109)
You are not getting it, Perl 6 is not designed as a successor to Perl 5 but as a Age proof Perl.

Think of it like pg called a hundred year lisp language. Perl 6 might be the age proof Perl language. When you have such and ambitious goal the time taken is worth to fulfill it. Larry wall figured out quite a while back evolving Perl 5 may fix some warts but it won't solve the larger problem.

The larger problem today is doing language extensibility sane-fully. There are no C based languages that are as much extensible as a Lisp based languages. Perl 6's larger aim is to solve that. While retaining the 'Perl factor'.

Re write is inevitable if you have to solve this problem, no matter what joel says you have to rewrite a few things to fix them. The incremental path is too slow and you will loose out on time while somebody eats your lunch.

Perl 5, Python x.0 and Ruby x.0 series are all great languages but eventually on the very long run they will be plagued with the same technical problem every language runs in to. Providing sane ways of extensibility without bloating too much.

IMO Perl 6 will do well, for the same reasons Lisp has done well.

Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by chromatic on Saturday March 31, 2012 @01:30AM (#3779473)
When you have such and ambitious goal the time taken is worth to fulfill it.

After almost twelve years of rewrite after rewrite after rewrite, it's no wonder people stop caring.

Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by kamaal on Saturday March 31, 2012 @02:04AM (#3779551)
Well, more than anybody else you know it well why most of the failures happened.

But for others. I can understand the obvious disappointment. But Perl 6 is designed such that without many of those failures we couldn't have figured it out earlier what it would take to build Perl 6. Perl 6 has a mutable grammar, which means it should be written in itself. And this created a huge problem, because you don't have ready tools in hand to build such a thing. Many of them had to be built from scratch. And people failed many times exploring strategies doing that. Some people got ill, some people lost jobs, and projects like this which span a lot of time and require volunteer effort without much funding takes toll on people.

In many ways there was a lead, Lisp is so extensible because its written in itself. We really should have understood this from history. But achieving that in a non homoiconic language was difficult and required thinking in direction totally new to C based languages.

But great things have come out of it. Audrey's Pugs taught us so many things. And as she says, the 'Perl 6 on CPAN' thing started long back. Moose has become a very awesome tool for OO programming. Other things borrowed from Perl 6, things like given/when have shown a way to Perl 5 for evolution. Devel::Declare showed a new way to do syntax experiments outside core without using source filters. And many great things have come out of it. Its difficult to imagine how Perl 5 will likely evolve over time.

A few years back none of us could have seen Devel::Declare or even Moose coming. I can only imagine how Perl 5 is going to evolve over time.

Lastly I would say Rome was not built in a day. Perl 6 will take time, but it will come out in some years to come.

Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by chromatic on Saturday March 31, 2012 @01:02PM (#3780797)
Perl 6 is designed such that without many of those failures we couldn't have figured it out earlier what it would take to build Perl 6.

Sure, but those don't account for the past four years of failures. What I see is a pattern of overwhelming desire to throw away code just as it's in danger of becoming useful to actual users.

Phrased from a different angle, the reason we wanted monthly releases was not because monthly releases are interesting in and of themselves, but because they could deliver regular (if incremental) improvements to actual users on a predictable schedule.

Forking Rakudo into an all-but-abandoned master branch and doing monthly releases off of that branch hews to the letter of the idea of monthly releases while violating the spirit of those releases. I understand the reasons why it happened, but that sort of decision has happened often enough in the project that it's a habit--if not culture.

Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by protomyth on Saturday March 31, 2012 @01:11PM (#3780830)
In the context I was talking about it really doesn't matter what I think as I am not a decision maker at some big company. Calling something the N+1 version tends to make people think it is the next version and not a proof of concept. It does matter what is said in the trades these people read:

for example: http://www.infoworld.com/search/google?cx=014839440456418836...

Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by sek on Friday March 30, 2012 @10:45AM (#3776146)
I think Python 3.0 is really well executed. With such a big ecosystem this takes a while, but when you wait too long somebody else eats your lunch.
Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by noselasd on Saturday March 31, 2012 @06:12AM (#3779975)
Because backwards compatibility matters more. There's anyway many other alternatives to Java if you need something else but still use the JVM.
Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by mahmud on Friday March 30, 2012 @08:59AM (#3775699)
by the time the rebuilt java2.0-NG reaches stability it will be 2017, or whatever.
Re:Java 9 with GPU processing, Java 10 will be all-OOP witho... by soc88 on Friday March 30, 2012 @05:11PM (#3778106)
Isn't that what Scala already does quite successfully for a while now?