I used to be RoR developer a while ago. Working with gitlab is a breeze because I can apply all the knowledge I have - by the virtue of being a RoR app i know how can i apply migrations, how to call interactive console, how to monitor and clear work queues, how to add middleware. Gitlab using RoR is a great win for /me/
Why We Chose Rails to Build Gitlab
11–20 of 165 posts
Re: Why We Chose Rails to Build Gitlab
#12No offense, but this is just a really weak PR fluff piece. The with only interesting thing is that they use Go for the hit access part. Oh, and Ruby and multithreading don’t mix, who knew? I like that if you preface your offending remarks with “no offense” you’re excused.
As an aside, when companies are doing these interview-style pieces are they actually interviewing the CEO? I always just assume they pull the quotes out of their ass.
Re: Why We Chose Rails to Build Gitlab
#13It's amusing, that you can substitute every reference from Ruby to Python and Rails to Django and article would still make sense.
Except for the part about running in production. Seems like Python is a bit ahead there.
Re: Why We Chose Rails to Build Gitlab
#14No offense, but this is just a really weak PR fluff piece. The with only interesting thing is that they use Go for the hit access part. Oh, and Ruby and multithreading don’t mix, who knew? I like that if you preface your offending remarks with “no offense” you’re excused.
As an aside, when companies are doing these interview-style pieces are they actually interviewing the CEO? I always just assume they pull the quotes out of their ass.
I don't know about other companies, but given that gitlab's CEO is the type to be regularly active on HN (and will probably be reading this) it seems safe to assume that he would actively cooperate with such an article
Re: Why We Chose Rails to Build Gitlab
#15> Because GitHub did.
Which was because two of the co-founders met at a Ruby meetup.
Re: Why We Chose Rails to Build Gitlab
#16Does anyone ever have to justify using Java for their backend?
mostly in the industry (finance) I work Java is the default. You need to justify and seek approvals for using anything else.
Re: Why We Chose Rails to Build Gitlab
#17"Why GitLab are stuck with Ruby on Rails"
[deleted]
Re: Why We Chose Rails to Build Gitlab
#18Re: Why We Chose Rails to Build Gitlab
#19No offense, but this is just a really weak PR fluff piece. The with only interesting thing is that they use Go for the hit access part. Oh, and Ruby and multithreading don’t mix, who knew? I like that if you preface your offending remarks with “no offense” you’re excused.
As an aside, when companies are doing these interview-style pieces are they actually interviewing the CEO? I always just assume they pull the quotes out of their ass.
I suspect that a PR person writes the piece with rough quotes, which the CEO then puts into their own words.
Re: Why We Chose Rails to Build Gitlab
#20"Why GitLab are stuck with Ruby on Rails"
>"Our mission is that everyone can contribute," he explains. "Because Ruby on Rails is really opinionated about which pieces go where, it's much easier for new developers to get into the codebase, because you know where people have put stuff. For example, in every kitchen you enter, you never know where the knives and plates are located. But with Ruby on Rails, you enter the kitchen and it's always in the same place, and we want to stick to that.
Sounds like they have no desire to switch away.