Live data from Hacker News

Migrating Dillo from GitHub

dillo-browser.org

181–190 of 219 posts

Re: Migrating Dillo from GitHub

#181

We are in the disapora phase; there is a steady stream of these announcements, each with a different GitHub alternative. I speculate that within a few months, the communities will have settled on a single dominant one. I'm curious if it will be one of the existing ones, or something new. Perhaps a well-known company or individual will announce one; it will have good marketing, and dominate.

... and it will be SourceForge. finally.

Re: Migrating Dillo from GitHub

#182
post #60
post #19

I've been messing around with GitLab as a self hosted alternative for a few years. I do like it, but it is resource intensive! For the past few days I've been playing with Forgejo (from the Codeberg people). It is fantastic. The biggest difference is memory usage. GitLab is Ruby on Rails and over a dozen services (gitlab itself, then nginx, postgrest, prometheus, etc). Forgejo is written in go and is a single binary.…

> I'm really excited about Forgejo Our product studio with currently around 50 users who need daily git access moved to a self hosted forgejo nearly 2 years ago. I really can’t overstate the positive effects of this transition. Forgejo is a really straightforward Go service with very manageable mental model for storage and config. It’s been easy and cheap to host and maintain, our team has contributed multiple bugfix…

"Forgejo is also a registry/store for most package managers"

Do you know if it supports OpenWRT packages?

Re: Migrating Dillo from GitHub

#183
post #182
post #60

Earlier quoted context omitted.

> I'm really excited about Forgejo Our product studio with currently around 50 users who need daily git access moved to a self hosted forgejo nearly 2 years ago. I really can’t overstate the positive effects of this transition. Forgejo is a really straightforward Go service with very manageable mental model for storage and config. It’s been easy and cheap to host and maintain, our team has contributed multiple bugfix…

"Forgejo is also a registry/store for most package managers" Do you know if it supports OpenWRT packages?

Since they support Alpine, and the recent switch of OpenWRT to the wonderful alpine apk package manager, I guess it is supported.

Re: Migrating Dillo from GitHub

#184
post #74
post #71

Earlier quoted context omitted.

Wait, forgejo offers a built-in container registry? How does that work? I don't see that in the admin section at all.

Container registry and a lot more, they call it Package registry in the docs https://forgejo.org/docs/latest/user/packages/

Is it not the same as in Gitea? https://docs.gitea.com/usage/packages

edit: Ok, this answers my question: https://forgejo.org/compare-to-gitea/#is-there-a-list-of-fea...

Re: Migrating Dillo from GitHub

#185
post #19

I've been messing around with GitLab as a self hosted alternative for a few years. I do like it, but it is resource intensive! For the past few days I've been playing with Forgejo (from the Codeberg people). It is fantastic. The biggest difference is memory usage. GitLab is Ruby on Rails and over a dozen services (gitlab itself, then nginx, postgrest, prometheus, etc). Forgejo is written in go and is a single binary.…

[deleted]

Re: Migrating Dillo from GitHub

#186
post #74

Earlier quoted context omitted.

Container registry and a lot more, they call it Package registry in the docs https://forgejo.org/docs/latest/user/packages/

Is it not the same as in Gitea? https://docs.gitea.com/usage/packages edit: Ok, this answers my question: https://forgejo.org/compare-to-gitea/#is-there-a-list-of-fea...

[deleted]

Re: Migrating Dillo from GitHub

#187
post #18

Earlier quoted context omitted.

In answer to my own question about in-depth decision making, I just found this presentation from February 2025 by seven-year GitHub veteran Joel Hawksley: https://hawksley.org/2025/02/10/lessons-from-5-years-of-ui-a... Relevant quote: > But beyond accessibility and availability, there is also a growing expectation of GitHub being more app-like. > The first case of this was when we rebuilt GitHub projects. Customers w…

What's nuts about that presentation is that the github frontend has gone from ~.2 to >2 Million lines of code in the last 5-6 years. 10x the code... to get slower?

That also means a much larger team and great possibilities for good perf reviews, so basically an excellent outcome in a corporate env. People follow incentives.

Re: Migrating Dillo from GitHub

#188
post #19

I've been messing around with GitLab as a self hosted alternative for a few years. I do like it, but it is resource intensive! For the past few days I've been playing with Forgejo (from the Codeberg people). It is fantastic. The biggest difference is memory usage. GitLab is Ruby on Rails and over a dozen services (gitlab itself, then nginx, postgrest, prometheus, etc). Forgejo is written in go and is a single binary.…

https://forgejo.org/docs/latest/user/actions/basic-concepts/ It's a shame that GitHub won the CI race by sheer force of popularity and it propagates its questionable design decisions. I wish more VCS platforms would base their CI systems on Gitlab, which is much much better than GitHub actions.

The CI job definitions for sourcehut are a pleasure to use: https://man.sr.ht/builds.sr.ht/manifest.md

A really neat feature is that you can also trigger a job by just submitting a yaml file (with the web interface, the API or the cli) without needing to push a commit for each job. This is neat for infrequent tasks, or for testing CI manifests before committing them.

Re: Migrating Dillo from GitHub

#189

> On the usability side, the platform has become more and more slow over time The best reason right here.

Off-topic, but as a non-native speaker I’m curious if it’s common to say “more and more slow” as opposed to “slower and slower” (maybe to emphasize the adjective?)

Linguistic decay. First they came for our adverbs, now they're attacking our comparative adjectives.

Re: Migrating Dillo from GitHub

#190

We are in the disapora phase; there is a steady stream of these announcements, each with a different GitHub alternative. I speculate that within a few months, the communities will have settled on a single dominant one. I'm curious if it will be one of the existing ones, or something new. Perhaps a well-known company or individual will announce one; it will have good marketing, and dominate.

> I speculate that within a few months, the communities will have settled on a single dominant one.

I really hope not. Heterogeneity is really valuable in this space, and there's really no "one size fits all" model.

Post reply on HN