Hacker Newsnew | past | comments | ask | show | jobs | submit | connorshea's commentslogin

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


We are actually starting work on allowing pasting images from the clipboard this week :D

So stay tuned!

Thanks for the kind words, the team really appreciates it.


This makes me so happy, thank you! :D


The issue in question for anyone curious: https://gitlab.com/gitlab-org/gitlab-ce/issues/28996

I'm looking forward to it as well :)


Not OP but anything that makes the process smoother is good IMO :)


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).


For more background an overview is available at https://about.gitlab.com/handbook/marketing/product-marketin...


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).

https://gitlab.com/gitlab-org/gitlab-ce/issues/19232


Not Sid, but thanks for being a fan ;)


Mirroring is an Enterprise Edition feature but there are probably ways to hack around that.


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".

You can see the hardware requirements here: https://docs.gitlab.com/ce/install/requirements.html#hardwar...


I mean, I don't use GitLab but I didn't really mean it disparagingly - for the OP's purpose, GitLab is massive overkill, and will need a lot more resources than a more targeted solution will.


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.

[0]: https://gitlab.com/gitlab-org/gitaly


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: