Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gitlab S-1

sec.gov

Post reply on HN
Print view View original

201–210 of 295 posts

Re: Gitlab S-1

#201

Post by jedberg »

smartbit wrote: post #191
the-dude wrote: post #4

Congrats Sytse.

18.9% shares, not bad. Had a chat with him a few year ago at the gitlab booth at Fosdem. Somewhere around 2014 Sytse asked my former coworker to become gitlab’s first employee, working on Ruby code. Completely understand the request, as he’s an excellent DevOps engineer and fine colleague. He declined to opt for a more secure job position ....

FWIW as the first engineer he might have gotten 1% of the stock, which would be worth about $6M. If he's really that good, there is a decent chance his more secure job has paid that much in 7 years, especially if it was with a FAANG company.

Re: Gitlab S-1

#202

Post by leeoniya »

tln wrote: post #186
klik99 wrote: post #182

Earlier quoted context omitted.

I think it’s about being the dominant player or not, as a long time employee of a very very well known and large company once complained to me “We care about the user experience, but only when we’re not doing well”. Gitlab will continue to impress as long as GitHub exists - I’d start to worry if gitlab “wins”

GitHub seems to care about user experience even though they're winning though.

i've opened multiple, detailed support tickets over the years about different UX wtfs they rolled out that removed vital functionality.

not one of my complaints has ever been addressed. my last complaint was ghosted after i pointed out that they should actually read my lengthy analysis instead of giving a worthless canned response.

still waiting for reply since Jan 4.

Re: Gitlab S-1

#205

Post by Aeolun »

stefan_ wrote: post #189
manquer wrote: post #171

Earlier quoted context omitted.

The theory is lot stronger/valid in enterprise sales like gitlab, customers take a lot of time to switch even if they are not satisfied with a product, there may not viable competitior with bespoke solution the same your current provider gives you etc It is far less true for consumer/SMB mid market products as cost of leaving there is not high.

Oh yeah, I think GitLab will make a fine company. Even if as a user of their product I routinely find it to be half-baked, but of course in enterprise the actual user is commonly the least important aspect of any deal.

> Even if as a user of their product I routinely find it to be half-baked

I thought so too, but then my enterprise started moving to Github. Hoo boy, that’s a whole different can of worms. Their core functionality is great, but if you need anything outside of that you are shit out of luck.

Re: Gitlab S-1

#206

Post by wdb »

nawgz wrote: post #150
wdb wrote: post #102

Earlier quoted context omitted.

NPM Private registry doesn't really work for me with Yarn and NPM v7 when trying to run binaries. This is a major blocker for a lot of things. Also the `npm install` is really flaky multiple times a day I get 404s for packages in the private registry. You need to keep retrying jobs that use that command until succeeds.

I experienced some initial configuration pain with their Package Registry, but after generating PATs for local use and passing secrets thru the CICD build runner nicely - and using yarn - I have had no issues publishing nor installing my own private modules. Here are the commands I suggest you run to authenticate your local machine to GitLab: yarn config set "@example:registry" "https://gitlab.example.com/api/v4/pack…

> I also suggest you fully commit to yarn or npm, they are definitely different enough to be awkward to combine.

I can't even migrate to Yarn because of issues. Try using a package that has binary (`bin` in `package.json`) or other metadata and publish on your private NPM registry and then use it with Yarn or NPM v7 you won't be able to as it strips away this metadata.

For example, if I want to push a patched version of Playwright to my NPM registry. I can't use it if I don't use NPM v6. Also the daily 404s errors when trying to install your private NPM packages which requires retry your jobs isn't help either.

Sadly it's not an important enough issue for them to fix. I am really wondering if Gitlab is using their products themselves.

Re: Gitlab S-1

#207

Post by Aeolun »

snicker7 wrote: post #82

The big issue we have with GitLab is the pricing. Ultimate is literally five (!!!) times more than premium. And there are only a couple of features that we want from ultimate.

Also, pay only per year, instead of per month. So if you even want to get started you better be ready to fork over $1200 per developer immediately.

I can say a lot of bad things about Atlassian, but their price/benefit ratio is outstanding.

Re: Gitlab S-1

#208

Post by paulryanrogers »

tln wrote: post #186
klik99 wrote: post #182

Earlier quoted context omitted.

I think it’s about being the dominant player or not, as a long time employee of a very very well known and large company once complained to me “We care about the user experience, but only when we’re not doing well”. Gitlab will continue to impress as long as GitHub exists - I’d start to worry if gitlab “wins”

GitHub seems to care about user experience even though they're winning though.

GitHub SAAS consumer experience. It doesn't go as far for users who would like to run their own GH instance as open source. And in some areas GitLab has done better, such as CI.

Re: Gitlab S-1

#209

Post by wdb »

Gitlab CI pipelines also validation errors in the Pipeline editor but when you then run it's all good. Super confusing these errors which aren't errors issues. Such a time sink
Post reply on HN