Earlier quoted context omitted.
That's the beauty of such stupid terms. I use carless transportation (taxis).
taxis are cars, aren't they?
Precisely. And serverless uses servers.
Rolling your own serverless OCR in 40 lines of code
51–60 of 69 posts
Re: Rolling your own serverless OCR in 40 lines of code
#52Earlier quoted context omitted.
> Serverless means spinning compute resources up on demand in the cloud vs. running a server permanently. Not quite. Serverless means you can run a server permanently, but you need pay someone else to manage the infrastructure for you.
Close. It means there's no persistent infra charges and you're charged on use. You dont run anything permanently.
It still doesn't capture the concept because, say, both AWS Lambda and EC2 can be run just for 5 minutes and only one of them is called serverless.
Re: Rolling your own serverless OCR in 40 lines of code
#53Wouldn't "Serverless OCR" mean something like running tesseract locally on your computer, rather than creating an AI framework and running it on a server?
No, that would be "Running OCR locally..." 'Serverless' has become a term of art: https://en.wikipedia.org/wiki/Serverless_computing
It's good they note explicitly:
> Serverless is a misnomer
Re: Rolling your own serverless OCR in 40 lines of code
#54Why "rolling"?
Is this a reference to baking or what's the origin?
Re: Rolling your own serverless OCR in 40 lines of code
#55Deepseek OCR is no longer state of the art. There are much better open source OCR models available now. ocrarena.ai maintains a leaderboard, and a number of other open source options like dots [1] or olmOCR [2] rank higher. [1] https://www.ocrarena.ai/compare/dots-ocr/deepseek-ocr [2] https://www.ocrarena.ai/compare/olmocr-2/deepseek-ocr
A bit surprised to learn that Rednote maintains one of the leading open-source OCR models on the market, nice.
Re: Rolling your own serverless OCR in 40 lines of code
#56How does this compare to Tesserect?
[flagged]
> The author spent $2 on A100 GPU time for 600 pages
Hopefully that cost would come down quite a bit, because that doesn't compete with most offerings right now IMO. I haven't tested it, but I can use models that have vision as an input modality for much cheaper, closer to 25k images per $1.
Re: Rolling your own serverless OCR in 40 lines of code
#57Wouldn't "Serverless OCR" mean something like running tesseract locally on your computer, rather than creating an AI framework and running it on a server?
Yep. That fraudulent term finally got me this time. Totally serverless except for that remote 3rd party server. Sigh.
Re: Rolling your own serverless OCR in 40 lines of code
#58The real question is why pick python 3.11
Re: Rolling your own serverless OCR in 40 lines of code
#59Not sure what “your own” in the title is supposed to mean if you are running a model that you didn’t train using a framework that you didn’t write on a server that you don’t own.
Not sure what "baking your own bread" means if you are using wheat grown by someone else in an oven that you didn't build that is run with electricity you didn't created from your muscles' force. You haven't even contributed to the nuclear fusion which created the oxygen for the water molecules you've been using! How dare you, standing of the shoulders of giants!
Re: Rolling your own serverless OCR in 40 lines of code
#60Earlier quoted context omitted.
> Serverless means spinning compute resources up on demand in the cloud vs. running a server permanently. Not quite. Serverless means you can run a server permanently, but you need pay someone else to manage the infrastructure for you.
You might be conflating "cloud" with serverless. Serverless is where developers can focus on code, with little care of the infrastructure it runs on, and is pay-as-you-go.
> You might be conflating "cloud" with serverless. Serverless is where developers can focus on code, with little care of the infrastructure it runs on, and is pay-as-you-go.
That's not what serverless means at all. Most function-as-a-service offerings require developers to bother about infrastructure aspects, such as runtimes and even underlying OS.
They just don't bother about managing it. They deploy their code on their choice of infrastructure, and go on with their lives.