However, I consider that there is still not a great UI for the core service, in special for a complex project.
In the other hand, I bet jujutsu has the best basic take, and is still missing a good forge.
With what I heard about GitHub Actions, the GitLab CI pipelines should be much better.
Not that I haven’t shot myself in the foot with GitLab pipelines on numerous occasions.
At first I thought the KDE apps all playing on the K was kinda weird and awkward, but as time went on I really appreciated how easy it was to search for them due to this. So I really think it's a benefit to play on traditional words rather than use them as-is.
jjplace/jjhub/codetown, whatever. Doesn't matter.
Names don't matter that much for brands. Names just have to be simple enough to remember (ideally two syllables or less). What the heck does Nike mean, for example? Boeing is just someone's name. Microsoft is just two words smashed together. A brand's name literally doesn't matter.
I would guess under 10%, and only that high because Nike sells shoes in Greece and Italy.
("Please don't sue us.")
And then impose the same requirements that killed GitHub in the first place.
- "Uuh, no"
Be a pretty quick story
If AI replaces software development the way that big tech company management wants it to, maybe they'll converge again. In the mean time, people want a git remote and they're getting an unstable host diluted with some flaky vibecoding bullshit.
Hosting a Docker container is a full-time job? I have worked at several employers self-hosting their own instances without issues or a lot of effort. Many FOSS projects do, that definitely do not have a full-time guy for that. What are you talking about?
I imagine requirements and integrations may differ a lot. I have seen many incidents with a large instance.
if you accept the performance hit, it's great quality software though.
however, a fairly large company with 100-120 users (developers, devops engineers, QAs etc) and ~600 gitlab runners ran happily on a 8 core / 64gb virtual machine (hosted on a local vmware cluster).
so it is (was?) also fairly cheap.
It'll probably never happen. But it'd be really nice if it did.
It's a bit short of actual PRs, but in some ways, especially with agents, the lo-fi approach has some advantages.
Also nice language evolutions: "socialize their changes to projects", "lo-fi approach" :)
Do you know that you can just send a patch via email (assuming you're not using the gmail web client)? You can even save the diff on some hosting website and send the link via any text medium.
Really? I can only think of two: Codeberg and Sourceforge. Which are both great, but that's not what I'd call "many".
I guess it's possible that my experience is wildly different than others, but if we're talking about volume of usage today rather than individual preferences, it's kind of shocking for me that someone wouldn't think to reference Gitlab at all in the list of potential successors, let alone not mention it literally first.
> Really? I can only think of two: Codeberg and Sourceforge. Which are both great, but that's not what I'd call "many".
- frequently needed navigation links buried within menus within other menus
- menus labeled by mysterious icons, sometimes with mysterious text, sometimes with no text at all
- authentication system that has failed me in a variety of ways over the years, even locking me out of an account in one case
- client-side script execution required to do anything all, even simply display a file
As I said, I haven't kept a list, but GitLab is very much in the category of interfaces that were built by javascript fanatics who don't understand (or don't care about) ergonomics or privacy. I accept that not everyone is bothered by its many problems, but I avoid it when I can.