I can confirm, I’ve never used a non memory managed language, and the Rust borrow checker is a massive kick in the teeth

But, the more i consider it from the perspective of memory, and pointers, the borrow checker makes a lot of sense

Especially when storing references inside structs, and how mutability affects references

I actually figured out i could fix a re-mutable borrow error by performing the two mutable operations in separate for loops

Blue cheese is intentionally inoculated with mold. Specifically penicillium mold that is perfectly safe to eat.

If a cheese “naturally” develops mold, there’s a good chance it could be harmful, so don’t eat that

The SoC on the motherboard has a special EDL mode

This is kinda like the SoC’s pre-bootloader, which loads the bootloader and can be used to flash a new bootloader

EDL mode is locked behind vendor specific certs/keys, so it’s unaccessible to the device owner

Buggies? Or just “furries”

There are a surprising number of moth and bee 'sonas, but the terms aren’t well defined

Can confirm, “scalies”

For birds it’s “avian”

Quality work will always need human craftsmanship

I’d wager that most revolutionary technologies are either those that expand human knowledge and understanding, and (to a lesser extent) those that increase replicability (like assembly lines)

I’m not sure that’s their intended design. Old pull-tab cans actually had a ring for you to pull them off (similar to “easy open” soup cans of today)

I’d imagine that as the tab shrunk and changed from pull to a lever action, the “ring” was left as a vestigial design (as a form of skeuomorphism)

That’s the only reason i don’t think this is real

This is genius

I run Arch, so docker was the easiest method of installation.

Rather than try and figure out how to install a .deb manually (and lose package manager perks)

Vscode and dotnet core (5+) work well on linux

You can also run SQL Server via docker

If you do that, you lose formatting and comments every time you load the source from disk

As much as this hurts, yeet; as an alias throw; is hilarious

The technology behind the registry is fine (which is what I think @VinesNFluff meant)

But it’s execution in Windows was ass

In theory, a configuration manager with DB-like abilities (to maintain relationships, schematic integrity, and to abstract the file storage details), isn’t a bad idea

But the registry as it is today is pure pain

Sanity checks

Always, always check if your assumptions are true

• am i even running the function?
• is this value what i think it is?
• what is responsible for loading this data, and does it work as expected?
• am i pointed at the right database?
• is my configuration set and loaded in correctly?

I’ve been running Linux for 4 years, but this still hurts to read

I mean, you just need to look at the conflicting files, fix up the code, then stage those changes and pop a new commit

There’s no “special” merge conflict resolution commit “type”

As for fixing the code itself, I usually look at what changed between both versions, and then re-author the code such that both changes make “sense”

Only eggs can sustain me

that is a little more complicated

p.communicate() will take a string (or bytes) and send it to the stdin of the process, then wait for p to finish execution

there are ways to stream input into a running process (without waiting for the process to finish), but I don’t remember how off the top of my head

from shutil import which
from subprocess import Popen, PIPE, run
from pathlib import Path

LS   = which('ls')
REV  = which('rev')

ls   = run([LS, Path.home()], stdout=PIPE)

p = Popen([REV], stdin=PIPE, stdout=PIPE)
stdout, stderr = p.communicate(ls.stdout)

print(stdout.decode('utf-8'))

nushell is pretty good. I use it for my main shell

although, i still prefer writing utilities in python over nu scripts