Live data from Hacker News

GitLab acquires Gitter, will open-source the code

venturebeat.com

151–160 of 333 posts

Re: GitLab acquires Gitter, will open-source the code

#151

Somewhat off topic, but I was once very interested in working for GitLab. According to their compensation calculator, though, I'd be making less than half what I make now (also working remotely). They ding me for living in a comparatively low cost area. I'm surprised they are able to attract talent to achieve what they have done so far. It makes me worry somewhat about my future prospects in an increasingly globalize…

This has been discussed quite a bit on HN in the past with the general sentiment that their calculator is very off from the market in the US.

Re: GitLab acquires Gitter, will open-source the code

#152

Somewhat off topic, but I was once very interested in working for GitLab. According to their compensation calculator, though, I'd be making less than half what I make now (also working remotely). They ding me for living in a comparatively low cost area. I'm surprised they are able to attract talent to achieve what they have done so far. It makes me worry somewhat about my future prospects in an increasingly globalize…

job prospects or salary ? because they are entirely different things.

Re: GitLab acquires Gitter, will open-source the code

#153

Earlier quoted context omitted.

Do we know what protocol Gitter runs on top of?

Gitter uses a proprietary websocket protocol built on top of the Bayeux protocol: https://docs.cometd.org/current/reference/ More details can be found on the developer site: https://developer.gitter.im/docs/faye-endpoint We also have an open-source IRC bridge: https://github.com/gitterHQ/irc-bridge

And there is a matrix.org/gitter bridge already in use by riot.im

Re: GitLab acquires Gitter, will open-source the code

#154
post #60

Earlier quoted context omitted.

I started a new project recently, and put it on Gitlab instead of GitHub. I'm very pleased so far, and have been finding reasons to justify encouraging others to move projects there as well.

I'm very glad to hear that. What are the reasons that you think will encourage others?

The biggest thing I think would encourage more projects to move is improving discoverability. On Github, I can very easily search for new projects to contribute to, and their Explore page [1] is very nice. Gitlab's, on the other hand, doesn't seem to have a way to browse by category like Github.

For everything else, I like Gitlab a lot -- it seems to have the best integration of tools of any code host.

[1]: https://github.com/explore

Re: GitLab acquires Gitter, will open-source the code

#157

Earlier quoted context omitted.

GitHub has that too, I noticed the other day. I still think Gitlab is much better, and use it by default for everything new, but fair's fair :P I love the integrated CI, though, and the use cases it enables. I love that I can just make a pipeline that lints, tests and compiles my code and then, if all of those pass, ends with deploying it to production. There are many more Gitlab features I like a lot, and the fact t…

It took forever for GitHub to get protected branches. It was quite frustrating. Glad they finally have it though.

It took forever for GitHub to get anything, until Gitlab lit a fire under their ass. GitHub were perfectly content just resting on their laurels while every essential feature was handled by a different $15/mo third party service.

Re: GitLab acquires Gitter, will open-source the code

#158
post #85

Earlier quoted context omitted.

We hear you and agree, GitLab.com is too slow. We're working on multiple things to improve it https://gitlab.com/gitlab-com/infrastructure/issues/947 GitLab 9.1 will have lots of performance improvements for database queries. The GItaly team is working hard to move git commands to the fileservers to reduce latency, that will happen in about a month from now.

Idea: put the performance plots from tickets on https://arewefastyet.gitlab.com Mozilla does this to great effect: http://www.arewefastyet.com/ https://areweslimyet.com/ http://www.arewewebyet.org/

Great idea! We've just forwarded http://arewefastyet.gitlab.com/ to http://monitor.gitlab.net/dashboard/db/fleet-overview

This doesn't show all the graphs we need to show like 99th percentile request latency but that will come when we add Unicorn support to Prometheus.

Re: GitLab acquires Gitter, will open-source the code

#159
post #129

Somewhat off topic, but I was once very interested in working for GitLab. According to their compensation calculator, though, I'd be making less than half what I make now (also working remotely). They ding me for living in a comparatively low cost area. I'm surprised they are able to attract talent to achieve what they have done so far. It makes me worry somewhat about my future prospects in an increasingly globalize…

Senior Backend Engineer shows 85-95k in Chicago, which is below average. It shows 45-55k for Fayetteville -- most junior guys/gals start around 75k in Fayetteville at mediocre companies.

Yeah, similar for me. In my geo it shows ~87-98K, but if I moved to San Francisco it is ~173-189K. Which seems foolish. They should incentivize people to move to the lower costs geos, not penalize them.

And the listed salary for my geo is about 2/3 to 3/4 of my current base pay before any bonuses. The idea of the company sounds good, but the pay is a deal breaker for me. I wouldn't like feeling like I'm providing the company more value but because the person lives in San Francisco they get twice as much pay. Maybe that is me being petty?

Post reply on HN