Hmm, as someone with 0 years of cat experience, I interpreted that arm movement as her just stretching, because she enjoys the pets…
Hmm, as someone with 0 years of cat experience, I interpreted that arm movement as her just stretching, because she enjoys the pets…


Yeah, window cleaner or alcohol in general has the advantage that it dissipates, making it much less likely for it to get into the electronics and shortcircuit something.


It’s not yet in its enshittification phase, so right now it seems like a good deal. But before you know it, blog posts there will be blocked by all kinds of overlays and whatnot, like they are on Medium these days.
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…
Ackshually, gram is a measurement of mass, not of weight. And because a gram of ice takes up more volume than a gram of water, it is likely to float on top of the water, where it is slightly further away from the center of gravity, therefore experiencing less strong gravity. As such, a gram of ice likely weighs less than a gram of water. :P
(I spent far too long thinking how I could torpedo that silly joke of yours, because I figured there must be something with mass vs. weight there. 🫠)
My personal interpretation was the guy is just overly tan and potentially covered in mud, because he’s so tough and runs around on battlegrounds all day long.
Well, and the color palette is gray-brown in general, because we had an abundance of those, especially military shooters in the early HD era.
But yeah, who knows, could also be that the post originated from 4chan or the like and is just racist.
Earlier today, I signed up to a service and immediately got the “Become a member” badge.
Well, and I had signed up to upvote an existing post, so I also got the “Team player” badge in the same moment, for that singular upvote I had made…


AI slop turned into ASCII art. That’s a new one…


For me, it’s a matter of infrastructure for regular downloads being free. I just upload the distributable into a release on Codeberg and I’m done.
Whatever is needed to provide a torrent is just additional complexity, where I’m not sure it actually benefits anyone.
Of course, if I wanted to become more independent from my code hosting platform, torrents would be something to consider. But my projects are far too unknown to get seeded, so it would still just be a direct download with additional hoops.


I like not being particularly recognizable. Treat me like everyone else that you don’t know.
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* 🙃
I mean, that’s kinda what makes storms scary…