w7

I think it may be in use by tools without people being aware. I decided to check my workstation for it just in case, figuring the file would be empty, or not exist.

Instead it seems to be populated with what seem to be Heroku API and git credentials.

Kaliningrad/Königsberg is a more apt comparison then? Because that's functionally what the CCCP did.

What do we consider "forced out of their home and livelihood".

Allied bombing of Japan in WWII destroyed upwards of 3.4 million homes and rendered the areas unlivable for a period of time.

They're fairly well known in networking circles.

They're basically THE company for buying cheap, but functional, networking bits-and-bobs-- either in bulk, or as an alternative to prowling ebay for smaller purchases.

I use them all the time for transceivers, cables, DACs, etc.

What makes you say that?

Mussolini was in Milan, and stayed in Milan, when he ordered the coup march to Rome.

Mussolini lead his coup from >100-600km away from the march, why would the leader of Wagner need to be in the convoy?

What makes NAT the "main factor" for that.

I'm pretty sure every consumer router since at least 2002, if not further back, has had some stateful firewall implementation with default deny rules.

Would you need the principles of structure engineering to assess that house's toaster?

Much like a house is more than just the structure itself, so is the realm of computers.

I'm not sure I understand.

Generally in Go: functions, structs, and consts are namespaced in a way I think is familiar to most, by package origin.

If something is not, then it's either a function/struct in the same namespace (same file, or directory), variable in same scope, or it's a built-in.

Built-ins like `append`, are not much different than say `map`, `filter`, `max`, etc in Python.

Anything sourced from a subdirectory, parent directory, or sibling directory needs to be explicitly imported via the module path.

I'm not sure I'd describe the golang community's attitude as a complete write-off of frameworks. I don't think I personally know a Go developer who doesn't use some sort of web framework (I personally use Echo, for example).

Rather I think it'd be better phrased as "frameworks should use simple abstractions and methods as often as possible", which the language naturally pushes people towards imo. I believe this causes most Go frameworks to be referred to as "microframeworks".