Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

about.gitlab.com

Post reply on HN
Print view View original

221–230 of 275 posts

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

#221

Post by SoreGums »

stickfigure wrote: post #179
dubcanada wrote: post #10

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…

People use Heroku (and Google App Engine) because - if your app fits the model, and most do - you can completely skip ops/devops. Your whole team can go to sleep without a pager. You spend your life building features that customers care about instead of mucking with config files.

Yes!! Being part of a large org, nobody cares about the ops bit, leadership/product/dev mgrs just want features deployed!!! It's very obvious that the sooner we can abstract all the ops away the leaner we'll be.

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

#222

Post by ZephyrBlu »

ralph84 wrote: post #109
ZephyrBlu wrote: post #79

Earlier quoted context omitted.

> 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 That's what the Unfiltered tag is for. To resolve the company of any responsibility for this kind of thing.

The place for employees to post their personal opinion that doesn’t represent the company is their personal blog, not “about.gitlab.com/blog”. After you’ve raised almost half a billion dollars in funding, you can afford a PR person to review posts that appear on the company blog.

A PR person did review the post.

See this comment: https://news.ycombinator.com/item?id=26557589

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

#223

Post by samb1729 »

nightpool wrote: post #207
JimDabell wrote: post #157

Earlier quoted context omitted.

> 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…

Regardless of its unofficial status, it's a post promoting the company's products in a public space, where the employee is representing the company. As a GitLab employee agrees above, it's fair to judge the company and hold them to a high standard based on how their employees present their work in the public sphere.

> As a GitLab employee agrees above

That employee being the CEO ;)

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

#224

Post by reducesuffering »

ignoramous wrote: post #216
sytse wrote: post #158

Earlier quoted context omitted.

It is fair game to judge us based on our blog. At the same time it is a free-for-all for employees for blog posts marked Unfiltered as this one is. The author apologized in https://news.ycombinator.com/item?id=26555617 and we've made 8+ updates to the article to reduce the bias https://gitlab.com/gitlab-com/www-gitlab-com/-/commits/maste...

Wow. sytse, there's no one else I know who's your equal in the kind of leadership you show in managing GitLab. The transparency, the honesty in everything GitLab does is truly astonishing. Thanks for letting folks like me who know next-to-nothing about building companies be a fly-on-the-wall from oceans away, watch your meetings on YouTube, go through your plans and processes, observe eng designs and discussions arou…

Idk about transparent. They deliberately hid their "open compensation calculator."

https://about.gitlab.com/handbook/total-rewards/compensation...

That's increasing opaqueness.

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

#226

Post by dang »

airstrike wrote: post #203
tnolet wrote: post #86

> "A typical web app requires a database, storage or caching backend, which can get complicated to run with Heroku." Ah no. That is exactly where Heroku is dead easy. The creating, maintaining, updating and general day-to-day management of these "addons" require almost no input from the user. DB failover and mgmt is almost magic. I wished GitLab would stay away from this needless, click bait type articles. It's not e…

I agree but you're replying to the wrong comment

Thanks, we detached it from https://news.ycombinator.com/item?id=26554734 now.

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

#227

Post by ZephyrBlu »

dnsmichi wrote: post #182
dustinmoris wrote: post #175

Honestly I wish the GitLab CEO would stop this running around the bush thing here. We know exactly what happened. This is not just an innocent accident by an employee. I mean the title says it all... -> "We are building a better Heroku" People at GitLab, probably including sytse, have decided that it's worthwhile to build a new Heroku competitor into GitLab. Then someone was tasked to write a PR blog post about it. T…

Hi, I wrote the blog post last week, and decided to publish it on Monday. https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_request... The title was chosen poorly, and the blog post did not reflect on its intentions. For that, I deeply apologize. The experience and first time with Heroku is my raw impression, also the fact that I am a backend developer who is learning frontend and web apps. It is a hard lesson lea…

I just want to say that I think most (If not all) of the vitriol is not directed towards you, but GitLab itself.

A guy linked a bunch of GitLab tickets in another comment showing that you went through the proper process and had multiple other people approve the post, so I think there wasn't much else you could personally do.

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

#228

Post by boleary-gl »

reducesuffering wrote: post #224
ignoramous wrote: post #216

Earlier quoted context omitted.

Wow. sytse, there's no one else I know who's your equal in the kind of leadership you show in managing GitLab. The transparency, the honesty in everything GitLab does is truly astonishing. Thanks for letting folks like me who know next-to-nothing about building companies be a fly-on-the-wall from oceans away, watch your meetings on YouTube, go through your plans and processes, observe eng designs and discussions arou…

Idk about transparent. They deliberately hid their "open compensation calculator." https://about.gitlab.com/handbook/total-rewards/compensation... That's increasing opaqueness.

GitLab employee here. That was based on requirements outside of our control - and it is still available to employees and candidates. Everything is public by default, except for things that can't be - but we're public about what isn't public: https://about.gitlab.com/handbook/communication/#not-public

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

#229

Post by cpursley »

jrochkind1 wrote: post #22

So I think heroku has stagnated a bit, and I am definitely very open to "better herokus". But the idea that something you did in five minutes is going to be better than heroku (in all ways?) is.... I don't know what the adjective is. Heroku is very mature and polished software, that almost always does what you expect -- it's a very non-leaky abstraction, I guess. You can almost always get away with ignoring the detai…

Iny my experience, Render.com is a better (at least cheaper) Heroku plus it handles distributed Elixir really easily.

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

#230

Post by cpursley »

nakovet wrote: post #20

Alternatively, I tried using DigitalOcean app platform (side note: super hard to Google for help due to the generic name) and it was way harder than setting up Heroku, I invested multiple hours in a few days and when I finally got the app running I was not confident enough to proceed with the migration yet. Things I've noticed: * Segmentation Fault when deploying a Rails app, Heroku just works. * Ability to add Postg…

Check out Render.com
Post reply on HN