This does not seem better.
We are far from a better Heroku for production apps in a hyper cloud
161–170 of 275 posts
Re: We are far from a better Heroku for production apps in a hyper cloud
#162This was very cringey. A super contrived demo and bashing Heroku through a Twitter reference. Reads like someone is drunk/high and wanted to shitpost about a competitor. I would be appalled by this if I were GitLab's PR department!
It's written by a developer with a disclaimer that it's "unfiltered". I think it's part of their PR strategy to sound authentic and not salesy. Seems to mostly work for them.
Authentically cringey
Re: We are far from a better Heroku for production apps in a hyper cloud
#163Hopefully this doesn’t work.
Re: We are far from a better Heroku for production apps in a hyper cloud
#164Earlier quoted context omitted.
The idea would be to allow Heroku working independently while offering their solution at literally AWS cost (without all the discount), or even AWS Graviton2 cost. This would pretty much directly compete with Linode and DO on a value proposition. And a lock in to AWS ecosystem.
Heroku runs on AWS already, they're earning cost + markup as it is. If they purchased Heroku and did this, they'd be out several billion dollars plus lose their markup. Many of the Heroku addons also run on AWS, so customers may lock themselves into without knowing it. Additionally, customers are free to further lock themselves into the AWS ecosystem via "private space"/VPC peering. And they have a competitor to Lino…
> Heroku runs on AWS already, they're earning cost + markup as it is. If they purchased Heroku and did this, they'd be out several billion dollars plus lose their markup.
I fail to understand this. If Heroku is on AWS, Heroku is selling its services at price X. AWS is getting from Heroku Y money, where X > Y (or it should at least, if Heroku is not operating at loss). If Amazon owns Heroku it could sell its services still for X, eating Heroku's margin plus the margin it already had on the AWS offering.
Re: We are far from a better Heroku for production apps in a hyper cloud
#165There is already a better Heroku and it's Vercel (previously Zeit) https://vercel.com/ I believe Vercel is the spiritual successor of Heroku. I guess Heroku got bought by Salesforce and the founders/visionaries left. Heroku should have moved to bill per seconds/milliseconds based on AWS Lambda functions like Vercel did later.
Isn't Vercel pretty much just for Jamstack? Not everyone wants or needs that so I'm not sure it's better.
Hey! Lee from Vercel here. Vercel isn't just for static sites – it also handles server-rendered applications, serverless functions, and hybrid frameworks (like Next.js).
The current focus has been on an incredible front-end experience, but we're working to become a first-party integrator with your favorite backend solutions.
For example, you can deploy a full-stack Next.js application with a PostgreSQL database in less than 3 minutes: https://twitter.com/leeerob/status/1351576575888797696
Re: We are far from a better Heroku for production apps in a hyper cloud
#166Earlier quoted context omitted.
It's a blog post on the company's official blog, no? I doubt it's like a free-for-all where any employee can post whatever they want without any review. Judging GitLab based on the content posted on their blog seems like fair game.
> It's a blog post on the company's official blog, no? No. There’s a notice saying it’s unfiltered, with a link leading to a disclaimer saying, pretty much: > it's like a free-for-all where any employee can post whatever they want without any review. Or, in their own words: > This blog is intended for user-generated content submitted by the GitLab team. The views and opinions represented in this blog are personal to…
[deleted]
Re: We are far from a better Heroku for production apps in a hyper cloud
#167This article is a bad look for GitLab.
Re: We are far from a better Heroku for production apps in a hyper cloud
#168They updated the post with this disclaimer:
> Update: This post does not live up to its original title We are building a better Heroku...It should have emphasized the building part, we're just starting. The current 5 minute production app doesn't hold a candle to Heroku at the moment. It should have made it clear the goals is to improve the speed with which you can configure a production app, not a development app. Development apps on Heroku are already close to perfect.
Re: We are far from a better Heroku for production apps in a hyper cloud
#169Earlier quoted context omitted.
User experience is often laughed at or even overlooked, but this is why Firebase and Heroku are used! I had a mainframes course in university and people from IBM would tout how everything we do today was already invented by them decades ago. But yeah, when you tried to use their stuff you had to jump through so many hoops, that you lost your motivation half the way.
I'm often confused at how poor so many engineers' product-sense is. Especially infra engineers (speaking as one). It's one thing to not have good product-sense when you're not the user, but for products like Heroku you literally are. My best guess is that a lot infra engineers actually value seeing the complexity and being able to understand all the pieces being used in the system more than they value getting somethi…
It must be something to do with forgetting how hard things are for novices
Reminds me of the famous old HN comment about Dropbox
Re: We are far from a better Heroku for production apps in a hyper cloud
#170the fuck did I just read? A bunch of buzz words smashed together "hyper clouds", "DevSecOps".
Then starts to show off how easy it is to use heroku, while complaining about how complex it is???
And at the end there are some vague screenshots showing a supposedly easier method of deploying things than using heroku, but first you have to learn GitLab CI/CD, Terraform, AWS, and probably a bunch of other things?