Wouldn't "Serverless OCR" mean something like running tesseract locally on your computer, rather than creating an AI framework and running it on a server?
Not quite. Serverless means you can run a server permanently, but you need pay someone else to manage the infrastructure for you.
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.
I do agree with the use of serverless though. I feel like we agree long ago that serverless just means that you're not spinning up a physical or virtual server, but simply ask some cloud infrastructure to run your code, without having to care about how it's run.
Low LoC count is a telltale sign that the project adds little to no value. It's a claim that the project integrates third party services and/or modules, and does a little plumbing to tie things together.
https://github.com/zai-org/GLM-OCR
(Shameless plug: I also maintain a simplified version of GLM-OCR without dependency on the transformers library, which makes it much easier to install: https://github.com/99991/Simple-GLM-OCR/)
'Serverless' has become a term of art: https://en.wikipedia.org/wiki/Serverless_computing
> Serverless is a misnomer
But this caught me for a bit as well. :-)
I use carless transportation (taxis).