664
submitted 1 year ago by gkd@lemmy.ml to c/programmerhumor@lemmy.ml
top 50 comments
sorted by: hot top controversial new old
[-] DumbAceDragon@sh.itjust.works 212 points 1 year ago* (last edited 1 year ago)

>buy serverless cloud
>look inside
>servers

[-] merthyr1831@lemmy.world 124 points 1 year ago* (last edited 1 year ago)

>make website on no-code editor

>look inside

>code

[-] qisope@lemmy.world 51 points 1 year ago* (last edited 1 year ago)

>buy serverless cloud

>never look inside

[-] QuazarOmega@lemy.lol 24 points 1 year ago* (last edited 1 year ago)

Ah yes, the age old "if a tree falls in a forest and no one is around to hear it, does it make a sound?"

[-] qisope@lemmy.world 24 points 1 year ago

or in this case, if a server fails in the cloud and no one is around to see it, does my app still run?

[-] XTornado@lemmy.ml 6 points 1 year ago

It requires conscious observation similar to the photons acting like a wave until observed which then they are a particle.

[-] konalt@lemmy.world 99 points 1 year ago

It's not serverless, it's just someone else's server

[-] evatronic@lemm.ee 30 points 1 year ago

Yeah, yeah, but I don't have to patch it.

[-] physcx@kbin.social 16 points 1 year ago

Don’t have to patch the host at least… I think we have a 6 week sla for certain compliances to ensure we are patching our containers, code, and deps regularly.

[-] evatronic@lemm.ee 5 points 1 year ago

That sounds like a problem for IT, not a dev. ;)

[-] takeda@lemmy.world 6 points 1 year ago

Exactly, it is as much serverless as the offering that allowed to host php sites back in the day.

[-] magic_lobster_party@kbin.social 5 points 1 year ago

Serverless is more associated with micro services where each micro service can scale independently from each other.

[-] takeda@lemmy.world 1 points 1 year ago

It is, but the idea how it works is roughly the same.

[-] Cryan24@lemmy.world 2 points 1 year ago

That you don't need to care about.. as a dev you want to write your code, deploy and not have to care about the underlying server maintenance.. you are paying for that to be someone else's problem.

[-] Dirk@lemmy.ml 61 points 1 year ago
[-] folkrav@lemmy.ca 31 points 1 year ago

I'm as critical as the next guy of how overused and abused serverless/microservice architectures can be, but there's disliking something and being completely disingenuous. Some of the comments every time the subject is even remotely mentioned fall into the latter. This time is not the exception lol

[-] gkd@lemmy.ml 21 points 1 year ago

I mean that’s generally the case with most tech. Just like the never ending PHP hate. Plenty of reasons to dislike or not use it but no reason to think it’s the scum of the earth.

[-] lemmyingly@lemm.ee 9 points 1 year ago

On a tangent, I imagine PHP is still one of the most used backends. Wordpress uses PHP and I wouldn't be surprised if 50% or more of the websites I visited are Wordpress sites. So I guess many others experience the same?

[-] gkd@lemmy.ml 9 points 1 year ago

Very widely used still and well maintained. It's been a good options since 7 came around. Most of the hate IMO comes from people who were working with PHP4/5 code or people who just saw PHP4/5 code and think that's what the language is today.

[-] railsdev@programming.dev 2 points 1 year ago

Don’t wanna hate but maybe this will stir the pot: any time I go to a website and go “this is definitely Wordpress” I’m usually right (I check with the Webappalyzer extension).

[-] dan@upvote.au 5 points 1 year ago* (last edited 1 year ago)

It really depends on how much customization has gone into the site. TechCrunch, Wired, and TIME all use WordPress for example, but their theme is customized to the point where you can't really tell that it's WordPress. There are some ways to tell though, for example some of the larger sites are hosted by Automattic (these say "powered by WordPress VIP" in the footer), and /wp-admin usually still works to go to the login page.

[-] railsdev@programming.dev 2 points 1 year ago

Yeah, that’s a fair point. I’ve been surprised to see a website is Wordpress from time to time.

As far as /wp-admin goes, I know all about that! Any web server I’ve run is constantly overrun with bots trying to hack it. A lot of times I configure nginx to simply drop connections to any URL ending in .php or GZIP bomb.

[-] folkrav@lemmy.ca 1 points 1 year ago

Yeah, this stat is always a bit dubious sounding to me (how much of it is blogspam?), but WP is still much more prevalent than most devs seem to realize.

load more comments (3 replies)
[-] folkrav@lemmy.ca 4 points 1 year ago

Yeah... Indeed, our field is pretty prone to weird tribalism and jumping on bandwagons. Still, I dislike that just as much lol

[-] gkd@lemmy.ml 1 points 1 year ago

For sure. People find a niche they like and then think that is the solution to any problem. Until, of course, some new shiny tech catches their eye and they try that out (or their favorite clickbait Medium writer comes out with an article about "Why you shouldn't be using ____ anymore in 2023"). Then the love of their life gets thrown to the curb.

[-] catacomb@beehaw.org 3 points 1 year ago

I think it's a maturity thing. You eventually see so many trends come and go, peaks and troughs of hype cycles and some developers (probably including yourself at least once!) overusing certain new tech.

You eventually discover what works with current tech and then you can become healthily critical of anything new. You see it more for where it can fit and where it can't.

If you have something small and stateless then serverless is easy and, more importantly, scalable. It was a little easier to see its role once the hype fog had lifted and I had a problem to solve with it.

[-] dan@upvote.au 3 points 1 year ago

see so many trends come and go

It's interesting how things are cyclical. Serverless functions remind me of cgi-bin scripts.

[-] catacomb@beehaw.org 2 points 1 year ago

Yep, it's usually an existing idea with progression in a few areas. You could definitely achieve serverless with a cluster of servers hosting the same scripts in cgi-bin and I think that context helps to put it into perspective.

[-] dan@upvote.au 1 points 1 year ago* (last edited 1 year ago)

I feel like I should start a "serverless" startup that's just Apache running in a Kubernetes cluster with a bunch of cgi-bin scripts in a Ceph cluster. Boom, serverless with high availability.

[-] folkrav@lemmy.ca 1 points 1 year ago

If you only focus on the concept of a serverless function and forego 99% of the other stuff, yeah 😛

[-] railsdev@programming.dev 1 points 1 year ago

The trends coming and going is personally what makes me more tribal. Specifically I’m thinking of the JavaScript/Node ecosystem from the perspective of a Ruby on Rails developer.

Thankfully these days we have Hotwire and it’s possible to completely rip out all the Node trash we had to stuff into our containers.

[-] deezbutts@lemm.ee 26 points 1 year ago

Eli5 server less, even on paper...

[-] 0xD@infosec.pub 29 points 1 year ago* (last edited 1 year ago)

Instead of spinning up a classical server like Apache or IIS for what you need, you just write a single function that you can bind to an endpoint and just host that - the rest is abstracted away from you.

[-] SkyeStarfall@lemmy.blahaj.zone 39 points 1 year ago* (last edited 1 year ago)

Serverless sounds like a terrible name for this lmao.

Why not remote functions or something like that.

[-] 0xD@infosec.pub 22 points 1 year ago

Marketing™️ I guess? :P

But probably because YOU don't have to fuck around with servers, for you it's just an upload of a function.

[-] DrM@feddit.de 14 points 1 year ago

I think that's the main reason, it's a good name explaining what you can expect: an environment where you don't have to worry about servers and don't need an administrator

[-] dan@upvote.au 9 points 1 year ago* (last edited 1 year ago)

Why not just call it shared hosting though? It's essentially the same concept as getting a GoDaddy (or Bluegost or whatever) hosting account and uploading a PHP file lol

[-] DrM@feddit.de 7 points 1 year ago

Shared hosting sounds like you don't have your data stored privately and doesn't sound like less work for the company.

Don't look at the name from a technicians perspective, but from the perspective of a manager of a small startup who wants to reduce the overhead for hosting it's service as much as possible. Also serverless is not wrong per sé, it's exactly what you as the customer get.

You could spin it the same way for every other instance. Why do you call GoDaddy "shared hosting", in the end it's just a pod on a kubernetes cluster. So why don't you call it "private kubernetes pod"?

[-] fox@hexbear.net 18 points 1 year ago

Someone else has a server and their infrastructure is set up so you can upload a zip of some executable and they'll figure out how to make it run. You don't worry about any details except your code and whatever API is require to be compatible, and they worry about hosting it, making sure it has memory, CPU time, disk space, DB, etc.

[-] dan@upvote.au 12 points 1 year ago

So it's essentially the same as shared web hosting, just masquerading as a new concept. 15 years ago I'd deploy PHP sites by uploading them via FTP to some free web hosting company.

[-] Cysioland@lemmygrad.ml 5 points 1 year ago

Except it's not quite shared but "containerized"

[-] pimeys@lemmy.nauk.io 2 points 1 year ago

Yep. But you pay only for the CPU time you use and very often the only IO you can do is HTTP due to the runtime.

[-] Cryan24@lemmy.world 22 points 1 year ago

For the sys admins etc.. saying it's still a server, you are missing the point.. it's conceptually serverless in that you are paying a premium so you don't have to care about the server maintenance etc... That's someone else's problem.

[-] 31337@sh.itjust.works 6 points 1 year ago

I haven't ran into a good use-case to try out server-less yet. Either cold starts would be a problem (for example, I have an endpoint that needs to load a 5GB model into RAM, and it takes about 45 seconds). Or, it's just much more expensive than a VPS if the service is projected to constantly serve many requests all day. Containerized services on a VPS doesn't require much server maintenance (unless you have a dozen or so micro-services, then yeah, Kubernetes maintenance adds a lot of overhead).

[-] cupcakezealot@lemmy.blahaj.zone 19 points 1 year ago

serverless devs are the same as devs who don't know what graceful degradation is.

you don't have to be a server admin but at least know the basics

[-] VantaBrandon@lemmy.world 8 points 1 year ago

But think of the profit margins, and all the buzzwords our marketing team can use

load more comments
view more: next ›
this post was submitted on 27 Oct 2023
664 points (97.8% liked)

Programmer Humor

32706 readers
518 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS