3 ms·
Gitlab split and rewrote some services in $faster_language. Based on the hires, Github seems to be doing that as well. Gitlab's history with $faster_language h
by pizza234 4y ago
Gitlab split and rewrote some services in $faster_language. Based on the hires, Github seems to be doing that as well.
Gitlab's history with $faster_language has at least some background documentation, e.g. https://about.gitlab.com/blog/2016/04/12/a-brief-history-of-gitlab-workhorse https://about.gitlab.com/blog/2016/04/12/a-brief-history-of-....
They seemed to have liked it, as at least a couple of other services are written in $faster_language - gitlab-shell and gitaly (probably, several others).
There may be more static languages nowadays, but they're very young - I think in real world, there wasn't, pragmatically, a lot of choice, although today's young languages are... still young :)
- bin_bash 4y agoI prefer Go to Ruby so I don't know what you're trying to argue. I just said it requires a lot of boilerplate and that makes it harder to be productive. Technology choice is about trade-offs. It doesn't mean a project is doomed simply because it chose Go. That said, Heroku tried to do a major Go rewrite of their entire backend and the project failed miserably.