Live data from Hacker News

We are far from a better Heroku for production apps in a hyper cloud

about.gitlab.com

51–60 of 275 posts

Re: We are far from a better Heroku for production apps in a hyper cloud

#51
I'm not sure how a blog post like this made it past any kind of review/quality control/PR in a 1000+ employee company.

Criticising other services is quite poor form already.

But then the criticism is a shallow dismissal by someone knowing nothing about Heroku, and with a minimal, odd example on top.

And the proposed alternative is running Terraform in a CI pipeline to set up AWS.

Yeah, that's not why people use Heroku...

I'm usually positive towards Gitlab, but if I were them I would make this post disappear as quickly as possible, it's that embarrassing.

Re: We are far from a better Heroku for production apps in a hyper cloud

#53
post #2

I feel like Gitlab is going in a direction of AWS, except that instead of having separate products it just bundles everything in one. One massive bloatware that's scary to touch, no idea where features begin or end, or what is it even for in the end. Everything? I thought it was supposed to be Git hosting, but I'm not even sure anymore.

GitLab is an experiment of building a VC funded startup on anti-patterns and see how far you can go and get away with.

Re: We are far from a better Heroku for production apps in a hyper cloud

#54

People do not use Heroku because it takes 5 minutes to spin up a box. They use it because it's super easy. Click a button, bam deployed. Want to add a database, click what database you want, bam you got a database, environment variables set and a GUI (depending on what you pick). Want to scale up? Click a button, you're now scaled up. Want a entire review system with staging links and everything? Setup the review pro…

"there is no CLI involved"

Well that's annoying, seeing as I've just done everything else on the CLI

Re: We are far from a better Heroku for production apps in a hyper cloud

#55

This 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!

The only thing they succeeded in was reminding me how good Heroku is compared to whatever they're trying to sell

Re: We are far from a better Heroku for production apps in a hyper cloud

#56

Earlier quoted context omitted.

> I have been a backend focussed developer in the past 20 years, web development is often fighting with Javascript and CSS. Especially Heroku as a deployment platform is a new area for me. No editing either...

I found the article confusing. It was difficult to understand what they're actually doing (I'm still unclear on that, actually).

The documentation might help you to better understand what we're building: https://gitlab.com/gitlab-org/5-minute-production-app/deploy...

Re: We are far from a better Heroku for production apps in a hyper cloud

#57
The first blog post I ever wrote that made the front page of Hacker News was called "Docker is the Heroku Killer".

https://news.ycombinator.com/item?id=8371249

Let me be real clear here...only Heroku will ever beat Heroku.

Docker has enabled a lot of other great options that are all modeled after the experience that Heroku has created...but ultimately people keep looking to Heroku because they are the gold standard.

Better is a series of tradeoffs. Heroku has been refining the tradeoffs to using their platform for a decade. You may create tradeoffs that work better for a use case that you want to enable, but ultimately you're going to have to convince people that your set of tradeoffs has made things "better".

Re: We are far from a better Heroku for production apps in a hyper cloud

#59
post #28
post #17

I wish they would focus on other things. Things like GitLab CI's cache are unusable with most workloads, we even had builds which were faster without the cache than with it.

GitLab customer here. Sometimes I also feel like they are adding a lot of stuff instead of improving their core services. BTW I already gave up on using GitLab's native caching in favor of doing all my CI/CD with Kaniko + Multi Stage Dockerfiles I would not care about new features if they had granular billing like AWS, GCP, etc... But here I am paying for Devsecops and a lot other stuff I don't use.

I would love to hear more about this billing information in GitLab. Are you looking for build minutes and CPU of Runners per cloud service? What kind of questions are you typically trying to answer with that information?

Re: We are far from a better Heroku for production apps in a hyper cloud

#60
post #16
post #12

Earlier quoted context omitted.

This was a great comment until the mean-spirited last word.

Some folks don’t take kindly to lofty claims and name-dropping just to rile up interest. I’ve run production apps on Heroku in the past, best possible service for small teams. Gitlab? Given how expensive it is - I’m not so sure.

Yeah, if you write a promotional post for technical people (I don't know who else this post would be for) you should expect to be called out on your bullshit.
Post reply on HN