syklemil

I work at a Linux-dominant shop. Macs are somewhat common. People with Windows are kind of seen as weirdos.

We don't use office packages all that much either; more geared towards markdown and git and programming languages. The office package I use the most is Google's.

I haven't had a machine with windows on it since Windows ME. I do have some training in windows server from over a decade ago (nearing two maybe?), but I've never used the knowledge.

Let's just say that ME deserved its "Mistake Edition" moniker

Yeah, the usual argument for not picking GPL with Rust is based on how it applies to static linking, which is how Rust works by default. But the coreutils are executables, not libraries.

Even for the libraries I think it'd be nice with some stronger guarantees. Allegedly the EUPL is copyleft but allows static linking, so probably something to look into.

Ah well. At least it's also possible for orgs like GNU to re-release forks of MIT stuff as GPL. The MIT licensing doesn't only work for the proprietary-preferring orgs.

We have nearly all electric buses here in Oslo now, and whenever I wind up on a diesel bus I think I'm going to get hearing damage

Electric buses are far from silent, but WOW the amount of noise and stink we've just been tolerating with fossil fuels is insane. Even absent climate change, that'd be worth switching to electric vehicles.

Yeah, Ubuntu actually isn't the first distro without GNU coreutils. Beyond Android and Busybox, there's also stuff like Talos, which is something like … Kubernetes/Linux.

IME something like Kubernetes/Linux running "distroless" containers have a huge potential to displace traditional GNU/Linux in the server market, and I wouldn't be surprised if someone manages to build a desktop out of it, either.

Also doesn't help that the grammar reeks of LLM.

I'm also a fan of baud. I really should alias cat to baud -400 cat or thereabouts.

Bonus: run baud -800 bat --color=always and you get that wonderful old dot matrix printer feeling of the cursor just stopping whenever the color codes are being processed.

Be kind, rewind.

re: mksh I have snippets in my editor for shebangs++. E.g. #!<tab><enter> nets me

#!/bin/bash
set -euo pipefail

or

#!/usr/bin/env python3
# pyright: strict

etc

.nl

checks out

They are utility, as long as you don't have a theme that randomly picks a new colour every time the token type changes.

It's a bit like having a bunch of different tools or utensils in separate colours. Even if the drawer is messy and the colour ultimately arbitrary, you can pick out utensils because you're habituated to looking for a given colour.

Just stick to one theme and you'll get the same thing but for code. Theme hopping kills your habituation, and resets you to the "I can tell that these are different things because the colours are different" stage.

The stance coupled with the garish background colour reminds me of how Pike also had a very dismissive view of using colours for syntax highlighting, and then later opened up about having a kind of colourblindness.

Both of them also seem to mean colour when they write syntax highlighting. That's just one typographic tool among many. We also use bold, italics, underline, and even whitespace to highlight programming syntax. We could write a lot of programming languages as if they were prose, but we don't. People hate that and call it "minified code".

Humans also have a great capacity for colour vision, much better than most mammals. Some of us are even tetrachromats. Our colour vision is basically a free channel of information: It's always on; we don't have to concentrate to be able to discern most colours. When things in nature are more colourful than usual, like leaves in fall or a colourful sunset, we don't find it tiresome; we find it refreshing and seek it out. But when our built environment becomes all shades of grey, we tend to find it depressing.

But humans are also different in many ways here. Better or worse colour vision is one thing, but some are also prone to getting overstimulated; others require more than average stimuli. We have great selective attention as a species, but again, individuals vary. There's no one syntax highlighting that works for everyone.

Ultimately we should just find some syntax highlighting that we find generally pleasant, and then stick with it until we reflexively use the information carried in those colours. Use habit formation for our benefit.

Tonsky may enjoy his garish background colour and have found a mushy colourscheme that works for him, but he's also way off base in his assessment of colourschemes in general.