> 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.
Nutrient.io Co-Founder here: We’ve been doing PDF for over 10y. PDF Viewers like Web browsers have to be liberal in what they accept, because PDF has been around for so long, and like with HTML ppl generating files often just iterate until they have something that displays correctly in the one viewer they are testing with.
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.
> One that I've repeatedly gone back to over the years is paginated rich text editing. It's simply impossible to do with contenteditable in a product level way - one of the reasons Google docs has a custom layout engine.
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/
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.
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/
Did you try the ones from https://getwellue.com/? In my informal testing against “medical-grade” SPO2 monitors they were accurate and they record all night long.
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.
Been playing with this for a while now while it was still in alpha, and I must say I am super excited where this will go. It's a great writing experience, with powerful tooling, especially for use cases like e.g. the legal profession that goes through many revisions.
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.
Hey Max, I think your offering is amazing but it might be built for the world of yesterday: Since starting this weekend apparently all deposits are 100% insured, why would I go to Mercury to take advantage of sweeps or a money market fund, when my bank offers me slightly higher rates for uninsured-but-insured-in-practice deposits?
When I looked at Python vs Ruby many years ago, I found the opposite: Why does Python have (special) functions like len() and map(), instead of 'properly' supporting both OOP (len should just be a method on objects) and/or FP (support multi-line lambdas so I can actually use map/filter etc).
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.
asdf + direnv is how I avoid the performance hit of the shims completely. For me that's the sweetspot of developer ergonomics, performance and reproducibility of the dev env.