I can already do that on LineageOS 21 (Android 14), no rooting required.

Debugging CI pipelines is so annoying, why is there no better way than committing a bunch of dumb changes until it works?

Does USB not use interrupts?

The documentation has improved a lot recently. Especially the pocket guide is a great addition.

Alright, but seriously: IPv6.

Snake case and kebab case mixed arbitrarily.

man -k to the rescue: mbsrtowcs, strxfrm and wcstold are C functions.

A major political agenda of Vim is to support children in Uganda. A message about that is displayed whenever you open Vim’s start page. Bram Moolenaar insisted on users donating to the ICCF charity instead of to him, making Vim a very political editor in my view.

This statement is wrong.

The premise is already wrong. No orchestra can play Beethoven’s 9th symphony in 40 minutes, this piece is longer than an hour.

THE MORE YOU SAVE

Okay, who will go to court for the cereal soup question next?

I don’t think I’ve ever seen a game on Steam with “Overwhelmingly Negative” reviews before. Usually “Mixed” is already a good indicator to leave your hands off a game.

I must say I like the idea of having changes to files be bound to just the current branch, not the entire worktree (section 6.4.2), but other than that the points that are brought up don’t really seem too compelling. It certainly didn’t convince me that git has an inherently flawed design. For example, eliminating the staging area is a tempting point for simplifying git, but the authors already admit that it has some legitimate use cases.

But of course it is always nice to see some experimentation done in this space. I think the main reason why git sometimes is confusing, is because distributed version control really is a complex task, and git already does a very good job at making it tractable.

Huh? Hexagonal Architecture?

While there certainly is some overlap, Python is a scripting language and not a shell language. Some tasks that involve calling lots of different programs and juggling input and output streams are much easier done in bash than in Python.

This blog post goes into some specifics of Rust reusing Vec allocations and some of the consequences. I think it’s really worth a read to better understand Vecs. From what I understand, it is possible that Rust will reuse the allocation of vec_a in your case, but it ultimately is quite complicated.

I won’t argue with you that bash is janky and easily insecure, but what shell language do you think should replace bash?

Jon Gjengset on Youtube is doing live coding where he uses neovim quite well. And you’ll learn about Rust while you’re at it.

I (luckily) haven’t had much experience using autotools, but I do suppose it was no coincidence that the injection was initiated there. I really like the comparison that was made in the post of the Meson maintainer you linked:

Several “undefeatable” fortresses have been taken over by attackers entering via sewage pipes.