Live data from Hacker News

Rolling your own serverless OCR in 40 lines of code

christopherkrapu.com

61–69 of 69 posts

Re: Rolling your own serverless OCR in 40 lines of code

#62
post #59
post #29

Not 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!

This is more like buying a loaf of bread from the store and saying you baked it yourself. They did nothing even close to making an OCR engine.

Re: Rolling your own serverless OCR in 40 lines of code

#63

Earlier quoted context omitted.

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…

A runtime is notably NOT infrastructure, had you said instruction set you might have landed closer to making a compelling argument, but the whole point is that AWS (and other providers) abstract away the underlying infrastructure and allow the developers to as I said, have "little care of the infrastructure it runs on". There is often advanced networking that CAN be configured, as well as other infrastructure components developers can choose to configure.

Re: Rolling your own serverless OCR in 40 lines of code

#64

Earlier quoted context omitted.

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.

Unless the engineer takes steps to spin down EC2 infrastructure after execution, it is absolutely persistent compute that you're billed for whether you are doing actual processing or not. Whereas lambda and other services are billed only for execution time.

Re: Rolling your own serverless OCR in 40 lines of code

#65
post #29

Not 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.

Consider the source of the idiom: rolling your own cigarettes.

Which involves taking some rolling papers, a pouch of loose tobacco (or whatever), and perhaps a little device if you're rich. As opposed to manufactured cigarettes, you're just doing some manual assembly for the end-product.

You don't need to cultivate the plants or pulp any trees to roll your own.

Re: Rolling your own serverless OCR in 40 lines of code

#66
post #29

Not 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.

It means "one that is yours" in the same way "running your own plex server" does not imply starting with building a silicon fab.

Re: Rolling your own serverless OCR in 40 lines of code

#67
post #59
post #29

Not 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!

Is it "building your own oven" if you go to Lowe's, buy an oven, and installed it yourself? You've done some work, but your integrating a pre-built appliance into your kitchen, not built your own oven

Re: Rolling your own serverless OCR in 40 lines of code

#68
post #59

Earlier quoted context omitted.

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!

Is it "building your own oven" if you go to Lowe's, buy an oven, and installed it yourself? You've done some work, but your integrating a pre-built appliance into your kitchen, not built your own oven

The title is "rolling your own", not "building your own"

Re: Rolling your own serverless OCR in 40 lines of code

#69
post #59
post #29

Not 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!

why are chefs baking bread? there's buildings to construct
Post reply on HN