Google Donates Windowbuilder, Codepro To Eclipse
h00manist writes "Google is donating Windowbuilder Pro and Codepro Profiler to the Eclipse project. 'Google acquired the software when it bought Instantiations, relaunching the Java graphical user interface building tool Windowbuilder Pro shortly after. Now the outfit has decided to donate both Windowbuilder Pro and the code analysis tool Codepro to the open source Eclipse project. Although Google has announced its intention to donate the software, it needs go through a rigorous filtering process to ensure that no intellectual property rights will be breached. Once those formalities are dealt with, it is likely that both Windowbuilder Pro and Codepro will tip up in the Indigo release of Eclipse sometime in June 2011.'"
Isn't Java getting on in years and in need of being replaced by something more modern?
no.
am more interested in CodePro. And what more it has to offer compared to YourKit
Eclipse PDE and Me
I don't like Java much myself, but I don't see it going anywhere. A staggering amount of java based (Android?) devices are shipped daily. Once the iPad version is released you may even see some folks switching (back) to it.
No. About 18% of all code written in 2010 was in Java. That's a huge percentage -- C had only 16%, and JavaScript (supposedly the hot new thing) is at 1.5%.
Believe it or not, Ruby hipsters on Reddit turn out not to be representative of the whole world.
Strictly speaking, it doesn't need replacement...
But - ORCL is hard at work at trying to alienate people away from java... ;-)
What do you think makes google want to donate the code to the public? Is it the insight that the market might be dying if Oracle doesn't finally get a clue...?
Meanwhile, people doing real low-level or time-critical work use assembler/C/C++, and people doing real high-level work don't go for a primitive imperative language which looks like C/C++ with training wheels.
Riiiiight. I wonder, where do people go who want to be able to find people to maintain their software for, say, a decade? Except for COBOL, of course... and that's going to get seriously expensive. (God, I really wish I was kidding about COBOL.)
Wake me up when one of the 'real high level' languages (whichever is your personal poison) has found a significant market and mind share. Meanwhile, I'll stick with whatever language fits the problem, instead of fitting the problem to my favourite language.
I suppose he is quoting the tiobe index because the numbers match: http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html - however, taking this as an estimate of the amount of code that has been written in a given language is a wild guess at best.
If I had to take my own wild guess off the top of my head, I think I'd give Java more than 18% of the code written in 2010, though. C and C++ added together get quite more popularity than Java, but I don't think their usage in the enterprise is comparable to that of Java.
That's because Java is so much more verbose ;)
Seems he was referring to the Tiobe community index at: http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html
Yes, it's controversial and probably a bit off the real numbers, but real numbers are near impossible to get. How do you want to know what people use in their closed projects? Nobody ever publishes that data.
Now if you check out a different chart, the language distribution of Github projects, you'd get a totally different picture: http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html , but it's also not very representative for the entire ecosystem.
This seems great, but it pisses me off that the lawyers have to get involved. It seems shockingly bad to me that we accept that there has to be lawyers too. That's how deeply they've embedded themselves into software licensing.
Training monkeys for world domination since 1439
Love Java. Love Eclipse. Sounds like my IDE of choice is going to get a lot stronger.
Errrr... Java debuted in 1995, and 2000 saw J2SE 1.3... it's almost 2011 now, does that count as a decade?
It most certainly does. C/C++, Java and C# are going to be around for quite a while yet: the odds are favourable for any language that has survived for long enough, and in which a sufficient number of people are capable if not proficient, whatever the technical merits of the languages in question (which shouldn't be scorned).
I was attempting being facetious about FuckingNickName's (what an elegant nick!) assertion that newer (or, in his/her/its terms, 'more high level') languages are always the better option. In engineering, you always have to deal with tradeoffs. Language elegance or expressiveness is far from the only factor to consider.
Isn't Java getting on in years and in need of being replaced by something more modern?
So says you. I'd guess that you don't actually work as a programmer.
Speaking as someone who started his programming career using a mix of C and Perl, Java is a pretty good balance between a systems programming and scripting language. With the increased speed of both hardware and the JVM since Java first arrived, it's got to the point where I can rarely justify using a language like C or C++ on the grounds of performance. As for paradigms, Java's implementation of OO is so much better than C++ (methods always virtual for example) - it's just a shame that Java's generics were bolted on later in a less than ideal way. In the real world don't really see functional programming taking off, but even if it does, Scala may offer the best of both worlds.
There's another aspect to this.
Oracle's fighting with Google over how they screwed over Sun. Sun's Netbeans Java IDE heretofore had the most innovative free Java GUI designer, the so-called Matisse. Matisse gave Netbeans a major edge vs. Eclipse, the other popular free IDE. And Sun sold services based on Netbeans.
Now, granted, Google's done a lot of stuff out of the goodness of their hearts. But when you have a chance to stick to someone (Oracle) who's suing you, and also get PR points in the process, why not?
I'm not a lawyer, but I play one on the Internet. Blog
... I think he means Android tablets.
Information wants to be beer.
assertion that newer (or, in his/her/its terms, 'more high level')
You are dense. LISP, Mathematica and Prolog are examples of "more high level" languages than Java. They all allow you to think about the problem rather than how the computer needs to process data because none of them are paradigmatically borne of Bjarne Stroustrup raping Alan Kay. They're all older than Java too.
And by Smalltalk you mean Objective-C right?
How we know is more important than what we know.
It's fear that their personal language of choice is in a decline. I'm a Java developer. When I hear people talking about languages like Python and Ruby I start to think about whether I'm going to have to learn a new Syntax if one of my "hip" clients comes to me and says, "Waddup yo. I wants you to write me a fly app in snake!!".
People are seduced by what's shiny and new. That being said, sometimes you have to kill a dinosaur so a manual can evolve.
I've been a Java developer for 11 years and I don't use development tools written in Java. While I am gaga over server side Java, I'm not a fan of interpreted code for client applications. I've always had fast machines and Jbuilder/Ecliples/Netbeans and all of the other Java IDEs have lasted for about 15 min with me whenever I have tried a new version. I can't think of anything else more irritating than having to wait for a menu on my development tool to come up. Coworkers always rave to me how _____ has improved and is fast. It has never been true.
I've stuck to Visual Slickedit all of this time. It is written in compiled code, is fast and has a ton of Java support. It also has a ton of support for many other languages so I can use it for everything and not have to learn a new tool.
A bit sad:
A Google employee got in touch with The INQUIRER to clarify that Google's donation to the Eclipse project does not include the Codepro Analytix software which it had acquired through Instantiations. The donation only includes Codepro Profiler and Windowbuilder Pro.
Ubuntu is an African word meaning 'I can't configure Debian'
I have modpoints but as no one bothered to reply to this post and point it's naive, fanboy inconsistencies then I felt the need to do that myself.
First, you've claimed the following:
If by "performance" you mean noticeable lag on your regular GUI operations then your comment is reasonable. The advances in the hardware world brought us in the last decade hardware powerful enough to run a GUI written even in the most bloated interpreted language you can find in a smooth enough way to not notice any lag any more. Yet, java still lags far behind languages such as C and C++ in performance, with some data crunching benchmarks running java at least twice as slow as the C++ program compiled with G++ and and also with the C program compiled with GCC. So, in the end what you said amounts to nothing more than claiming that writing programs in C or C++ instead of Java is rarely justifiable on the grounds of performance if and only if performance is irrelevant for the application you are developing.
Then you moved on to the OO paradigm, where you made another silly claim. You stated that
This statement is absurd. Do you happen to know what any C++ programmer must do in order to get all the methods in a class to be virtual? Well, he only needs to state that they are virtual. That is it. There is absolutely nothing in C++ that forces any class method to not be virtual. As a side note, not having a method to be virtual by default is a terribly useful feature, particularly in performance terms, as a method can be called without having to waste cycles checking up with a vtable to realize what method to call.
And just to drive the point home, which is that your comment regarding the implementation of the OO paradigm in Java Vs C++ doesn't make sense, let me just mention a single issue plaguing Java that C++ implements just fine: multiple inheritance. That, alone, is a big thorn in the side of the "Java's OO implementation is much better than C++", simply because it makes it just plain wrong.
Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
mention a single issue plaguing Java that C++ implements just fine: multiple inheritance
I had a good chuckle at that statement because in my experience, the *lack* of MI and operator overloading features is one of Java's biggest selling features. (I've worked at companies that had to make it a firing offense to use either in order to stop programmers from using these features.)
Both these features allow programmers to write elegant, stream-lined code... for themselves. Unfortunately, the guy maintaining the code who has neither the experience with the project nor the mental acuity of the original programmer to see the mental model that underlied the programmer's conception of the code then destroys everything.
In their defense, MI and operator overloading have probably protected many a programmer's job. "We can't lay off Jeff, he's the only one who will ever understand the code he wrote."
(Caveat: Of course it's *possible* to write maintainable code using these features, but it's like setting the speed limit to 120 mph - a lot more people *think* they can manage it than can actually manage it, and there's a lot of collateral damage along the way.)
Scratch that, name me one
Yahoo Store.
(That's not necessarily a recommendation)
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
Emacs.
It's not commercial, but it's arguably *very* popular.
Free Manning, jail Obama.
Meanwhile, people working "in the real world" embedded devices (from Refrigerators to DVD/BluRay players to Mobile phones) work in Java.
Maybe I should be ashamed, but I work with embedded devices (in C) and I have no idea how I could do the same work with Java. How do you even get a JVM to understand the specifics of the hardware ?!? Unless you meant Android which is a world in itself and where all the low level stuff is Linux anyway (in C).
Non-Linux Penguins ?
Hey, I was going for "Funny", not "Insightful"...
(Yeah, I get it.)