Live data from Hacker News

A browser extension that replaces occurrences of 'serverless' with 'CGI-bin'

github.com

31–33 of 33 posts

Re: A browser extension that replaces occurrences of 'serverless' with 'CGI-bin'

#31

Earlier quoted context omitted.

I'd rather say it's worrying how millenials+ raised in post-standard cloud times are in denial of just how much they dropped the ball and are being brainwashed to believe the cloud progress narrative where there is only centralization and monopolization. Self-delusion to stay relevant in the job market.

I don't think you're fair here. There definitely are some that blindly believe the hype, but I met many who clearly see through the bullshit. Mostly, it boils down to the crucial distinction: are you building the project for someone else or for yourself? If for someone else, of course you want to maximize your revenue, and here the complexity of AWS &co. is an advantage. However, if you're building something for your…

This is a great point. If we didn't host our own servers, we'd be on the line for thousands more than we currently pay.

It's only sheer force of keeping servers internal that we've had the expertise and knowhow to host our platform ourselves. Now that we're the size that we are, the platform is crazily reliant on hosting it ourselves for administration and liability, so we'd need to have migrated anyway.

Re: A browser extension that replaces occurrences of 'serverless' with 'CGI-bin'

#32

Earlier quoted context omitted.

Managed FastCGI with guaranteed execution environment, integrated deployment process, aggressive autoscaling and billed for usage rather than provisioned resources.

Soooooo... Heroku? :)

No, you tell heroku how many dynos you're going to pay for, and you pay whether you fully utilised them or not. With lambda you don't declare that up front and get billed only for what was served.

Re: A browser extension that replaces occurrences of 'serverless' with 'CGI-bin'

#33
post #28

Well, maybe I'm just missing something in this meme, but... Back in the day, deploying code to cgi-bin first required buying and hosting your own server; which I have neither the time or patience to do today.

No, you just rented an account on a shared host. My first job after uni in the 1990s was looking after Demon Internet’s web servers, which were all like 1000 accounts/sites per server.

People generally only rented T1 lines when cgi was introduced.

Building and hosting your own server was prerequisite for having hacker cred in the 90s.

Post reply on HN