Java

IntelliJ IDEA on OS X

Driving me nuts.

If you are a developer on OS X and you are customer of JetBrains using IDEA the Java IDE, it is a cloudy year for you!

There are two critical bugs that haven't been fixed in over 6 months since being reported to JetBrains. IDEA enabled my fulltime switch to OS X and now it is unusable after 4 - 5 open files or half a work day. Whichever comes first.

Check it out:

Without Regard for the People Who Care

John Gruber of Daring Fireball fame, who I have mucho respect for, linked to an article about how the Java support in the lastest version of Mac OS X is terrible. He then makes a very irresponsible statement:
"I fail to see why anyone (other than Java developers themselves) would care."

The problem with this statement is that you should care. Why? Well, because you are a Mac user. It will take a bit to explain. Humor me.

There are many upon many businesses out there that support the Mac platform ONLY because their Java applications will run on a Mac. But this isn't the complete reason. Hear me out.

Now, these businesses aren't Google, Microsoft, or IBM. You probably haven't heard the names of these businesses, let alone the names of the software they provide. They certainly aren't household names, and your mom and dad aren't using their applications. But they do represent a significant base of development energy. These are the guys that make it possible for the little guys and the medium guys to do business.

EclipseUML by Omondo, a Partial Review

I was just trying out the latest state of UML tools for Eclipse and gave a look at the apparent industry heavyweight, Omondo. Since the beginning, they always seemed like they would end up on top.

My initial impression was that this was a quality product and one that I would actually consider buying at work. For home use, I would just stick with the free version. But then I ran into some trouble.

AttachmentSize
move-class-buginess.mov6.46 MB

Overly Complicated ORM

Why is it that in Hibernate I have to specify the mundane? Isn't a project like this supposed to save me from the mundane? Then why do I find myself having to state that the column named ProjectName in PROJECT is mapped to the methods setProjectName and getProjectName in the Project javabean? *And* Why do I have to specify this in verbose XML files? Hibernate is not alone in this regard. Top Link and others force the same mundane tasks on you, in different ways. I'm only picking on Hibernate because of its popularity.

Syndicate content