Live data from Hacker News

Migrating Dillo from GitHub

dillo-browser.org

71–80 of 219 posts

Re: Migrating Dillo from GitHub

#71
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…

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

Re: Migrating Dillo from GitHub

#72

Earlier quoted context omitted.

GitHub pull request pushes you a notification/e-mail to handle the merge, and you have to handle the pull request mostly online. I don't know how you can download the pull request as a set of patches and work offline, but you have to open a branch, merge the PR to that branch, test the things and merge that branch to relevant one. Or you have to download the forked repository, do your tests to see the change is relev…

Seems like you found it, but for others: one of the easiest ways to get a PR's diff/patch is to just put .diff or .patch at the end of its URL. I use this all the time! Random PR example, https://github.com/microsoft/vscode/pull/280106 has a diff at https://github.com/microsoft/vscode/pull/280106.diff Another thing that surprises some is that GitHub's forks are actually just "magic" branches. I.e the commits on a for…

It’s bonkers to me that there isn’t a link to the plan patch from the page. Yes, it’s trivial to add a suffix once you know, but lots of people don’t—as evidenced by this thread.

Discoverability in UX seems to have completely died.

Re: Migrating Dillo from GitHub

#73
post #45
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.…

If you want even more minimal, Gerrit is structured as a Java app with no external dependencies like databases, and stores all it's configuration and runtime information on the filesystem, mostly as data structures in the git repos. Shared filesystems is all you need to scale/replicate it, and it also makes the backup process quite simple.

I might be one of the few that is intrigued by this being that it’s Java but this looks really neat. Does it do git repositories like gitea, GitHub, etc, or is it more of a project management site for the repositories? They describe it as “code review”, so I wasn’t sure.

I’m a little put off on the google connection but it seems like it could run rather independently.

Re: Migrating Dillo from GitHub

#74
post #71
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…

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/

Re: Migrating Dillo from GitHub

#75

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

For real. I've been hearing the interface is slow and requires Javascript for years and never really paid much mind, it worked for me. But lately the page loading has gotten abusively slow. I don't think it can be simply blamed on React because that move was made long before this started.

I've taken to loading projects in github.dev for navigating repos so I pay the js tax just once and it's fine for code reading. But navigating PRs and actions is terrible.

Re: Migrating Dillo from GitHub

#76
post #5
post #2

>frontend barely works without JavaScript, ... In the past, it used to gracefully degrade without enforcing JavaScript, but now it doesn't. And the github frontend developers are aware of these accessibility problems (via the forums and bug reports). They just don't care anymore. They just want to make the site appear to work at first glance which is why index pages are actual text in html but nothing else is.

Having to enable javascript to see a website is not an accessibility problem according to WCAG.

There's 'enabling javascript' and then there's 'requiring a javascript VM with bleeding edge features basically only found 3 browsers'.

Re: Migrating Dillo from GitHub

#77
post #36
post #2

>frontend barely works without JavaScript, ... In the past, it used to gracefully degrade without enforcing JavaScript, but now it doesn't. And the github frontend developers are aware of these accessibility problems (via the forums and bug reports). They just don't care anymore. They just want to make the site appear to work at first glance which is why index pages are actual text in html but nothing else is.

https://github.com/orgs/community/discussions/62372#discussi...

It's 1 step forward 2 steps back with this "server side rendering" framing of the issue and in practice observing Microsoft Github's behaviors. They'll temporarily enable text on the web pages of the site in response to accessibility issues then a few months later remove it on that type of page and even more others. As that thread and others I've participated in show this is a losing battle. Microsoft Github will be javascript application only in the end. Human people should consider moving their personal projects accordingly. For work, well one often has to do very distasteful and unethical things for money. And github is where the money is.

Re: Migrating Dillo from GitHub

#78
post #18
post #13

Earlier quoted context omitted.

I'd love to hear the inside story of GitHub's migration of their core product features to React. It clearly represents a pretty seismic cultural change within the company. GitHub was my go-to example of a sophisticated application that loaded fast and didn't require JavaScript for well over a decade. The new React stuff is sluggish even on a crazy fast computer. My guess is that the "old guard" who made the original…

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…

Who has ever used github on mobile?

I'd like to see their logs about this.

Re: Migrating Dillo from GitHub

#79
post #6

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.

This has been going on for a decade, at the beginning it was projects moving to Gitlab now there's a lot of alternative projects but GitHub is still the only one that counts for discoverability. This is a very small minority of projects that move away from Github and it's way too early to declare GitHub doomed.

No different than everyone talking about the next “iPhone Killer” when someone other than Apple releases a phone. Although, I think that rhetoric has largely died down.

Re: Migrating Dillo from GitHub

#80
post #57
post #53

Earlier quoted context omitted.

I interact with GitHub on my mobile phone every day.

yeah and I bet three people used Windows 8 on tablets too.

I think you are wildly underestimating how common it is for people to use GitHub from a phone.

It's where I interact with notifications about new issues and PRs for one thing. I doubt I'm alone there.

Post reply on HN