Most extractors are either fast but lose structure (markitdown, pymupdf4llm) or accurate but slow (docling). Ours ties with docling on accuracy but is orders of magnitude faster.

https://github.com/pspdfkit/pdf-to-markdown

We'd love feedback on it, and ofc send us files that break it.

Comments URL: https://news.ycombinator.com/item?id=47618274

Points: 6

# Comments: 0

But regarding our pricing - I can point you at an actual testimonial https://www.g2.com/products/pspdfkit-sdk/reviews/pspdfkit-sd...

> These pricing structures can be complex and NEED to be understood fully before moving forward with purchase. However, out of all of the solutions that I reviewed, [Nutrient] was the one that walked me through their pricing the best and didn't make me feel like I was going to get fleeced.

That’s why we built our AI Document Processing SDK (for PDF files) - basically a REST API service, PDF in, structured data in JSON out. With the experience we have in pre-/post-processing all kinds of PDF files on a structural not just visual basis, we can beat purely vision based approaches on cost/performance: https://www.nutrient.io/sdk/ai-document-processing

If you don’t want to suffer the pain of having to deal with figuring this out yourself and instead focus on your actual use case, that’s where we come in.

As do we at Nutrient, we use Harfbuzz in WASM plus our own layouting - see the demo here: https://document-authoring-demo.nutrient.io/

Getting APIs for that into the Platform would make life significantly easier, but thanks to WASM it’s not a total showstopper.

Btw, I saw you’re working on sync at ElectricSQL - say hi to Oleksii :)

We're looking for a Senior TypeScript SDK Engineer to join the team responsible for the Nutrient Web SDK.

It is a toolbox for web engineers and application developers who need a painless way to render, edit and process documents. It either runs client-side using WebAssembly or connects to the Nutrient Document Engine. Take a look at its API docs to get an understanding of the scope involved: https://www.nutrient.io/api/web/

More details & application here: https://ats.rippling.com/en-GB/nutrient/jobs/27613cfa-84eb-4...

Nutrient | Senior Internal Tools Engineer | Full-time | Remote

We’re looking for someone who will work on our internal applications - primarily built with Ruby on Rails and Postgres - which power everything from product development and licensing workflows to revenue analysis and operational management across Engineering, Sales, Product, and Finance.

More details & application here: https://ats.rippling.com/en-GB/nutrient/jobs/66934d69-fd40-4...

We're looking for a Senior TypeScript SDK Engineer to join the team responsible for the Nutrient Web SDK.

It is a toolbox for web engineers and application developers who need a painless way to render, edit and process documents. It either runs client-side using WebAssembly or connects to the Nutrient Document Engine. Take a look at its API docs to get an understanding of the scope involved: https://www.nutrient.io/api/web/

More details & application here: https://nutrient.bamboohr.com/careers/205

Thousands of companies, organizations, governments, and developers use PSPDFKit’s document SDKs to enable collaboration, signing, markup, and more in their apps.

We are a fully remote company backed by Insight Partners and we're in it for the long run.

https://pspdfkit.com/careers/

Thousands of companies, organizations, governments, and developers use PSPDFKit’s document SDKs to enable collaboration, signing, markup, and more in their apps.

We are a fully remote company backed by Insight Partners and we're in it for the long run.

https://pspdfkit.com/careers/

Consider these two function signatures:

map :: ([a] -> [a])

map :: ([int] -> [int])

Furthermore the syntax that Elixir uses here let's you do something like

map :: (list(a) -> list(b))

list_to_other_data_structure :: (list(a) -> other_data_structure(a))

It all reminds me a bit of how Haskell does it https://medium.com/functional/haskell-basic-types-and-type-v...

I'm now curious to know if/how the above 'generics' would be expressed in TypeScript/Python/Go without a similar 'type constructor' syntax construct?

Comments URL: https://news.ycombinator.com/item?id=35901200

Points: 21

# Comments: 0

I never understood how this can be considered consistent at all, and those IMHO language design warts made me look into Ruby at the time.

Has this improved since? I know print was changed in Python3 to make it not-special.