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

51–60 of 219 posts

Re: Migrating Dillo from GitHub

#53

Post by simonw »

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

github is a tool used where code is written: on desktop computers no-one cares about the github mobile experience microsoft making the windows 8 mistake all over again

I interact with GitHub on my mobile phone every day.

Re: Migrating Dillo from GitHub

#54

Post by kijin »

bayindirh wrote: post #27
throwaway150 wrote: post #24

Earlier quoted context omitted.

All of this makes sense. Thank you for explaining. I don't think I understand the difference though. Like are they calling the "GitHub pull request" workflow as the push model? What is "push" about it though? I can download all the pull request patches to my local and work offline, can't I?

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…

You could set up a script that lives in the cloud (so you don't have to), receives PRs through webhooks, fetches any associated diff, and stores them in S3 for you to download later.

Maybe another script to download them all at once, and apply each diff to its own own branch automatically.

Almost everything about git and github/gitlab/etc. can be scripted. You don't have to do anything on their website if you're willing to pipe some text around the old way.

Re: Migrating Dillo from GitHub

#56

Post by tayo42 »

potato-peeler wrote: post #43

I hope you will continue maintaining a mirror in GH. Some tools like deepwiki are excellent resources to learn about a codebase when their is not much documentation going around. But these tools only support pulling from GH.

How is pulling dependent on github?

Git pulling isn't unique to github and it works over http or ssh?

Re: Migrating Dillo from GitHub

#57

Post by blibble »

simonw wrote: post #53
blibble wrote: post #22

Earlier quoted context omitted.

github is a tool used where code is written: on desktop computers no-one cares about the github mobile experience microsoft making the windows 8 mistake all over again

I interact with GitHub on my mobile phone every day.

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

Re: Migrating Dillo from GitHub

#58

Post by input_sh »

potato-peeler wrote: post #43

I hope you will continue maintaining a mirror in GH. Some tools like deepwiki are excellent resources to learn about a codebase when their is not much documentation going around. But these tools only support pulling from GH.

I have the exact opposite experience where I had to block multiple such "excellent resources" from my search results.

Re: Migrating Dillo from GitHub

#60

Post by isodev »

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.…

> 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 bugfixes and improvements and we’ve built a lot of internal tooling around forgejo which otherwise would’ve required a much more elaborate (and slow) integration with GitHub.

Our main instance is hosted on premise, so even in the extremely rare event of our internet connection going offline, our development and CI workflows remain unaffected (Forgejo is also a registry/store for most package managers so we also cache our dependencies and docker images).

Post reply on HN