lad

Did it help, have you managed to get rid of the sounds?

Because unstoppable 🦀

I don’t quite get what sense does ‘the flinch’ in the title have beyond being a reference to The Hitchhiker’s Guide to the Galaxy. It reads as if it was something bad, but the post is just a list of thanks

No True Scotsman, ey?

You mean things like this?

It seems flying the English flag is now as transgressive as posting you’re not a big fan of mass immigration on Facebook. And given that the latter is already likely to land you in trouble with the increasingly authoritarian state, it seems likely that the former might soon too.

I’m not exactly using Xitter, and his blog looks like a lot of reading only to find out who DHH is

Edit: oh, it seems like not much reading was needed, I’m starting to see your point after reading how good it feels to be in the Reagan’s era again:

[L]et me tell you about the 80s. They were amazing. America was firing on all cylinders, Reagan had brought the morning back, and the Soviet Union provided a clear black-and-white adversarial image. But it was the popular culture of the era that still fills me with hiraeth.

[…]

It feels like we’re finally emerging from this constant 90s Seattle drizzle to sunny 80s LA vibes in America. The constant pessimism, the cancellation militias, and the walking-on-eggshells atmosphere have given way to something far brighter, bolder, and, yes, better. An optimism, a levity, a confidence.

I think, it’s based on an old flake-compat package or something. It’s not inherently bad, but it displays what I dislike the most about Nix design, it’s very opaque and magical until you go out of your way to understand it.

The globals are another example of this, I know I can do with something; [ other ] but I am never sure if other comes from something or not. And if it’s a package parameter, the values also come seemingly out of nowhere.

Sometimes it’s also the updates, rolling back a failed update is much simpler with Nix even if it took some elaborate set-up. This might be not wildly useful but it happens more often than spinning up a new machine entirely

Personally I use flakes.

On the work we use an abomination that creates flake.lock but then parses it and uses to pin versions, it took me a while to realise this is why setting a flake input to something local never seemed to have any effect, for instance

Community publishing the configs sometimes confuses even more, because everyone does the same things differently, and some are deprecated, and some are experimental, and I was lost way more times than once while trying to make sense of it.

I like Nix, and I use it on my Mac and in our production for cross-compiling a service, but man is it a pain to fix issues. That is beside the point that for some reason Nix behaves a bit different on my machine and on co-workers’, and the only thing I wanted from it is to be absolutely reproducible

Wait, can’t this presumed weapon of mass rustification coreutils clone be also re-published under GPL?

I agree completely, I still think that for some things Nix is the most convenient thing, e.g. when packaging cross-compiled images of the apps, but I would never be able to build this from ground up, and whenever something breaks it’s a pain to fix. Using NixOS on Mac at least taught me how it works more or less, and it mostly does except for when it doesn’t and I’m in it deep

You were right, it’s an entertaining if a bit unsettling comment section

No, it’s just anything can be considered a sign that hl3 is 80% finished

Also, it may as well be, and then stay 80% finished for the rest of the century

The author claims to be an expert in Rust, so at least they don’t come from a standpoint of ‘I hate Rust and everyone who recommends it’ which seems to be somewhat popular

I almost agree, but I think that supporting old hardware practically forever would be a nice thing to have.

Luckily, it doesn’t evolve anymore and given time Rust will likely have that support if it would be necessary for its role in the kernel.

Maintainers, I guess, as in, the update that was rolled out, was broken for some users. But I don’t know if that’s the case here

This quote from Linus is what I find inspiring hope of a future wider adoption or Rust:

Thanks. I decided to try to do the merge on my own, but failed. I came close, but it was good to have your example merge to see what I got wrong.

The pin_init becoming a crate of its own, but ‘pin::Pin’ being in the core crate ended up messing with my “monkey see, monkey do” approach to Rust merges.

I’ll learn eventually, in the meantime please do continue to give me example merges and I’ll use them as training wheels.

My girlfriend is gonna be mighty upset is she thinks I’m into that kinda thing. […] please change the image to something Gnome-related and/or trustworthy.

That’s an interesting takeaway from a DDoS issue

It’s a step in between

It then takes it a step further, as they are both 0 in that regard