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

121–130 of 219 posts

Re: Migrating Dillo from GitHub

#121

Post by arccy »

hk1337 wrote: post #73
zdw wrote: post #45

Earlier quoted context omitted.

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.

It necessarily hosts a git server (using jgit), but the primary interface is as a code review tool.

even browsing the git repos it hosts uses an embedded version of another tool (gitiles).

https://gerrithub.io/ is a public instance

Re: Migrating Dillo from GitHub

#122

Post by II2II »

jmspring wrote: post #84
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.…

One concern the post brings up - single point of failure. Yes, in this case, blah blah big company microsoft blah blah (I don't disagree, but..). I'm more worried about places like Paypal/Google/etc banning than the beast from Redmond. Self hosting, it's still a single point of failure and the article arguing "mirroring", well... it allows redundancy with reads but writes? It's an interesting take on a purist problem…

I found the banning comment to be odd. That said, all it really takes is a policy change (something that I see as far more likely in Microsoft's case) or simply a change in the underlying software (again, somewhat likely with Microsoft) for the platform to become unusable for them. Keep in mind that Dillo is a browser for those who can't on don't want to fit into the reality of the modern web.

Re: Migrating Dillo from GitHub

#123

Post by layer8 »

> GitHub seems to encourage a "push model" in which you are notified when a new event occurs in your project(s), but I don't want to work with that model. Instead, I prefer it to work as a "pull model", so I only get updates when I specifically look for them.

I agree with the sentiment, but want to point out that email can be used to turn push into pull, by auto-filtering the respective email notifications into a separate dedicated email folder, which you can choose to only look at when you want.

Re: Migrating Dillo from GitHub

#124

Post by CuriouslyC »

dewey wrote: post #6
the__alchemist wrote: post #3

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.

Github is fine for discoverability but as a development platform I think it's going to die. Public issues/PRs are a cesspool now and going to get worse, and agentic workflows are going to drive companies to want to hide how the sausage is made. People will gradually migrate to alternatives and mirror to Github while it remains relevant.

Re: Migrating Dillo from GitHub

#125

Post by cess11 »

simonw wrote: post #13
superkuh wrote: 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.

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…

If it's fast people don't stick around for as long. Make it sluggish and you get more stonks analytics.

Re: Migrating Dillo from GitHub

#126

Post by dewey »

CuriouslyC wrote: post #124
dewey wrote: post #6

Earlier quoted context omitted.

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.

Github is fine for discoverability but as a development platform I think it's going to die. Public issues/PRs are a cesspool now and going to get worse, and agentic workflows are going to drive companies to want to hide how the sausage is made. People will gradually migrate to alternatives and mirror to Github while it remains relevant.

I’d guess most revenue comes from enterprise accounts which are not public.

Re: Migrating Dillo from GitHub

#127

Post by gorgoiler »

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…

You don’t! Forges are for collaboration outside of the rhythm of git commits. You’re happy to make a new commit every time you have something to add to an issue. With X issues and Y comments a hour, polluting the git timeline with commentary is going to become unhelpful.

Some forges even include(d) instant messaging!

https://secure.phabricator.com/Z1336

Re: Migrating Dillo from GitHub

#128

Post by marginalia_nu »

llbbdd wrote: post #120
marginalia_nu wrote: post #37

Earlier quoted context omitted.

It is a very real accessibility problem if you're using Dillo, which does not support javascript.

it's also a real accessibility problem if you're trying to use sticks and rocks to access the internet

This is in the context of where that web browser is hosted, so it's quite relevant.

Re: Migrating Dillo from GitHub

#129

Post by hahn-kev »

emfrosztovis wrote: post #115
0x696C6961 wrote: post #47

> 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?)

Slower and slower is more natural to my ear. More and more slow sounds weird.

Re: Migrating Dillo from GitHub

#130

Post by mbreese »

dvdkon wrote: post #107
c-hendricks wrote: post #29

Earlier quoted context omitted.

When I self hosted gitlab I never found the maintenance to be that bad, just change a version in a compose.yml, sometimes having to jump between blessed versions if I've missed a few back to back. Like others, I've switch to Gitea, but whenever I do visit gitlab I can't help but think the design / UX is so much nicer.

My usual impression of GitLab is that it has too many functions I don't ever use, so the things I actually do want (code, issues, PRs, user permissions) are needlessly hidden. What's your workflow that you find GitLab's UX to be nicer than Gitea's?

That was my take too. It is a big project with a lot of functionality. But, I never needed all of that functionality, so it just seemed bloated to me. I switched over to Gitea for self-hosted code repositories (non-public repos behind a firewall) a while back and haven't had any issues thus far.
Post reply on HN