He used default-male pronouns in his documentation for Ladybird, and didn't want to change it when some random person made a drive by PR to do so, so a huge Github thread — where a bunch of leftists flew in from left field, who had never cared or known about the project before, let alone contributed to it — started to harass him over it, although those comments seem to have been deleted now.
Then after that, Drew DeVult decided to go after him, digging up and hyperbolically misinterpreting his every tweet to make him look like an, in Drew's words, outright fascist — for instance, confusing objections to affirmative action with belief in White Replacement Theory.
Yes, but, you see, guns are merely tools. If you give these guns to the right people, they will actually create more work for the doctors, and everybody wins.
A couple years ago I wanted to design a custom Nonogram as a birthday present. We had a photo of the giftee and pixelated it. But how do you make sure the Nonogram is uniquely solvable, without any guessing? Of course I wrote a solver in Python.
But now I needed to test the solver. I had a couple of magazines with Nonograms. Transfer those manually into the computer? No way! So I wrote a utility that uses OpenCV to parse these low resolution pixel grids from photos, from the solutions page of the magazine. This was way harder than I imagined. A huge waste of time, but quite a fun project on its own.
For the solver I added one technique after the other. In the beginning it would not be able to solve all puzzles. Then it gradually became more capable, until it would no longer get stuck on the test inputs. A list of techniques like this would have been very helpful!
The solver was still quite slow, but it was really fun to watch it fill in the solution pixel by pixel. It took about 10-20 s to solve the larger puzzles.
I know what you mean, but there is bitrot. I'm currently trying dwm. Zero out of the three patches I downloaded from the website applied successfully. I'd call that bitrot.
Not sure how much I like "hand-write your own code from snippets" as a way to configure software.
One advantage of the patches not working is that manually applying a patch (usually quite simple) brings you some familiarity with the code. In my case this let me make my own modifications that were not available as patches. Altering window manager code is fun!
And while you have a good point, I don’t think this is what most people have in mind when they use the term “bitrot” (but I could be wrong). I say this because dwm as supplied continues to work perfectly without modification. The patches are enhancements contributed by third parties (as far as I know) and, as you’ve discovered, are not maintained.
(Also, once you have a working, patched dwm, it should continue to work forever, even if the patches that you used may no apply automatically to future versions of the base dwm.)
I tried jj, but I'm used to Sublime Merge. Doing version control in the command line was just too much repeated typing, as you keep losing information. In a GUI you always see the current state. You commit, it updates the display. A diff is a click away. Changing focus to type the commit message is a click away. No reason to ask the same questions again and again. Even with aliases like jjl for `jj log --limit 10` it felt too inefficient and annoying. Selecting individual hunks with the keyboard... I don't ever want to do that again. In SM it's a pleasure.
The git CLI might suck, but SM just doesn't. Looking forward to jj GUIs taking off. Or even better: jj getting integrated into SM.
reply