Here in Germany, I can pretty much only buy them shrink-wrapped, at least in the winter. They get imported from Spain, and I guess, the shrink wrap helps keep them fresh and undamaged during transport.

I imagine, this wouldn't be too different in the UK, but would be glad to be corrected.

I mean, Rust has the additional thing that a reference is a pointer + a borrow, so it's not quite as similar to a pass-by-value.

And as for the dereference operator, occasionally you can use it to turn a reference into an owned value, often by making a copy of the value (but in that case, you can usually also use .to_owned()).

A case where I don't think there's an alternative to the dereference operator, is if you've got a mutable reference and you want to replace the value that's underneath: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=04621490e1d0fd6fe1af7f2e843547fb
At the very least, if you remove the asterisk, the compiler will tell you very precisely that you need to add it back.

To me, it just means that you need to be mindful of it being a partnership. If they're good at giving emotional support, while you're good at handiwork or whatever, and you're both happy with that arrangement, then there's no point in mulling it.

It's more a word of warning, especially for the traditionally-male raised folks, who might come into a relationship and fall apart completely, because they feel for the first time, like they're allowed to share their hardships. Like, yeah, you can do that thing, if you're mindful of them being on board. You do still need to make it up to them, because it is a partnership. And you simply won't know, if they can even emotionally deal with your troubles. There is always the risk, especially in young relationships, for your partner to need to get out of there, no matter how much you'd be willing to make it up to them, because it simply drags them down far beyond any relationship could make up.

I think, your expectations are off for what a native integration would achieve. A kernel which has both a Linux API and a Windows API would be an insane maintenance effort. You'd naturally want the Windows APIs to simply be translated to the respective Linux API calls. This is what WINE does.
In theory, if it's directly integrated, you could do some dirtier stuff, i.e. call kernel-internal APIs, but you want to avoid that as much as possible, since those kernel-internal APIs are not nearly as stable as the public APIs.
It should also be said that writing kernel-level code is hard. You cannot ever crash, you cannot ever make mistakes when managing memory, you cannot allow yourself any vulnerabilities. Again, you want to avoid writing kernel-level code, if you can.

WINE has some additional ugly workarounds, like a virtualized filesystem. There's not terribly much you can do about that. Windows applications may simply expect certain folders to be in certain paths. You can't directly map that to a UNIX filesystem.

As far as I can tell, pretty much the only advantage of natively integrating it, would be that it's installed by default, which can be achieved in other ways (distros), and due to those ugly workarounds will not be popular at all. As much as I'm touting its horn right now, I do not want WINE on my system, unless I need it.

It's easy to be frustrated with WINE, because it does not handle all applications perfectly, and then think that the approach is just wrong. But yeah, no, some really smart folks came up with that approach. It's just insanely hard to get the exact (undocumented) behavior of the Windows kernel APIs correct, whether you do a mapping or implement them natively.

Yeah, I was expecting it to be a joke like:

• Introducing Longtrucks. 🚌
• Impress even more strangers of the superior person-hauling capabilities with 32 seats.
• Includes a light-up sign 🚍 so you can proudly show to strangers where you're headed.
• Access a world-wide network of pick-up bays 🚏 for you to pick up strangers from.

Hafertee

Was bin ich sehend?

Zero-setup snapshotting, GUIs for system settings, more sophisticated repo management, less custom-patching of software, more utilitarian than minimalist.

I do enjoy how he's referred to as "head chef", when "chef" itself comes originally from the Latin word for "head".

If you will, he's either Head Head Jeff or also Chef Chef Jeff.

I guess, I'm not up-to-date on the situation then...

https://turbo.fish/

It's so ridiculous, too. As far as I can tell, he was arrested, because his clothes looked superficially similar to the person who shot the CEO, but if you spend five seconds comparing the security camera images, it's pretty obvious that none of the clothing items actually match. If they hole him up based on this evidence, that's embarrassing.