Trailblazing Braille Taser

Take a look at all the struct definition. It’s a pure virtual method of 🍴 with a bunch of overrides in the structs that inherit from 🍴.

Yeah, there really should be some expectation of stewardship in exchange for absurd post-Disney copyright durations.

The code is speaking to me, but it’s just word salad.

Am I being dense? I don’t get it.

I don’t understand any of these analogies at all

I learned MIPS as an undergrad. Pretty neat little RISC architecture.

Get out of my office

I mean technically I could write an interpreter that assigns semantics to HTML constructs.

Oh dang, sorry about that. I’ve used rclone with great results (slurping content out of Dropbox, Google Drive, etc.), but I never actually tried the Google Photos backend.

You could try using rclone’s Google Photos backend. It’s a command line tool, sort of like rsync but for cloud storage. https://rclone.org/

I have to run the .ps1 script in a new Command Prompt because the compilation takes a few minutes

I don’t follow this reasoning. Is it because you don’t want to take over the VSCode terminal with a long command? Couldn’t you can open multiple tabs, or run in the background, or use screen/tmux, etc.?

Until then, we have simdjson https://github.com/simdjson/simdjson

I don’t know, Schlitz beer is doing okay

I don’t? You can apply a similar technique to bust file hashes. Add a new comment to each source file, or whatever.

My point is that automated methods to detect unwanted content will only get GitHub so far. It will have to be fuzzy, and that means it’s an arms race between detectors and obfuscators.

It would be possible to create a dummy “salt” commit and rebase every the branch onto it. The content would effectively be the same, but each commit hash would differ.

Below you will find my highly researched list of advantages over the typical smartphone:

• Headphone jack
• Mucho storage space
• Works without internet connection
• Free software purity (I don’t know, ask RMS)
• Coolness

The third contender: the mighty embedded developer.

Why can’t we see them?

They are embedded in the wall. 🥁

At least it was better than CVS

Exhibit 1: https://programming.dev/post/5180682

Aka “vim turds”