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?
Excuse me, but please get off my Pennisetum Clandestinum, eh!
am more interested in CodePro. And what more it has to offer compared to YourKit
Eclipse PDE and Me
Of the market by using Smalltalk. Its great to Instantiations still in business, and focused on Smalltalk. I find it very perplexing that Google bought the Java tools from them while leaving the Smalltalk business and dev folks behind that used Smalltalk to create these Java tools. When folks finally get to the real world of Smalltalk and its power, and Java is realized for its weaknesses maybe we'll all get back to the real work of creating real tools for real people with real problems to solve.
We haven't seen a company more keen to take control away from you since IBM. If there's one thing Google will not do, it's create something for real people to solve real problems.
At best, they'll offer to solve sufficiently simple problems for you. Give a man a fish.
It's Java. That's where my interest ends, especially after Google's own fight with Oracle.
Now if you do integrate a couple of decent C profiling tools, I'd be interested.
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.
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
Why is it that every time an article related to some technology built on Java ends up on Slashdot there's 3 comments regarding the product and another 100 comments with evangelical morons still questioning the currency of the Java language? I want to actually know more about CodePro and WindowBuilder not irrelevant opinions on why Java sucks and they should rather just use brand X where X is any language not Java. Java is used almost exclusively in all major enterprise applications where I work on AIX, HP-UX, Solaris, Linux and Windows operating systems. Scripting languages like Groovy which get interpreted as java bytecode make it even more attractive as you don't have to write "Java" yet still get all the cross-platform goodness that comes with the JVM.
And by Smalltalk you mean Objective-C right?
How we know is more important than what we know.
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.
Oracle will be anxiously anticipating their handout in the coming weeks.
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 see that WindowBuilder Pro can be used to create GWT GUIs.
Serious question: Does anybody out there use GWT? I went searched for good showcases and didn't find any good examples. If anything the examples tell me to stay away from GWT.
This is the first post.... After starting eclipse. ;)
Ignoring the expected language-wars comments for a second, this is actually really cool. These were solid, expensive pieces of software that will now reach a wider audience. Netbeans (which I don't use much) was always better than Eclipse in at least this one way - visually building GUIs. It will be nice to see Eclipse achieve parity or exceed its primary free rival in this regard, finally.
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)
...no love for IDEa?
Netbeans developers claim that fowl play is at the heart of the latest Eclipse GUI code and existing steps in that direction may have been responsible for Eclipse's legendary slowness. The developers' claims stem from their exploratory search of the donated code, where a new GUI code a class called "Beak" was found to contain methods such as doPeck(), doSquark(), doScratch(). Further suspicions were raised when an existing Eclipse non-GUI class called Headless was found to be extending Thread class while overriding the run() method.
Apache foundation members were heard murmuring that these revelations should be no surprise given the way the Eclipse Foundation members voted in the recent JCP vote.
Is this the same WindowBuilder Pro I used back in the mid 90's on a Win 16 Smalltalk/V system? What's next great leap forward, VisualAge?