iText at Java One

These are the people representing iText at Java One:

Valérie, marketing:
Paulo, development:
Michael, sales:

Google Analytics — September 2012

Looking at the sales for 12Q3, I'm very proud of what we've achieved at iText. We started to invest in people and development in the Summer of 2011, and this translates in better sales in the Summer of 2012: the billed revenue for the iText Group (ISB + ISC) in 12Q3 was 124% of the billed revenue in 12Q2, 235% of the billed revenue in 11Q3, and 60% of the total billed revenue in 2011. With one quarter to go, the volume of sales for 2012 is already 1.45 times the volume realized in 2011. We've been growing for 11 quarters in a row.

JavaOne: an alien’s view – day 3

Mark Stephens from IDRSolutions invited Paulo and me to have breakfast at Lori’s dinner. We took the breakfast special: two large cakes, two slices bacon, two sausages, two eggs any style & hash browns.

A lot of our customers are getting PDF’s dynamically from server to client using NetBeans and Glassfish/Tomcat. I decided to sign up for the Netbeans Community day and the Glassfish unconference to find out more about GlassFish.
I was happy to chat with Jim Weaver, Java/JavaFX Technologist at Oracle, and briefly spoke to Stephan Janssen, my former employer.

JavaOne: an alien’s view - day 2

Coming out of my hotel I bumped into Geertjan Wielenga, Oracle Principal Product Manager on the NetBeans Team.
I’ll probably see him again on the Netbeans Community day on Sunday.

JavaOne 2012: an alien’s view - day 1

iText is exhibiting at JavaOne this year. 95%, or maybe even 98% of JavaOne attendees are male. That, and the fact that they’re of course all programmers, makes me stand out a little.

Good candidate for a favorite quote

As read on Stackoverflow:

iText 5.3.3 — XML Worker 1.2.0

The technical roadmap for 2012 consisted of 4 goals:

  1. Digital Signatures— Make iText ready for PAdES and PDF 2.0: done!
  2. XML Forms Architecture— Add support to flatten dynamic forms created by Adobe LiveCycle: done!
  3. Android— Make an Android port of iText that is better than the (barely legal) ports created by third parties: done!
  4. Cloud— Make iText "Cloud-ready": done! (Some of our customers are using iText on GAE.)

Goal number 3 and goal number 4 were already presented at the iText Developer Summit in March.

Things to consider before you publish your code as F/OSS...

So you've written a piece of software that is going to change the world.
What are you going to do? Here are some options:

FOSS and liberal licenses

I've just read a great article entitled Open Source, Software Hygiene and STDs on the Outercurve blog. I wrote a comment, but I don't know if I submitted it correctly. In case I didn't, this is what I wrote:

Measuring popularity

People keep saying that the Alexa and Klout metrics are worthless. From a purely scientific point of view, they have a point: the algorithms to calculate the world-wide ranking of your site or your world-wide influence are bound to be suboptimal. It's madness to think that you can 'measure' something like 'influence'. Yet that doesn't mean the metrics are worthless! Let's see how I use Alexa and Klout:

Syndicate content