Roku developer repositories moved from GitHub to GitLab
https://blog.roku.com/developer/gitlab-moveHow so? I used both at work and they're functionally the same.
Choosing one over the other is just a matter of details. How well it integrates with the corporate network, how pretty it looks, the options regarding CI/CD integration, overall popularity and community, etc... Last time I got to choose, I went with Gitea, because performance was good and it met my needs.
This sounds pretty annoying though: https://docs.gitlab.com/administration/license_usage/
And, dare I say it? There is a place for GitLab in a world where most development happens with coding agents. Its perfectly fine to be the version control & CI place. But they got stupid management (just like Atlassian or GitHub) that have convinced themselves they must be the orchestrator, the middleman, the gatekeeper to inference. They neither are nor will be that and if they go down the path of Copilot trying to ruin their product to make it happen, it will be the end.
Deploy contains the released versions and packages.
Operate is for Infrastructure as Code.
Analyze are project and CI statistics.
I doubt you want to remove any of them, they are quite needed functionality.
I don't know that the grass will remain green for very long anywhere in this current scenario.
GitHub is not having most of its outages because GitHub's engineers are using AI (although there might be a case or two of this). The primary driver of the outages is the fact that developers can move so much faster in their workflows. Every single user of these products is placing a heavier demand on the system. I don't think this ramping of demand will cease any time soon. I fully expect to receive an email any second now about how my 5,000 req/hr GH API quota will be cut in half before 2027.
I don't understand how GitLab would be immune from these forces, unless we were willing to reach for self-hosted & enterprise plans. Both of which GitHub offers.
I'm sure most of it is garbage.
does not portend good things for the future
Of course considering who just bought EA (PIF, a Saudi fund + Kushner and some other asshats) and it all makes sense. But I'm still shocked and really sad.
the new incentives do not seem to have served us well, and perhaps worth noting that the same oligarchy controls the algorithms of the new platforms
I have been unable to find an open equivilent of Roku, Apple TV, and Nvidia's Shield, but would be interested in sponsoring an open version via https://bounties.fulu.org/ that could be manufactured through CrowdSupply. An open design and code to run on the hardware avoids future commercial capture. One can then own their media system end to end, from storage, streaming (Jellyfin ecosystem), and hardware on a display.
Not sure if that translates into real demand for it, most consumers are going to consumer.
I recommend Drone.io or WoodpeckerCI for hosting your own CI. It's a very good design; very simple, easy to run, easy to use, integrates with most systems you'd want to, abstracts away components rather than tightly integrating them, and you don't need to be a programmer to use it. So basically the opposite of Dagger.
- Container based workflows are the same in CI and locally (you can run containers too), they become one-liners
- Remote caching out of the box without extra steps
- Multiple language SDKs, unlocks the DAG in BuildKit and containers, real reuse
- Obfuscates secrets from your logs and agents. I've built an agent environment on Dagger, which also includes forking and time travel)
tl;dr - Dagger gives you SDK access to BuildKit and container based DAGs for building or anything else.
v1-beta just released yesterday: https://dagger.io/blog/dagger-10-beta/
---
edit: they are replacing BuildKit (for good reasons) and that is already out https://dagger.io/changelog/theseus/
I'm gearing up for a major rewrite, there is a lot of cruft in there from nearly 10 years of my experiments and explorations :]
I made a game that I thought people might like. I'm trying to offer it to F-Droid and I am encountering pressure to create a GitLab account.
I have been finding it intensely ironic that a project like F-Droid is doing this. It seems like they have, themselves, built processes that have resulted in a form of lock-in that requires others to sign up to GitLab for interoperability.
In specific, off the top of my head:
- you can't group repos
- CI/CD is far behind what GitLab offers
- Review apps (though I think now you can do this on GH with other tools)
- Can't mark PRs as drafts by default in GH
- better metric tracking, easier to see a "snapshot" of where something is at on GitLab
Tbf, GH may have closed some gaps over the years but when I was bouncing between the two GH always felt a lot more rigid and further behind than GL. It did have fantastic support for open source though, and has a few unique and fun things like the `io` site stuff. Overall though if I could choose which to work in for serious projects I'll always choose GL.
Even as an appreciator of multiple Git forges... Github seems good?
As for gitlab...yuck. But whatever. Most of the dev tool space is really just "sh* we have to put up with now", none of it is any good, all of it is dated from the early aughts, and taken as a whole is even worse because none of it works together.
While software development itself got better in the last ten years these tools stayed the same or got worse (enshittification). And this is part of why folks are self hosting.
The other part is that AI is destroying the Internet and its time to pack your bags anyway. The smart people already have.
Same reason we ended up with git. Their predecessors were significantly worse, and then they had enough momentum to keep going.
You broadcasted your negative feedback but it seems you had no positive remarks to give. If you feel everything is so bad, would you mind sharing what tolerable alternatives are there to GitHub and GitLab?
Not the op, and while your criticism of their negativity may be somewhat justified, the ask is kind of silly. There are a bunch of well known alternatives:
Self-hosted free software:
Gerrit <https://www.gerritcodereview.com> Phorge <https://we.phorge.it>
SaaSsy:
Codeberg <https://codeberg.org> SourceHut <https://sr.ht/>
There are a lot more, of course, these are just the ones I have experience with.
Not really. It's pointless to go around accusing everyone of picking what they believe to be subpar alternatives when they even fail to establish what the par actually is, let alone what would be a preferred option.
It's as if they post this blend of comments just to try to feel smug.
> There are a bunch of well known alternatives:
See, that's what makes these exercises pointless. Those might work for your weekend pet projects, where you have the luxury of wasting all Sundays toying with how to deploy CICD systems because you have nothing better to do. For actual work, not so much. For example, SourceHut is renowned for being in perpetual alpha. It's baffling how it's being floated as a reasonable alternative to either GitLab or GitHub. Here's what they have to say about the risk of choosing them at this stage:
> disguised as an open source project
Gitlab CE is open-source. There exist versions of Gitlab with features that require payment. This does not mean that Gitlab (the product) is not open-source; it means that Gitlab (the company) has a core product which is open-source, and then sustains its development through the sale of licenses to product tiers beyond that.
I am even considering hosting my own GIT server myself. Some of our deployments got affected multiple times in the last 6 months alone we were really caught off-guard. Thankfully our clients were understanding of the GitHub outages. But, this should not be the baseline. Reliability should not be the cost of doing business.
[1] https://github.com/creativefoundrysg/desktop#an-open-letter-...
Everyone spent years talking against GPL, business friendly licenses like MIT and Apache were the way of the future, not viral and co.
Now we are here, most projects have their key contributors working at corporations like Microsoft, or gladly getting their acquisition money to pay the VCs, embrace your business friendly licenses.
Every other free service would die nearly instantly, so maybe only want useful things to move to other services.
>I am even considering hosting my own GIT server myself.
It's mostly a good idea.... but, with the current security apocalypse we seem to be under making sure your own shit doesn't get pwned is a full time job. The level of security hostility on the internet recently has reached numbers I've never seen before. RCE's dropping about every day, more targeted scans than I've ever seen in my life, swarms of AI bots breaking into services.
Say annual contracts start at 100k minimum and everyone gets a dedicated support engineer.
You get your own rack. None of this degraded shared capability nonsense.
Does that seem like a solid business ?
I don't need or want a dedicated support engineer for my VCS, I need it to integrate with all the bullshit products I already have, tick off the compliance and governance checkboxes for the suits, give me controls so SWEs do less dumb shit and above all, not be something I have to think about except at contract renewal time.
I'm just not going to trust a rando to run all that for me and get it right, especially not at that price point.
Ideally this would be DevOps as a service. But I’d have to charge an absurd amount of money to do it right.
Back to the drawing board