Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Migrating Dillo from GitHub

dillo-browser.org

Post reply on HN
Print view View original

171–180 of 219 posts

Re: Migrating Dillo from GitHub

#171

Post by zzzeek »

> This is specially problematic when active issues with developer notes begin to be filled with comments from users that have never contributed to the project and usually do more harm than good. This situation ends up causing burnout in developers.

This is a huge with github and I would desperately want a github where issues are visible, but the ability to create or modify them is STRICTLY locked down to project members, and non members can only post Discussions for problems. I really prefer that I write the issue(s) based an "intake discussion" so to speak.

Re: Migrating Dillo from GitHub

#172

Post by mroche »

estimator7292 wrote: post #64
homebrewer wrote: post #25

Earlier quoted context omitted.

Ease of maintenance is an even bigger difference. We've been using gitea for a bit over five years now, and gitlab for a few years before that, and gitea requires no maintenance in comparison. Upgrades come down to pulling the new version and restarting the daemon, and take just a few seconds. It's definitely the best solution for self-hosters who want to spend as little time as possible on their infrastructure. Back…

I found gitea's interface to be so unusably bad that i switched to full-fat GitLab. Gitea refused to do some perfectly sensible action- I think it had something to do with creating a fork of my own repo. Looking online, there's zero technical reason for this, and the explanation given was "this is how GitHub does things". Immediately uninstalled. I'm not here for this level of disrespect.

I found gitea's interface to be so unusably bad that i switched to full-fat GitLab.

Was this Gitea pre-UI redesign or after? 1.23 introduced some major UI overhauls, with additional changes in the following releases. Forejo currently represents the Gitea 1.22 UI, reminiscent of earlier GitHub design.

Re: Migrating Dillo from GitHub

#173

Post by cxr »

simonw wrote: post #170
yeasku wrote: post #166

Earlier quoted context omitted.

Saying your life is about filling PRs on you phone while walking your dog is not the flex you think it is.

These are PRs against my own personal projects. I enjoy hobbies. Criticizing other people's hobbies isn't the flex you think it is.

Neither one of those comments should have received replies. Just flag and move on.

Re: Migrating Dillo from GitHub

#174

Post by kragen »

IgorPartola wrote: post #99
xrd wrote: 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.…

What exactly is the advantage of running something like GitLab vs what I do which is just a server with SSH and a file system? To create a new repo I do: ssh example.com ‘mkdir repos/my-proj.git && cd repos/my-proj.git && git init —bare .’ Then I just set my remote origin URL to example.com:repos/my-proj.git The filesystem on example.com is backed up daily. Since I do not need to send myself pull requests for persona…

CI runners would be the main advantage of GitLab over bare Git, I think. Also if you want to show other people your personal project at some point, it may be nice to be able to link to a diff or a historical version of a file that they can see in a browser. Or just a syntax-highlighted file or a rendered Markdown or Jupyter file. Also previous release tarballs.

Re: Migrating Dillo from GitHub

#177

Post by sunaookami »

simonw wrote: post #18
simonw wrote: 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…

What does "app-like" even mean? It's a website, not an app. Don't they have a native app for phones?

Re: Migrating Dillo from GitHub

#178

Post by lioeters »

kragen wrote: post #176
toastal wrote: post #51

Earlier quoted context omitted.

I wish Tangled supported alternatives to Git

Darcs? Fossil? Subversion?

On their home page they have links to some repositories (or equivalent term) on a couple of Darcs hosts.

https://hub.darcs.net

https://smeder.ee

Here's a recent discussion about Darcs, it's the first I've heard of it.

Darcs, Friendly Version Control - https://news.ycombinator.com/item?id=43022059 (9 months ago | 76 comments)

Re: Migrating Dillo from GitHub

#180

Post by rafaelgoncalves »

WD-42 wrote: post #30

> To avoid this problem, I created my own bug tracker software, buggy, which is a very simple C tool that parses plain Markdown files and creates a single HTML page for each bug. The hacker spirit alive and well.

got here to comment on that, hella impressive and looks so simple and clean.
Post reply on HN