HN user

philjohnson

377 karma
Posts3
Comments82
View on HN

First thing is it was released much after BreezePDF was.

You could make the same argument with Adobe or any other PDF software. Why doesn't everyone use all use BentoPDF? Things like brand, and simply what shows up when they search on Google are factors.

Also, Bento doesn't have a desktop app a regular person can download. You have to download the GitHub. Non-developers won't do that.

Additionally, each tool is separate. It's not all in one editor. That's a UX consideration. BreezePDF, everything is in one editor interface. It added a lot of development complexity but makes the UX better in my opinion.

I tried Bento and some of their tools are very slow, cause of large downloads to the client. BreezePDF is much faster.

Good for them making an open source tool though. Lots of options out there and everyone can choose for themselves.

Thanks for trying it!

In what scenario was undo not working? If you can provide that context, I can dig into it more as to what wasn't undoing properly.

For text editing, I see the issue with that for some of the fonts. Fixing now

Sorry for the trouble!

Far from it haha

Some features took a longggg time to do, such as table extraction, text editing, and (surprisingly) preserving positioning of elements (text, images etc.) when rotating the page in the downloaded file - PDF specification has a different orientation system than the web, so this was very intricate to get correct.

A lot of PDF editors have tools that all work independently, meaning you have to use each tool separately. My decision to add all the features I did while keeping it in one editor was because I felt that was a better user experience, but I means that all features become intertwined, which added a ton of complexity managing that.

Thanks! Feel free to send feedback to joe@breezepdf.com if you get the chance to try it.

Regarding your concern, if a manipulation of the PDF doesn't meet the standard specification, it won't render properly in a PDF viewer as it is in the present day, let alone in 20 years. All PDF viewers/editors worth their salt adhere to the PDF spec. So as long as the PDF specification stays the same, anything that renders correctly now in a PDF viewer will render correctly in the future.

For something like compression, if the file reduces in size and the PDF renders the same (minus expected potential minor quality loss), then you have evidence right there that it worked successfully.

I built BreezePDF with PDF spec adhering libraries, so everything should be up to standards.

Let me know if that answers your question!

Yes, it definitely is. It handles everything from the basics like editing, signing, and merging to more advanced stuff like OCR, redaction, and digital certificates all in a clean and lightweight interface.

The desktop app is only 58mb and uses effectively zero CPU, so it's about as far from bloatware as you can get.

Shoot me an email at joe@breezepdf.com — happy to jump on a call and walk you through it before you get it for your company.

The MuPDF part is separated from the rest of the code as a completely separate file communicated to over web workers, so the separation means the rest of the code does not need to be open source.

Thanks! Looking into text removal issue, fixing now.

Yes, PDF data is never uploaded to the servers. It's the entire reason I created the project, after seeing the all the main results you see when you search on Google upload your data to their servers.

Understood. Yes, it was a major upgrade since last time, where then it only had maybe 6/7 features. Now it has nearly 40, plus desktop and a CLI.

I updated the intro, is if sufficient to be unmarked as dup? Thanks