61–70 of 99 posts
Earlier quoted context omitted.
Having just had to buy 4TB of RAM, I appreciate this.
That's like 100,000 USD. I keep thinking about making a rap video wearing a 10 TB gold chain surrounded by big booty girls with their naughty bits covered in m.2 SSD's while dissing the AI industry. Though I cant afford the RAM :-/
Earlier quoted context omitted.
I suspect some companies may already be considering it. Especially with the wealth of alternatives today.
In my experience companies are moving into GitHub for Copilot and GHA.
Good thing git is a distributed system
I've been looking into having a separate git server that we can commit to and add plain ole git hooks to, and just having it be synced with github as a clone.
Good thing git is a distributed system
Virtually no one knows how to do anything with it outside of github.
I once read someone commenting "Nobody writes code by hand without looking syntax up".
Man, you are just outing yourself as a complete beginner, the field is way deeper than you imagine and it's not even close.
Earlier quoted context omitted.
GitHub on-prem. Officially called GitHub Enterprise Server. You can have GitHub, but hosted on your own servers.
So you still pay them, you do the hosting work, and you get a product with worse features than gitlab?
Perhaps the gemini-cli bot arguing with itself is taking its toll https://github.com/google-gemini/gemini-cli/issues/16750
https://github.com/google-gemini/gemini-cli/issues/16723 is even worse, GitHub shows `5195 remaining items` in the collapsed timeline.
Perhaps the gemini-cli bot arguing with itself is taking its toll https://github.com/google-gemini/gemini-cli/issues/16750
Earlier quoted context omitted.
Things would have to get really bad before I considered managing my own repositories. Trading someone else's headaches for my own.
It depends how high you value your headaches, and how high, your org's downtime. Github not working accrues over the hourly rate of every developer affected, which is likely $70-$100 a hour. 10 hours of outage in a year affecting a team of 10 would cost north of $70k, enough to hire a part-time SRE dedicated just to tend to your Gitlab installation.
10 hours x 10 developers x $70 per hour = $7000, not $70000.
Good thing git is a distributed system
Git is! PRs and code review are not. CI/CD is not. I mean, there are solutions, but none of them seems to have a large enough mindshare and efficiency. (Even though Github's code review tools are pretty spartan.)
They can be. A PR can be made and code review conducted by submitting a patch to a mailing list. That's how the kernel and, I think, git itself is developed.
CI/CD is really a methodology. It just means integrating/deploying stuff as soon as its ready. So you just need maintainers to be able to run the test suite and deploy, which seems like a really basic thing.
Earlier quoted context omitted.
Virtually no one knows how to do anything with it outside of github.
You might be surprised, but that's not true at all. I once read someone commenting "Nobody writes code by hand without looking syntax up". Man, you are just outing yourself as a complete beginner, the field is way deeper than you imagine and it's not even close.
What I am saying is that people learn as much as they need to. They generally don't need to know any more git than is required to interact with github. If anything problematic comes up, they go in with a wrecking ball because they don't truly understand what they are doing. And git has a lot of wrecking balls available.
If you threw them at raw git and asked them to collaborate with someone they'd be up shit creek. They have no idea how SSH or email works for example.