Aside from the idea of charting random developers' gut instincts regarding entire programming languages, the only contribution this article makes to the literature is the dubious phrase "scalability of innovation." I would have appreciated some honesty regarding why they're really sticking with Rails at Gitlab: a decade worth of development that would have to be rewritten from scratch to little discernable benefit.
> I would have appreciated some honesty regarding why they're really sticking with Rails at Gitlab: a decade worth of development that would have to be rewritten from scratch to little discernable benefit.
This is an underappreciated value of sticking with a current solution. You know the warts. You know the issues. You have significant sunk costs.
The value of moving to a new solution has to be really really high, because there are always surprises when doing so (business logic that you didn't account for, edge cases that only occur once in a blue moon).
