blog

Source files for chris.bracken.jp
git clone https://git.bracken.jp/blog.git
Log | Files | Refs | Submodules | README | LICENSE

commit 97891f93b46d4d3dfb4844a22267fa6e951b3e8a
parent 8749f0fe820bf6237c9aa2d9342e79eafe8c25fc
Author: Chris Bracken <chris@bracken.jp>
Date:   Fri, 13 Nov 2020 15:32:42 -0800

Clean up code repos list

Eliminate one of these options; after one year of trying it out, I
decided it's not something I'm willing to pay for again.

Pros:
* Email-based patch workflow.
* Minimalist, lightweight user interface.
* No JavaScript

Cons:
* Markdown rendering much uglier than GitHub, GitLab, Gitea and others.
* Paid service. GitHub, GitLab, Gitea, all over storage unpaid.
* Owner generally acts like an asshole online, and while I agree with
  many of his views on minimalism, decentralisation, and the awful state
  of the web. I'd prefer not to fund people who can't express their
  points in good faith and without resorting to fallacious logic.

Diffstat:
Mcontent/code.md | 7++-----
1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/content/code.md b/content/code.md @@ -5,13 +5,10 @@ title = "Code" You can find most of the public code I contribute to hosted at one of the following sites: -* [sr.ht](https://git.sr.ht/~cbracken/): Lightweight, no-nonsense UI and - support for email-based contribution workflows. This is where most of - my own repos lie. -* [GitLab](https://gitlab.com/cbracken/): Better features and UI than - GitHub. Web markdown support is currently more legible than sr.ht. * [GitHub](https://github.com/cbracken/): The most popular source code hosting solution and where most of my public contributions lie. +* [GitLab](https://gitlab.com/cbracken/): Better features and UI than + GitHub. ### Significant contributions