Not all communities I want to follow made the transition. I'm still on Reddit for HFY, and some smaller game communities.
But Lemmy has replaced a sizable chunk of my Reddit usage, especially around more technical topics.
It requires a phone number to log in. That already kills any hope for anonymity. I use it to message family and close friends, of which the fact that I'm messaging them is not surprising.
I run my Nextcloud behind Tailscale, and Caddy handles theTailscale https certs.
That's because it was a regression from 1.5 to 1.6 that got fixed.
The 10x speedup is in linking builtins during startup, so it's only really seen for very small inputs.
xkb has been split off from Xorg, all Wayland compositors (that I know of) use it for mapping.
in the OP
My reply is to a commenter who said they prefer "${HOME}/docs" over both options in the original image ("$HOME/docs" or "$HOME"/docs). Many people prefer to always include braces around the parameter name out of consistency, instead of only when they are required.
My comment explained why my habit is to only include braces when they are necessary.
It's interesting, the results here are way different than the Code Golf & Coding Challenges Stack Exchange. I would never expect Haskell to be that low. But after looking at code.golf, I realize it's because I/O on CG&CC is more relaxed. Most Haskell submissions are functions which return the solution.
Sidenote: I like the CG&CC method, it's semi-competitive, semi-cooperative.
- all languages welcome
- almost all users post "Try it Online"/"Attempt This Online" links
- most users post explanations under their submissions
- often people will post solutions beginning with "port of user1234's excellent Foolang answer" when there's a clever shortcut someone finds
- or people will post their own solution with "here's a solution which doesn't use user1234's algorithm"
- or people will add comments to answers with minor improvements
IMO It's geared towards what is the best part about code golf: teaching people about algorithm design and language design.
My experience is still pretty good there. Back in ~2015 my family got an USB WiFi card which needed an out-of-tree module, which the manufacturer had on Github, complete with DKMS instructions. It was upstreamed after about a year, though!
The only completely unsupported device I've had is my laptop's fingerprint sensor.
I think this is a good default.
An impossible dream of mine would be to check a list of devices with haptic touchpads, and disable tap-to-click on those.
This has never stuck with me, and I hadn't thought about why until now. I have two reasons why I will always write ${x}_$y.z instead of ${x}_${y}.z:
- Syntax highlighting and shellcheck have always caught the cases I need to add braces to prevent
$x_being expanded as${x_}. - I write a lot of Zsh. In Zsh, braces are optional in way more cases.
"$#array[3]"actually prints the length of the third item inarray, rather than (Bash:) the number of positional parameters, then the string'array[3]'.
I typically use find "$HOME/docs", but with a few caveats:
- In Zsh or Fish, the quotes are unnecessary:
find $HOME/docs - If I'm using anything potentially destructive:
mv "${HOME:?}/bin" ... - Of course, if it's followed by a valid identifier character, I'll add braces:
"${basename}_$num.txt" - I'm pretty inconsistent when globbing:
"$HOME"/docs/*or"$HOME/docs/"*are common for me. - I don't use
"${HOME}"unless I actually need the braces. The reason? I write more Zsh than anything, and the braces are even less necessary in Zsh:$#array[3]actually gets the length of the third element of the array, rather than substituting the number of arguments, then the string'array[3]'
I've heard that this is what is causing SteamOS 3.5 to take so long.