Slashdot Mirror

Eclipse tries really hard to have good C++ support. I'm using Indigo still (I think), on my workstation. It does a few things well, but some of the automatic warning/error detection is bad bad bad...

As far as GUI editing, Qt's Creator is actually pretty great. Curious how it will integrate QtQuick going forward. As someone else pointed out, Eclipse actually has really good GUI editing capabilities for Java now, thanks to Google.

So, yeah. I think Eclipse + Plugins (and Qt Creator) is plenty sufficient for development on Linux. Is it as good as Visual Studio on Windows? No. But I'd MUCH rather develop a GUI-based desktop application for Linux using Qt 4.x than ever having to deal with Swing... and GridBag...

Once you learn that, and how to use GrdiBagLayout properly then you are 'away laughing'

heh ... laughing from insanity? I think this sums up my experience with Gridbag. I ended up switching to Mig Layout which was a paradise compare to Gridbag. It actually made Swing work fun.

Back in the day I use to refer to it as DoucheBagLayout.

Once you learn that, and how to use GrdiBagLayout properly then you are 'away laughing'

heh ... laughing from insanity? I think this sums up my experience with Gridbag. I ended up switching to Mig Layout which was a paradise compare to Gridbag. It actually made Swing work fun.

http://madbean.com/anim/totallygridbag/

Being I wrote my application in GridBag, I had to RFTM. I had no choice. The layout manager is needlessly complex. It's a pig to develop and debug. But don't take it from me. Mig was quick and easy, making debugging a trivial affair even for resizing elements. I rewrote my entire UI in less than a day and loved it as it made simple additions to the GUI a trivial affair. But hey, each to their own.

The main value of an IDE is having a Window Editor and being able to step through with the debugger. Although a window editor doesn't really help you very much in Java!! http://madbean.com/anim/totallygridbag/.

Speaking of GridBagLayout, this is the funniest animation I have ever seen...

http://madbean.com/anim/totallygridbag

Totally GridBag

Clustering *is* hard. And even the best application server in the world can't reduce that complexity. It can just try to not add any complexity of it's own.

Front-end load balancing, internal load balancing policy, cache settings, fail-over settings, setting up the LAN correctly... these are all *extra* things you need to do under a clustered J2EE server that you don't need to worry about normally. Clustering is hard

Having said that, I've been involved in commercial projects using clustering under Weblogic and JBoss. We have been able to get them going without too much trouble.

Also, some things J2EE allows some things in non-clustered mode that it explicity warns won't work in clustered mode. For example, objects in Sessions must be Serializable when clustering.

=Matt

First, familiariarity breeds increased effency. If you don't have the time to study all choices and train on something new then pick a familar one.

.Net is younger and has fewer choices when it comes to web framworks and external libs which some people prefer. This blog enty explains it better than I can: http://javablogs.com/ViewEntry.jspa?id=31449

Java is more of a Language For the Masses than C#/.Net. While us alpha-geeks like Languages For Smart People that does not make them better, espcially when we have to work with less smart people on your team. Much more on this at: http://madbean.com/blog/20/.

Interwoven's press release regarding their patent states the following 6 claims (of 13 claims). I have quoted each claim as described in their press release, and then shown how CVS can be used to show prior-art over the claim.

(And it only took me half an hour and a little googling to work all this out...)

(read above blog entry for details)