Notices by Drew DeVault (sir@cmpwn.com)

Summary of my Mastodon account:

- Almost all software is terrible- Use Plan 9- Angry programmer noises

Programmers are computing enthuasists

Computing enthusiasts typically have enthusiast-grade hardware

Programmers cannot empathize with the plight of someone on a $100 netbook

This explains bloat

???? scp???? rsync???? ssh example.org tee file.txt < file.txt

tar -c some-dir/* | ssh example.org tar -xv

Turns out google translate cannot translate 上代日本語 into... anything

Compared to GitHub and GitLab, SourceHut wins by objective measurements in all of these categories:

✓ Free software✓ Reliability✓ Performance

@brown121407 @lain he probably means pull requests because the lack of them is a thing naysayers often feel is an affront to their sensibilities

@lain @brown121407 @brettgilio I didn't say anyone was stupid for wanting these features

sr.ht provides most of what you mentioned here. Perhaps not with the same workflow, but that's a feature, not a bug.

The US is basically a totalitarian state where the power is exclusively held by rich corporations rather than by government officials

Web browsers need to stop

https://drewdevault.com/2020/08/13/Web-browsers-need-to-stop.html

An object can be a blob, tree, commit, or tag. An object is identified by its ID, which is a SHA.

A blob is just some arbitrary data. Files are represented as blobs.

Trees are a list of blob IDs and other tree IDs, and their names. Directories are represented as trees.

A commit has a tree ID, an author, a date, a parent commit ID (or IDs, for a merge commit), and a commit message.

A reference is just a commit ID. Branches are a kind of reference. The only information which is stored to represent "master" is the ID of the latest commit. To get the commit log, you just follow the parent ID in each commit. To get the contents, you look at the tree ID of that commit. To update master, create a new commit and write its ID to .git/refs/heads/master (which is a plaintext file).

A tag has a commit ID, an author, and a message. It just calls out a specific commit as special, like a release number, and adds a message, such as that version's changelog.

All git commands are just a means of manipulating what is ultimately a very simple data store. If you want to know more about how a specific command works and how it relates to this data store, let me know.

The falsehoods of anti-AGPL propaganda

https://drewdevault.com/2020/07/27/Anti-AGPL-propaganda.html

#blog