Oliv in Swedish.

They said “especially”, not “only”. your question is still partly valid why he would be “more ok” with other types of governmental structures.

Avocado, young me thought it was a Kiwi so it might just have been the surprise of how different it was.

Got to tweak dos startup menu to maximise your conventional or ems memory.

I’m using pass, the Unix standard password manager. While the original application is just a. shell script, gpg and git, it seems to have evolved more into a standard structure of encrypted files that any applications can use.

On UNIX I use gopass, on my phone I use Password store together with open keychain.

Benefits: completely self hosted, well known and robust technology, easy for developers to make applications or even just read the files youself

Cons: Need to setup and maintain gpg keys. Applications I’ve used so far seem geared to more technical people. Setting up a new device requires copying gpg keys or generating new ones and add the public key to your vault. Last I checked, no viable IOS client.

Depending on your view this can be either pro or con, but you can store your 2fa and password in the same repo, all protected by your gpg keys.

It makes perfect sense actually. I did write another comment here if you are interested.

This is how operator overloads were written going back to the initial version of C++ back in 1985. The only new thing is that we can now add = default to get the compiler to generate a default implementation that compares all the member variables for you.

Maybe to a non C++ dev, but a lot of C++ is probably incomprehensible to a non C++ dev, just like there are other laguages that are incomprehensible to C++ devs. To me it makes perfect sense as it works just like all the other operator overloads.

auto - let the compiler deduce return type

operator<=> - override the spaceship operator (pretty sure it exists in python too)

(const ClassName&) - compare this class, presumably defined in Class name, with a const reference of type Class name, i.e. its own type.

const - comparison can be made for const objects

= default; - Use the default implementation, which is comparing all the member variables.

An alternate more explicit version, which is actually what people recommend:

auto operator<=>(const ClassName&, const ClassName&) = default;

if I just want to have less than comparison for example I would:

This one makes it explicit that you’re comparing two Class name objects.

if I just want to have less than comparison for example I would:

auto operator<(const ClassName&, const ClassName&) = default;

If I need to compare against another class I could define: auto operator<(const ClassName&, const OtherClass&)

You mean copy/move constructor and assignment operator?

Unless you have any special handling the ones generated by the compiler automatically should work just fine. But if you do have to define them for some reason (which is becoming increasingly rare) you would need to define both if you need both copy/move construction and copy/move assignment.

I do appreciate how newer C++ standards have made these kinds of things a lot easier too.

Define all comparison operators with just one one line using C++20

auto operator<=>(const ClassName&) const = default;

I haven’t even read your post, just copy pasted it into chatgpt o1 preview model and it said this:

Based on your detailed recollections, I believe the book you’re searching for may be one of the anthologies by Ruth Manning-Sanders, particularly those illustrated by Robin Jacques. Here’s why:

1. Ruth Manning-Sanders’ Anthologies:

“A Book of Ghosts and Goblins” (1968): This collection features a variety of eerie tales from around the world, all retold by Manning-Sanders. The stories often involve witches, ghosts, and other supernatural beings.

“A Book of Witches” (1965): This anthology includes tales specifically about witches, which might correlate with your memory of a sea-witch draped in seaweed.

“A Book of Mermaids” (1967): Given the sea theme and possible illustrations of underwater scenes, this book could also be a contender.

2. Illustrations by Robin Jacques:

Art Style: Jacques is renowned for his intricate pen-and-ink drawings with heavy linework and detailed crosshatching, which matches your description.

Depictions: His illustrations often have a gothic and eerie feel, featuring classic elements like willow trees, cliffside scenes, and supernatural creatures.

Sample Illustrations:

Diver and Sea-Witch: While I can’t access specific images, Jacques’ work frequently includes mythical and maritime elements that could involve divers and sea-witches.

Creepy Willow Trees and Gothic Cliffs: His landscapes are detailed and atmospheric, possibly aligning with the images you remember.

3. Physical Attributes:

Binding: Many editions of Manning-Sanders’ books from the 60s and 70s came with green or teal bindings, especially after losing their dust jackets.

Publication Era: The books were published in the mid to late 60s, fitting your timeframe of “old but not ancient.”

Age Appropriateness: These books were marketed as children’s literature but often contained darker themes and illustrations that could slip past less attentive parents.

4. Why This Might Be the Book:

Combination of Elements: The combination of maritime tales, witches, and eerie illustrations matches the key elements you recall.

Illustrator’s Style: The pen-and-ink crosshatching and gothic atmosphere in Jacques’ illustrations seem to align closely with your memories.

Looks interesting. I do have a Linux machine for work due to software requirements. I will have a look at void.

I went from using slackware late 90s early 00 to Mac OSX in early/mid 00. When coming back to Linux late 00 early 10s I was so disappointed in the Linux distros. I tried Ubuntu but was very disappointed in the lack of newer versions of third party software in their repo. Tried Arch for a while and while packages were up to date, every now and then the OS updates would mess something up and I had to start troubleshooting.

It might be better now, but I eventually gave up and went to FreeBSD about 10 years ago. Stable base and separate up to date third party feels like the best of both worlds. Not sure if any llinux distro offers something like that now. No snap, no flatpack, just a base os and up to third party date packages.

What you observes could be OS depended,. Vim has its own copy paste buffers (y,p etc) and the OS has its own. Traditionally highligh to copy and middle mouse button to paste on Unix. Windows has 2 methods, ctrl-c,v but those are also bindings in vim so only the older less known crtl-insert,shirt-insert works.

Copy paste is definitely built in, there is no need for extra plugins.

You mean you couldn’t copy some text from vim and paste it into another application? if yes, what did you have to install/configure for that? I’ve never had any issues copy paste from/to vim, console/GUI windows/Unix.

1 FreeBSD server with zfs mirror for storage and various server software

1 FreeBSD laptop for development

1 Linux laptop for software that doesn’t support FreeBSD

1 Linux desktop for work.

The rest of the family is 100% windows though :/

It’s not necessarily better, some things are a personal preference. Though some might be able to list some technical pros and cons.

Some things I appreciate are:

• base systems and packages are completely separate. Packages and their configuration goes in /usr/local/ No where else. (Thought they might write to /var/ )
• bsd init, not systemd. Feels more home to me as a late 90s slackware user.
• first class zfs support. Linux has caught up lately, especially now that there is a shared zfs codebase for both Linux and FreeBSD. When I switched to FreeBSD on my home server ~10 years ago that wasn’t the case.