I've been using Sorbet on a personal project (https://github.com/connorshea/vglist) for almost two years now, and it's been great (although I've had to build myself a lot of tooling for it over time).
I don't think I'll use the compiler (for now, at least), but I'm very interested in seeing how it grows over time :)
As a user of the iOS app it used to have some admittedly frustrating problems, but pretty much every complaint I had previously has since been fixed, huge kudos on the progress you've made!
The only thing left that really bugs me is the fact that you can't paste images from the clipboard into the message field. It's made me change my entire workflow, from copying images to saving them.
Sorry to use this as a soapbox for my pet issue, but I saw the opportunity :P
Libre/Starter/Premium/Ultimate are the names of plans for our distributions. CE and EE are distributions of GitLab. CE has _only_ FOSS code in it for users (e.g. self-hosting open source projects) who don’t want to run any proprietary code whatsoever. Libre features are any features that are in the CE distribution by default.
The Free/Bronze/Silver/Gold plans are for GitLab.com specifically (all open source projects get Gold features by default).
We also have an issue for running jobs only when modifications are made to a given file or files in a directory, it's tentatively scheduled for 10.7 (April's release).
We actively try to make improvements so GitLab uses fewer resources, but with the scope of the application it's definitely not easy to make it super "lightweight".
There are no plans to migrate all of GitLab to Go. The main Rails app is going to stay a Rails app for the foreseeable future. There are a few reasons for this. For one it'd be such a huge project, but also Rails is working well for us, it's great for our pace of feature development.
We are working on moving the git layer to Gitaly[0] which is written in Go (and is what this blog post is about). It was one of our major bottlenecks and we've seen a lot of benefit from having made the switch. It's not done yet, but a lot of the calls to git that the application makes are now done through Gitaly.
See our Stewardship page[0] for how we determine what goes in EE vs. CE, for now Burndown Charts will stay in EE. As for EBS, feel free to open an issue for it[1] since I couldn't find one :)
Thanks for the feedback, I looked into it and it looks like neither of these problems have been fixed as of yet. I've asked the CI and UX teams if we can work on the Environments page.
For what it's worth, in the last year (since January 23, 2017) we've merged ~440 merge requests labeled "performance"[0]. It's not perfect right now and there's still plenty of work to do, but compared to when I started at GitLab almost two years ago it's night-and-day.
We've also got an entire team dedicated to porting our Git layer to Go with Gitaly[1], which has been a major bottleneck that we've started resolving over the last year or so.
We do have support for macOS and Windows in Runner, though you'll have to run them yourselves. We're looking into offering hosted macOS and Windows Runners for the future, but we have no solid timeframe for those right now. https://gitlab.com/gitlab-com/infrastructure/issues/3183
API v3 is still supported in the latest GitLab release (and will also be supported in this month's release, as well as probably the next few since we haven't decided the exact date of deprecation yet), have we communicated this incorrectly somewhere?
I don't think I'll use the compiler (for now, at least), but I'm very interested in seeing how it grows over time :)