3 ms·
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-
by viraptor 7y ago
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?)
- GauntletWizard 7y agoI think you're the one mistaken, here. The interface for cgi-bin was that you created a process per web request. The interface for Serverless is that you create a process per web request. The tooling is a lot better for Serverless, but I'd hesitate to call it 20 years better - I'd hesitate to call it 10 years better.
- viraptor 7y ago> The interface for Serverless is that you create a process per web request. That is not how it works in the most popular solutions. Both aws lambda and Google cloud functions will keep the server instance running after your first request and only dispatch function calls - you can cache data between requests in globals. That's also why the first cold request is so much slower (it actually loads the code for the first time). Most serverless function environments are much closer to managed fastcgi, than old cgi-bin approach. This is mentioned right in the service docs: https://cloud.google.com/functions/docs/concepts/exec#function_scope_versus_global_scope https://cloud.google.com/functions/docs/concepts/exec#functi... Also, thanks for proving my point - some people don't understand it's a meme, not real equivalence.
- exabrial 7y agoso it's not serverless then...
- keanebean86 7y ago"Someone else handles the server instances and hardware while you just write the functions" doesn't have the same ring to it.
- spc476 7y agoOh, so it's FastCGI then.
- viraptor 7y agoManaged FastCGI with guaranteed execution environment, integrated deployment process, aggressive autoscaling and billed for usage rather than provisioned resources.
- kbenson 7y agoSo, FastCGI with good process accounting and limits. I get it, it's nice, but I agree with others it's mostly a nice extension and better api for CGIs. Oh, with better marketing of course.
- majewsky 7y agoSoooooo... Heroku? :)
- viraptor 7y agoNo, 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.
- tannhaeuser 7y agoI'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.
- dvfjsdhgfv 7y agoI 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 yourself, unless you're stupid you'll calculate well and choose the option that makes most business sense. In many case this means renting a server or a couple of servers for a flat rate. The sad piece of truth in your comment is that there are actually people who seem to know only AWS (etc.) and use it for everything, whether it makes sense or not. Well, that's their choice.
- tannhaeuser 7y agoThat'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]: https://www.reddit.com/r/webdev/comments/cxfvcw/is_react_still_worth_it_for_nondynamic_webpages/ https://www.reddit.com/r/webdev/comments/cxfvcw/is_react_sti...
- viraptor 7y agoI feel you're misrepresenting that discussion. Most people say they shouldn't use react, some propose react to generate static content before deployment, few raise good points for why you may want to use react even if the page is static right now. There's always going to be an extremist opinion somewhere, but it's really not common in the discussion you linked.