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.
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.
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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
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.
It’s interesting how things are cyclical. Serverless functions remind me of cgi-bin scripts.
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.
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.
If you only focus on the concept of a serverless function and forego 99% of the other stuff, yeah 😛
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.