Live data from Hacker News

Migrating Dillo from GitHub

dillo-browser.org

151–160 of 219 posts

Re: Migrating Dillo from GitHub

#151

Earlier quoted context omitted.

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…

What exactly is the advantage of running something like a restaurant vs what I do at home which is just cook it myself? -> convenience, collaboration, mobility

Personal projects that you work on by yourself do not need collaboration. I feel like I pretty clearly implied that in my comment.

Re: Migrating Dillo from GitHub

#152
post #102

Earlier quoted context omitted.

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…

Collaboration and specifically collaboration with non git nerds. That's primarily what made GitHub win the VCS wars back in the day. The pull request model appealed to anyone who didn't want to learn crafting and emailing patches.

I specifically was talking about “personal projects” and excluded PRs for the reason that I would be the only contributor.

Re: Migrating Dillo from GitHub

#153

Earlier quoted context omitted.

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…

This is kind of like asking what the point of Dropbox is when we have rsync. Rsync is nice, but most people won't know how to use it.

Setting up a server with SSH and GitLab is more work than setting up a server with SSH. Dropbox is great and I use it but only because I can’t get the same functionality out of rsync without major additional orchestration. But if I am the only one working on my own project why would I need a second read-only UI for my own code?

Re: Migrating Dillo from GitHub

#155
post #102

Earlier quoted context omitted.

Collaboration and specifically collaboration with non git nerds. That's primarily what made GitHub win the VCS wars back in the day. The pull request model appealed to anyone who didn't want to learn crafting and emailing patches.

I’d argue they if you can’t prepare a patch diff then your abilities as a contributing developer should be thoroughly questioned.

Yes, the projects that are emailing patches around generally have a much higher bar then the ones that accept GitHub PRs, but whatever works for a given project I guess

Re: Migrating Dillo from GitHub

#156
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.

To be fair, the developers might care, but upper management certainly doesn't, and they're the ones who decide if those developers make their rent this month.

Re: Migrating Dillo from GitHub

#157
post #120

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

Why should you need JavaScript to render text and buttons? Were browsers unable to do this prior to the JavaScriptification of everything?

Re: Migrating Dillo from GitHub

#158
So, the first and foremost reason:

> the [GitHub] frontend barely works without JavaScript, so we cannot open issues, pull requests, source code or CI logs in Dillo itself, despite them being mostly plain HTML

because Dillo is a simple browser without a JS engine. And that is a perfectly valid reason to leave GitHub.

Re: Migrating Dillo from GitHub

#159

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

For me (native speaker), I would say "more slow" is incorrect grammar no matter how you use it, though people will know what you mean. So you should say "slower and slower".

Re: Migrating Dillo from GitHub

#160
post #80
post #57

Earlier quoted context omitted.

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.

I think you're very much in the minority, but I guess we can't really know.
Post reply on HN