

It has more features, it has a bigger team working on it (we are 2 now), it’s built trying to follow best practices from Joshua Bloch in Effective Java and Robert C. What are the advantages compare to the pdfsam-console? PDFsam itself was/is working pretty well but maintenance was/is a bit of a hell so I made the choice, I started to rewrite the pdf manipulation logic with 5 years of experience on my shoulders and trying to keep a close eye on quality and best practices. I realized at some point that some of the design choices I made were unfortunate and the code base wasn’t inline with 2010 software development standards.

Ok, as many of you know I’ve been working on PDFsam for 6 years now and I realized at some point that the pdfsam-console (the component providing pdf manipulation capabilities to PDFsam) has some… mm… limitations. It’s a PDF manipulation layer written in Java. You are probably asking “What the heck is Sejda?”.

Great news! After more then one year of development today we released Sejda!
