Yeah, from what I understand, countries try to regulate the use of antibiotics, so that we don’t blow the most potent ones, a.k.a. new ones, right away. But on some level, we’re reliant on regularly discovering new antibiotics, which isn’t great.
and the superbugs that might breed aren’t viable in humans.
But diseases jump from non-humans to humans all the time?
At least, Wikipedia chooses to spell out the sentence “Most human diseases originated in non-humans” and lists a who’s who of pandemics as such: https://en.wikipedia.org/wiki/Zoonosis
Or do you mean something different?
Yeah, it’s especially funny to me, because the word “AI” has been used in gaming to describe the behavior code for NPCs since forever. And in this case, they actually even happen to refer the same thing in the end. At best, it’s a different strategy for getting to that same end result.
Yeah, the latter is certainly a big part of it. The way to make it compile-safe is to use macros to generate code, so that my users can write e.g. Package::my_frontend.version and that gives them the version of their frontend package.
Writing such macros, i.e. writing code to generate code, is certainly something I haven’t done a ton of yet, because you practically cannot justify doing that in an application codebase, only in a library, so it is new stuff that I learn.
But well, you did already call it a “nice abstraction”, which is another big part where my excitement comes from and where I think, the special nerdery is necessary.
Others might build projects which are visually tangible, like a sexy GUI, or which do something tangible, for example a colleague (who I will absolutely not deny his own special nerdery) is currently building a driver for a motor. If that driver works, you can see a motor moving in the real-world. Even non-nerds can at least tell that something is happening.
But with my project, my success is that you can write Package::my_frontend instead of Package::from_str("my_frontend")?. And that if you rename the package to super_duper_frontend, that the compiler will tell you to fix the code rather than it only breaking once you actually run the build code for the frontend.
No chance of explaining to non-coders why this is exciting or even just when you’re successful.
On Monday, one of our students at $DAYJOB asked me what projects I do in my freetime. After I infodumped on her for half an hour, she asked in disbelief “And you do these in your freetime, without being paid?”.
Like, mate, did you not listen how feckin’ excited I got just then? Of course, I do these in my freetime.
To be fair, though, the last project I told her about is very dry. It’s a library to help automate CI builds. And the thing I’m thrilled to build is a compile-safe API for accessing the packages in your workspaces. Like, yeah, it does take a special kind of nerd to get excited about that…
Pretty sure, people drawing for commissions would typically use a drawing tablet… ^^’
I mean, Rust does have a pretty inclusive community…
I’m guessing, those people are worried that it will be removed. It’s already somewhat on the line since Wayland started replacing X11, because individual desktop environments can now decide to implement it or not.
Genuinely how I feel sometimes. Like, I’ll usually just say yes, so that we can move on, but I have made the joke “How would I know?” quite a lot of times already, because it’s much closer to the truth…
I don’t think there is a way to do that. It does not seem like something they’d make configurable, if it was implemented.
It does seem like something they might want to implement, though. You can vote on it being implemented here (where someone else already submitted the idea): https://connect.mozilla.org/t5/ideas/drag-handle-on-firefox-browser-too-limited-add-ability-to-also/idi-p/104103
Side-note: In case you are on Linux, you may prefer the operating-system-wide shortcut to move any window from anywhere on its surface by holding either the Windows-key or Alt-key (varies between desktop environments) and then left-click-dragging on the window. If you do a right-click-drag instead, it resizes the window.
AI slop turned into ASCII art. That’s a new one…
Ah, I thought there would be a male bird involved still, but I guess that example just explains ovulation. Still quite optimistic that everyone shares the same understanding here, though…
Yeah, I virtually only use --force for moving tags around (which one could definitely argue isn’t really a thing you should be doing regularly either)…
Yeah, we always try to automate as much as possible with generic language build tooling and scripts, so that ideally the call in the runner is just a single command, which can also be triggered locally.
Unfortunately, if you want to be able to re-run intermediate steps, then you do need to inform the runner of what you’re doing and deal with the whole complexity of up-/downloading intermediate results.
--force-with-lease* 🙃
This post made me realize, I’ve only ever heard “the birds and the bees” referenced, but never actually how it’s applied during sex ed.
But uh, turns out this does not make any sense in that context either. It’s just two separate examples to explain sexuality, so bees pollinating flowers and birds laying eggs. They’re just used as examples, because they’re visible in nature and somewhat resemble the mechanics of sex.
My thinking was that bees are the ones that pollinate, so male.
But they certainly don’t pollinate birds, so I don’t know where that was going either. 🫠
F-Droid blog post on the topic: https://f-droid.org/en/2025/09/29/google-developer-registration-decree.html
It was posted before Google backpedalled somewhat, if I remember correctly.