4 ms·
10 Years of HexaPDF
- 4silvertooth 2y ago>Another thing that was imported to me was - and still is Typo in the article word imported should be important.
- gettalong 2y agoThanks and corrected!
- poulpy123 2y agoThere is a side note that really shocked me: > Normally one would need to pay ISO to get a standards document. What is the point of a standard that is not pulicly available ?
- andai 2y agoA lot of regulations exist largely to make it more difficult for individuals and small companies to compete. I don't know if that's the explanation here (maybe there's good reasons for it?) but it's the first thing that came to mind.
- 082349872349872 2y agoAccording to https://www.iso.org/standard/51502.html https://www.iso.org/standard/51502.html the standard would cost ~$250, so basically 1 hour of dev time. I can't think of anything competitive I might do as an individual/SME in this space that would come in at under 2 weeks, so compared to actually doing the work, paying for the standard would be in the noise. Keep in mind that ISO traditionally dealt more with industrial standards; eg something like https://www.iso.org/standard/40447.html https://www.iso.org/standard/40447.html costs ~$180, but I doubt anyone who'd be attempting to compete in the "Apparatus for industrial gamma radiography" world would consider that expense as any more burdensome than buying office consumables.
- andai 2y agoOne hour of dev time? Are you paid half a million a year?
- 082349872349872 2y agoI have been in the past; currently I consult part time, so that's both (a) fully burdened, and (b) not the rate I'd choose if I still wanted 1'800 hours/year. Chop it down by a factor of 2-4, and the question still remains: is $250 significant compared to the amount of work you're going to have to do to be competitive in the PDF-document processing space? (for quick hacks, reverse engineering is good enough. you only need the standard once you're processing enough client documents that you need to know all about the long tail of possible but unlikely constructs your code may encounter, after all)
- andai 2y agoThe answer is yes. It's a lot of money for what it is. ISO is the international standards organization. A software developer in Indonesia earns $500 per month. Half your salary for one document is indeed a lot.
- 082349872349872 2y agoWow. True; it probably doesn't help that ISO HQ is in Geneva. How much is 500g emping for you all? From a swiss source it's $25. That might give us a rough idea of price differentials... [This is all moot though, because the PDF standard is available gratis.]
- gradschoolfail 2y agoISO docs seem to me to be one of those club antigoods.. paying for them doesnt necessarily make them less destructive (dependent on timescales tho, i do believe that standards are an unalloyed good if they are patched with a timeconstant low compared to what standards bodies consider optimal)
- RadiozRadioz 2y agohttps://www.iso.org/footer-links/frequently-asked-questions-faqs/general-faqs.html https://www.iso.org/footer-links/frequently-asked-questions-... "Developing, publishing and maintaining ISO standards incurs a cost, and revenues from selling them helps ISO and its members to cover an important part of these costs. Charging for standards allows us to ensure that they are developed in an impartial environment and therefore meet the needs of all stakeholders for which the standard is relevant. This is essential if standards are to remain effective in the real world."
- tonyedgecombe 2y ago>Charging for standards allows us to ensure that they are developed in an impartial environment I don't think the PDF standard was developed in an impartial environment.
- dotancohen 2y agoPDF? I'd agree about that "open" document format that MS Word use (the standard literally states that some things should be implemented "like MS Office does") but not PDF.
- aredox 2y agoHere are the members of the ISO Technical Committee 171 (ISO/TC 171), Document management application, Subcommittee SC 2 who is in charge of developing and updating PDF standards: https://www.iso.org/committee/53674.html?view=participation https://www.iso.org/committee/53674.html?view=participation
- kjksf 2y agoYou should be able to see when someone is gaslighting you. They charge because they want and can. The above justification might apply to some of their standards but certainly not to PDF. PDF was developed by Adobe. They make lots money selling PDF tools and licensing PDF software. PDF didn't have to be a standard. It could be a proprietary format. Adobe wanted the adoption of PDF so they made PDF a standards so that they can sell more PDF tools. It didn't have to an ISO standard. Adobe could have released it as an open spec with some sort of permissive license. Adobe wanted it to be ISO standard to piggy back on "respectability" of International Standards Organization, to buy the impression that it's an open standard. But ISO makes money by selling standards so we ended up in this situation when the spec for "open" standard that Adobe wants to be adapted costs $100+ to buy. I guess Adobe at some point figured out this is stupid and made the spec available for free.
- andai 2y ago>commercially available library Are there any examples of this? How do you monetize a DLL file? One time purchase and later upgrades? It seems like you'd have to put it behind an API and charge for usage, though I don't have a good overview of what the other options are.
- alemanek 2y agoThis used to be much more common. I worked on a product in 2004 that licensed a library around providing a nice SDK for different payment processors. Effectively making it super simple to switch or route payments to different processing gateways. We paid on a per domain basis and also paid a yearly maintenance fee to get updates. Nothing stopped us from just using the library in ways that violated the license but we didn’t. The threat of lawsuit is an effective deterrent if the ethical concerns aren’t. In my experience for B2B the people that are going to steal from you were never going to pay anyways.
- tonyedgecombe 2y ago>In my experience for B2B the people that are going to steal from you were never going to pay anyways. I used to think that but eventually the evidence pointing to the opposite was overwhelming. It wasn't just small companies either, some of them you will have heard of.
- gettalong 2y agoThe library is dual-licensed as AGPL plus a commercial license. So everything is in the open and can be tested and tried out under the AGPL. Once the library is used in a commercial context, you nearly always need to buy the commercial licenses to stay compliant. This is how it generally works. What the commercial license does is a different thing. You could charge once OR once and for every upgrade to an (arbitrarily defined) new major version OR each year via a subscription OR ... It is really up to you and how you want to handle this.
- pabs3 2y agoThe AGPL is pretty easy to comply with in a commercial context even if you are using it as part of a SaaSS product. Just either use the code unmodified, or release your modifications to customers, or to the public in general. Do the businesses buying commercial licenses just not understand the AGPL license? or are their development processes not rigorous enough to ensure compliance? The AGPL includes some easy ways to be forgiven for accidental violations, so that should not be a problem in almost all cases. So only deliberate non-compliance should be an issue.
- aidog 2y agoNote: This is by the author of the popular kramdown markdown library.
- nona 2y agoI looked at HexaPDF several years ago, and really liked what I saw. However, my only major issue with it was the difficulty (back then) for laying out PDFs. Most people I worked with found it a lot easier to layout in HTML/CSS and converting to PDF from there; so we went that way. If I were to look for a way to manipulate existing PDFs I'd definitely use HexaPDF. I'll re-evaluate its (more recently) improved layout capabilities again and consider it for my next project. And I also think the dual-licensing model is fair. Congrats on the 10-year/1.0 milestone.
- gettalong 2y agoThanks! I agree that laying out PDFs could be made easier by using a declarative mechanism instead of coding. However, I'm still not sure what the best way would be to do that. Using HTML/CSS for this and doing it right would entail implementing something like PrinceXML... With the current layout model you have the possibility to implement price layouts, like the one needed by Swiss QR bills (see https://x.com/_gettalong/status/1748823670368117154 https://x.com/_gettalong/status/1748823670368117154), or just define the general layout and let HexaPDF decide the final position (see https://hexapdf.gettalong.org/examples/pdfa.html https://hexapdf.gettalong.org/examples/pdfa.html). If you have any ideas, how laying out PDFs could be made simpler, I'm all ears!
- arresin 2y agoHow did you go from HTML to PDF?
- pabs3 2y agoWhat do the terms of your commercial license allow customers to do and what do they prevent them from doing?