No, they mean the license costs. I’m pretty sure, you only have to pay a fee for Docker Desktop…

I mean, yeah, it can make sense to duplicate information. That screenshot isn’t supposed to say that all of these should be deduplicated.
But you really gotta be cautious with duplication, because it makes everything else harder to find. And I would absolutely argue that GitHub has crossed the line where they duplicate too much, across the board. It feels like design-by-committee.

This is entirely anecdotal, but what really dumbfounded me while annotating that screenshot, is that I never actually read the links in that “About” section.
I’ve seen this page probably a thousand times already, but I had no idea that there’s an “Activity” link there, which actually seems like it could be useful. Nor a link to the README, to the CONTRIBUTING.md or for “Custom Properties” (whatever that is).
I had no idea how to report a repo until now, even though the link is apparently always on screen.

There’s just so much info there, and it’s presented like read-only info, not like navigation links, so I always just skipped over the lines that don’t have numbers in them. I also genuinely never tried clicking any of these lines before…

I could rant a lot about the GitHub UX, so here’s just the fairly obvious stuff on the repository page:

Red arrows mean duplicated information or duplicated navigational elements.
Green arrow means why the fuck do I have to tell our customers to click a random link in the middle of bumfuck nowhere, in order to download our software?

Yeah, from what I understand, hardware manufacturers need to ensure that no one uses the mobile chip to send on reserved frequencies. And the way they typically do that, is with a proprietary, undocumented driver for the mobile chip. So, you basically need to reverse engineer that for each mobile chip, to be able to make calls and such…

Flohmarkt is probably the closest. Basically federated ebay.

https://codeberg.org/flohmarkt/flohmarkt

I feel like a patent would’ve run out by now. From what I’m finding online, US patents generally only last 15-20 years. They might’ve filed it in a different country, and yesterday I read of a media codec patent lasting 25 years in Brazil.
But yeah, I believe that feature was in there before 2000 already, and they didn’t innovate on it since, which might’ve allowed for a new or renewed patent.

It might also just be a pain to implement…

?

Kate with an LSP server installed, for the language you want to code in, is also pretty decent. In case, you want less of a difference to KWrite. 🙂

You can also get a travel bidet, if you can’t permanently install one, or just want to try it out. It’s basically just a squeeze bottle with a nozzle…

Huh, used to see this regularly, but have not seen it for a few years now…

Ah, had not heard that before, but I’m willing to believe it right away.

That just sounds like a very Google thing to do, like how they tweaked the video algorithm, so that longer videos would get more visibility, not long before TikTok took off and they had to introduce a separate category for short-form videos.

I think, it comes from a general frustration, because the YouTube comment section is practically unusable for actually discussing a video.

Every so often, I watch something and want to see what people are saying about a particular section in the video. Like, maybe I was hoping for some info in the video and expect someone to have posted it in a comment instead.

But then I have to scroll through tons of comments like:

• “First!” (Followed by people telling them they’re not actually first.)
• Various comments about how they’re watching the video shortly after its publication. Or long after its publication.
• “What an inspiring video! Blah blah blah…” (with a profile picture of a half-dressed lady, because it’s actually just a bot)
• A verbatim quote of a funny sentence in the video with nothing added.
• “Just commenting for the algorithm!”

Like, I don’t want to hate on people commenting what they like, but it’s just frustrating in that situation, because you do have to read every comment, to make sure you’re not missing something. You just become acutely aware of every repeated joke and every single comment you had to read, which did not actually say something.

In ‘proper’ software development projects, you (ideally) want all information checked into the repo for what is needed to run the software:

• which dependencies you need,
• what particular versions of the dependencies,
• as well as which runtime/compiler version to use.

And then you’d use a package manager which can automatically install all these.
Python projects are currently heavily moving towards uv for this. Traditionally, you’d use pip + virtualenv + sometimes pipx for this.

Using nix develop with flakes is also valid for this, if your team agrees on it: https://nixos.wiki/wiki/Development_environment_with_nix-shell#nix_develop

Whichever way you solve it, the idea is that:

1. You can check out a commit from months ago and just run it right away. Well, or just a commit from yesterday, which is on a different Git branch, where you haven’t yet started your big dependency upgrade. As soon as upgrading a dependency requires changes in your code, you want the dependency version change tracked together with the respective code change.
2. Your different team mates can all work on the repository, even though one of them might be on Debian, the next on Arch and the third is on macOS. By defining all your dependencies in the repo, you can avoid “works on my machine” scenarios, where a bug occurs on one PC, but not on the dev’s PC where you try to reproduce it.

Could imagine that working at the scale where PeerTube is currently at, where you can actually get to know folks and it’s not just about broadcasting to as many people as possible…

I imagine, the problem comes in from there being wildly different sizes of both, dogs and chocolate.

I once heard a story, where a small dog had eaten chocolate, so the owner called the vet. And at first, the vet told them that it’s probably fine, but wanted to know how much chocolate the dog ate.

And when they then told the vet, that the dog had eaten a full-size chocolate bar, suddenly it was treated like an emergency. As in, they had to bring the dog to the vet immediately, got treated before everyone else still waiting, and the dog was given a drug to make it puke out all the chocolate.

I mean, it could most definitely be better, but I really don’t think that it’s worse on Linux. Error handling is one of the hard problems in computer science in general.

And well, at least you do get easy access to logs and error messages on Linux, which makes it infinitely better in many ways, but is also at least partially why this post exists.
On Windows or such, you’d instead put a vague description into a search engine and hope someone had the same symptoms before…

Hmm, interesting. I always write Markdown unformatted, so where I put the asterisks in myself. So, that’s a decent reality check, I guess.

If they wanted to make a specific part of the command bold, that still wouldn’t work.

Could underline the part, I guess, like this:

ls -la
   ###

(# starts a comment in shell syntax, so doesn’t get run, in case someone pastes the whole thing.)

I mean, Markdown was specifically designed to be convertable to HTML. So, it is structurally rather similar. It’s basically just a bunch of aliases for a subset of HTML tags.

Having said that, it is also designed to be plain text. You don’t have to convert it, and even when you do convert it, there’s a good chance that what you’ve written in plain text will look fine in converted Markdown as well.
For the purposes of this meme, I would certainly group it with plain text.

Nope, it is quite a literal Fallout 3 reference: https://www.pcgamer.com/heres-whats-happening-inside-fallout-3s-metro-train/