I dunno, I've worked on some pretty big projects that have used lots of coroutines, and it's pretty easy to avoid all of the footguns.

I'm not advocating for the ubiquitous use of coroutines (there's a time and place), but they're like anything else: if you don't know what you're doing, you'll misuse them and cause problems. If you RTFM and understand how they work, you won't have any issues.

They're a crutch for people who don't know what they're doing, so of course they invite a whole host of problems that are harder to solve than doing it right in the first place.

If you strictly require people to know exactly what they're doing and always RTFM and perfectly understand how everything works, then they already know well enough to avoid coroutines and SendMessage and UnityEvents and other footguns in the first place.

It's much easier and more efficient to avoid all of the footguns when you simply don't use any of the footguns.

I'm curious about Hashibashi as well. I've seen lots of Japanese people doing it, and now I'm worried I look like a total poser from copying them.

I think many people know how to google "what is my IP" and send that to a friend, but don't necessarily know what a port is.

NAT randomization, I don't know. Depends on your setup, I guess.

Or lots of parents will put their ID into their kid's computer so that they have full access.

What ID? Most of these laws don't require any ID.

They require that when the administrator of the computer sets up an account for a user the admin can enter an age or birthdate for the user, and that the OS provides an interface so that apps that user runs can ask based on that admin provided information what age bracket the user is in ([0,13), [13,16), [16,18), [18,∞)).

Apps that need to make age based decisions can use that information.

Once a mechanism is in place, they can easily "refine" it.

It's not so much a workaround as it is an elegance in design. In Zig, when you @import a file, that file is converted to a struct with comptime fields for all of the public members. Similarly, a "namespace" in Zig is just a nested struct with more fields. Usually it's just another import of something else.

N.B.: Coffee hasn't reached my bloodstream yet; accuracy not guaranteed.

files aren't converted to structs on import, they _are_ structs (well, their contents are the inside of a struct declaration). also, public members don't become comptime fields? file structs are basically left as-is on import, nearly like you copy&pasted the file contents into a struct declaration

I like JR's "shaggy fur" interpretation, but my initial thought for the mammoth was that it might be butcher markings? (as someone who is not a butcher and knows less than they should about anatomy)

I feel like days are a non-issue; they would just start at different times (UTC) in different territories. This wouldn't make things any more complicated than they already are (currently, if I want to talk to someone in Australia, I have to look up what time it is in Australia and infer the day of the week from that, if necessary. If everything is under UTC, I know what "time" it is, but I still have to look up what day it is).

Most of the issues time zones cause are not "day of the week" related anyways (at least in my experience), so I think having to figure out what day of the week it is somewhere else wouldn't be a common problem anyways.

I've just accepted that Microsoft, Google, and Meta all have a constant wiretap in my office (on account of my Windows PC, Android smartphone, and Meta VR headset).

It's rather dystopian to just know and accept this, but there's really no alternative if you want to participate in modern society at a normal capacity (sans the VR headset, that really isn't a necessity).

Something something, keep your enemies closer, right?

fr fr, OP be cappin 2000 ain't English