lime

not exactly "a" building, but i live around 20 minutes from a copper mine which was in active use from around 900AD to within my lifetime. it's a museum today.

i bought this expecting a story-heavy atmospheric lonely driving experience with weird world building tense moments, like the vibe of the ship repair stuff in outer wilds.

i got a survival-crafting horror roguelike. you do comparatively little driving, the main game consists of scavenging for loot and using it to build replacement parts for your crumbling vehicle.

i hope this gets me back in. last time i thought the "repair vehicle after a successful run" setting would help me, but that also completely removes the quirks system, where the car picks up weird behaviors with time. it just deletes that gameplay element. that made me feel like i was cheating, which wasn't fun.

they are also working on a follow-up, uv. not really a fan of writing tooling in another language but it works really well.

honestly i expected the fifth panel to be full of things like "GIL", "2to3", "virtualenv" "pip vs conda vs poetry vs...", "mypy", etc

that's always been nintendo's MO though. with the exception of the N64 and GameCube, their consoles have all been very modest spec-wise. but the games they put out are made specifically for that hardware, so it's usually fine.

and actually, the switch is underclocked in its stock configuration. if you have adequate cooling for it you can basically double its clock speed with a softmod, which at least for totk removed basically all stuttering for me!

i mean it is eight years old.

no

i don't think any manufacturer publishes the voltage their devices run at, could be anywhere from 3.3 to 5V. so i don't know how an end-user is supposed to compare battery sizes between devices.

you would be a bit peeved as well if one guy in a lecture hall with 150 people constantly asked you to convert every measurement in your talk to something only that guy understands.

the spec is 10 chapters. everything is unquoted by default, so parsers must be able to guess the data type of every value, and will silently convert them if_they are, but leave them alone otherwise. there are 63 possible combinations of string type. "no" and "on" are both valid booleans. it supports sexagesimal numbers for some reason, using the colon as a separator just like for objects. other things of this nature.

i can see what it points to. you can't claim the statement is unfalsifiable just because you didn't see the issues before removal. like, this is not proof-of-god tier stuff.