Just a quick reminder: european developers should not forget the NetBeans Day in Zurich, next Saturday. It's a FREE event and you will have the chance of knowing all the things that you always wanted to know about NetBeans, from the mouth of evangelists, the NetBeans staff and other developers.
In the latest week I've written a few times about the world of Java imaging. I've anticipated one of my points, that is we lack an "unified community" dedicated to imaging Java programmers, which spans over all the Java imaging technologies (Java2D, JAI, others), focusing only on imaging themes (e.g. dropping rendering stuff in Java2D).
Starting up a community is not easy.
When your application becomes large, and it starts requiring a non-neglectable compilation time, it's high time you profiled your environment.
Now, compiling blueMarine on my MacBook Pro requires more than 2 minutes, so I started thinking about tuning the environment. As usual, tuning starts with a measurement.
Paul Buchheit criticized Java imaging APIs as they require "closer to 100 lines of Java" just to do a simple image resizing, that in Python can be done in three lines:
i = Image.open("/tmp/c.jpg") i.thumbnail([220, 133], Image.ANTIALIAS) i.save('/tmp/c-thumb.jpg', quality=90)
He also criticized the over-u
The news is circulating since a few days, but I was suprised to not see discussions about it but in a few forums.
(the title of this blog is related to the one of my previous post...)
I don't know whether the expression "Buridan's Donkey" has the same meaning in english as in italian (I've just recenly discovered that the latin "qui(d) pro quo" has nowadays different meanings in english and romance languages).
A few days ago I blogged about the way we can now deliver a more robust .deb installation of our application on Ubuntu Feisty Fawn.