The distinction is meaningless in the land of Opcode's and memory addresses

For example, a struct is just an imaginary "overlay" on top of a contiguous section of memory

Say you have a struct

struct Thing {
  int a;
  int b;
  Thing* child;
}

Thing foo {}

You could easily get a reference to foo->child->b by doing pointer arithmetic

*((*((*foo) + size(int)*2)) +size(int))

(I've not used C much so I've probably got the syntax wrong)

This looks more like a solar eclipse

Linux is already at 4.5%

https://gs.statcounter.com/os-market-share/desktop/worldwide/

Use a towel

Just make sure it's not damp, or the resulting steam will burn you

You can either patch the binary

sudo patchelf --replace-needed libalpm.so.14 libalpm.so.15 "$(which paru)"

Or install paru-git

sudo pacman -S --needed base-devel
git clone https://aur.archlinux.org/paru-git.git
cd paru-git
makepkg -si

Or do both, patch the binary, then use it to install paru-git (which is what i did)

As a furry, i approve this message

Timezones make intuitive sense for humans

UTC / Unix timestamps make intuitive sense for computers

The issue is bridging the gap

Just a software dev furry passing by

This one hits scarily close to home

I even use a non-POSIX shell (https://www.nushell.sh/), with my config synced with Syncthing

Why wait?

I feel like that would cause false positives

Then again, not that many people mess with their router

How is she reading without glasses?