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

Post by dvfjsdhgfv » Wed, Sep 04, 2019, 6:03 AM UTC

tannhaeuser wrote: post #20

viraptor wrote: post #2

I appreciate the meme and get it as a response to everything being "serverless" recently. But I noticed some people started repeating it unironically, like cgi-bin was actually equivalent. I wish this project at least acknowledged it's a meme reaction. Maybe people these days don't remember anymore what cgi-bin really worked like? (or never worked with it?)

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.

Post by tannhaeuser » Wed, Sep 04, 2019, 6:20 AM UTC

dvfjsdhgfv wrote: post #21

tannhaeuser wrote: post #20

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…

Post by viraptor » Wed, Sep 04, 2019, 6:55 AM UTC

tannhaeuser wrote: post #23

dvfjsdhgfv wrote: post #21

Earlier quoted context omitted.

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…

That's a great point - that there are of course those who ride the cloud wave to milk their customers. To get a sense of how much we're putting the cart before the horse, I recommend taking an occasional look at a subreddit frequented by webdev bootcampers (eg. [1] where they're hellbent to justify using React for static sites, because that's all they really know, and even accuse dissenters of being hiveminded). [1]:…

Post by majewsky » Wed, Sep 04, 2019, 12:56 PM UTC

viraptor wrote: post #13

spc476 wrote: post #12

Earlier quoted context omitted.

Oh, so it's FastCGI then.

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

Post by sodabrew » Wed, Sep 04, 2019, 1:58 PM UTC

quickthrower2 wrote: post #16

jasonjei wrote: post #8

Earlier quoted context omitted.

It’s a really apt comparison. Before PHP and embedded scripting with HTML, and entire contained applications with MVC frameworks, we had our static HTML and our CGI. Now we have serverless and HTML that talks to our cgi-bin using JavaScript. Life is full circle. Client/server back to the cloud, which reminds me of the dumb-terminal/mainframe days.

But the key difference is in the "why". Serving that HTML from a nearby web server is a lot faster, and it's easier to distribute static content to a bunch of servers around the world that are near the people requesting them.