Peter Hendriks - All Comments

re: Java 7 and the Elvis operator

Doug Hammond — Tue, 05 Jan 2010 10:14:01 GMT

I'd also like to see this:

for (Item i ?: list)

Should be self-explanatory.

re: Java 7 and the Elvis operator

Elias Mårtenson — Wed, 30 Dec 2009 13:51:34 GMT

The proposal is not only ugly, it's rather useless if not counter-productive.

If you are doing these kind of checks a lot, especially in chains like in the above example, chances are there is something wrong with your design.

re: J-Spring 2009, full of surprises

peterhe — Sun, 27 Sep 2009 15:58:09 GMT

Hmm, interesting to see these kind of pinpoint reactions to isolated out of context "anti Netbeans" sentences, half a year later. Also, please don't call me (or Karsten Lentzsch) an idiot without anything more than a link to generic Netbeans propaganda. I will remove such comments in the future.

First of all, the above comments are not meant as an attack on Netbeans RCP as a platform. I have the "Netbeans RCP" book at home, I built some examples with it, and it basically is all just a bit easier and nicer to use than Eclipse RCP. Of course, some things are better in Eclipse RCP too, overall, there is no clear winner when it comes to basic use and capabilities today.

Sure, Netbeans is used a lot as well, and would still exist based on community effort. Without the strategic leadership and contributions by Sun, however, Netbeans will not able to stay current for long, in competition with Eclipse, .NET and other solutions. As I see it, there is no other software company that would take over strategic leadership and/or the major contributing role of Sun. If you would know which company would, please tell me. Likewise, I would think that Eclipse would have major issues if IBM would decide to step out. IBM however, based all its products on Eclipse, ranging from Websphere to Lotus to Jazz.

I genuinely share the frustration of Lentzsch that Sun is dropping the ball on important desktop capabilities like a basic application framework and databinding. Although Karsten warned in April that JSR 296 was dead, Sun officially dropped it only weeks ago. It is evident that Sun cannot power innovation in both Swing and JavaFX at the same time, and is choosing the latter. At the same time though, Eclipse RCP is moving forward with data binding, forms support, enhanced web browser integration, provisioning and proxy/security support. Microsoft is picking up the pace with WPF and Silverlight. And Swings best option is still a one-man job performed by a crazy German that you guys call an idiot for speaking reality.

re: J-Spring 2009, full of surprises

Jason — Sun, 27 Sep 2009 09:23:03 GMT

"Where Eclipse RCP is used by major companies, Netbeans RCP is not used as much for very large applications. "

Only an idiot could say that. http://platform.netbeans.org/

re: J-Spring 2009, full of surprises

Tom — Wed, 23 Sep 2009 23:03:12 GMT

Hmm. Whether or not IBM had bought Sun, NetBeans would continue to exist... since it is an open source project that many VERY large companies depend on!

re: Injecting JSR330 into JSR299

Gurkan Erdogdu — Wed, 09 Sep 2009 11:43:59 GMT

Apache OpenWebBeans implementation samples are fully complicant with JSR 330 API. You can take a try if you wish :)

re: Java 7 and the Elvis operator

Juliano — Tue, 01 Sep 2009 01:50:24 GMT

?:| Well, its one for the money,

Two for the show,

Three to get ready,

Now go, cat, go.

re: Java 7 and the Elvis operator

Sat, 29 Aug 2009 22:44:54 GMT

how about

name = (g.members[0].name)? "Anon"

All or nothing operator.

re: Java 7 and the Elvis operator

Chris — Sat, 29 Aug 2009 17:23:09 GMT

@MeBigFatGuy I like that idea! Groovy is nice with the ?. syntax, but you're right, a lot of times you're just traversing down to the last property/method so why not have a shortcut syntax for that.

Injecting JSR330 into JSR299

Peter Hendriks — Wed, 05 Aug 2009 19:31:06 GMT

Last week, I blogged about Guice 2.0 and the state of Java EE 6 dependency injection: JSR299 , competing

re: The user interface beyond Star Trek

Maarten Metz — Thu, 11 Jun 2009 06:49:18 GMT

re: Why tools matter

peterhe — Mon, 04 May 2009 07:01:23 GMT

Great points Erno! I fully agree with that: you still need to know your craft, no matter how good the tool is (a great hammer does not make a great carpenter), and you need to know the tool to effectively use it. I'll try to update this in the picture tonight using some advanced imaging tool (paint.net).

re: Why tools matter

Erno de Weerd — Mon, 04 May 2009 06:01:08 GMT

IMHO there are two dimensions missing in your pictures. You could have a great tool but in the hands of a fool it would have to be an awsome tool to protect you from the fool. Two, you might have a great tool but when used at the wrong time or improperly used it might give you a false feeling of greatness. (Forgetting to label your builds in Source Safe or reverse enginering class diagrams and pretending you now have your documentation covered) (No, I am not implying Source Safe is a great tool ;-) ) See: www.google.com/search

re: J-Spring 2009, full of surprises

peterhe — Sun, 26 Apr 2009 11:54:55 GMT

The reasons Karsten mentioned were maturity and user base, where Eclipse RCP is better documented, more examples, and more users. Where Eclipse RCP is used by major companies, Netbeans RCP is not used as much for very large applications. This is especially true in the German market where Karsten is coming from.

Also Karsten took into account the position of Sun as a company at the time. When Sun would be bought by IBM, this would mean the end of Netbeans (IBM is a heavy user/inverster in Eclipse). Now that Sun is bought by Oracle, Oracle has three tooling stacks, and will likely need to make a cut as well.

Info Support does both Swing and Eclipse RCP projects. Eclipse RCP has impressive tool support for the platform when building modular clients (using plug-ins), but can be a daunting platform to use because everything works using extensible abstractions. Swing is built-in into the Java runtime, and has better features for custom graphics.

If you are looking for tool support for drag-n-drop design tooling, take a look at WindowBuilder: www.instantiations.com/.../index.html

They offer great tools for both SWT and Swing, with a much more flexible tooling strategy than the Netbeans designer uses.

If you'd like to talk some more about this topic, feel free to drop me a note using the "Contact" option on my blog, and we can discuss this by e-mail or phone.

re: Google AppEngine for Java: the cloud keeps getting bigger

peterhe — Sun, 26 Apr 2009 11:36:48 GMT

Thanks for spotting the typo, fixed it.