Cuz the sewer pipes are known for being hermetically sealed.

I imagine just checking if your windows are closed, sealing any cracks as best you can with wet towels, and staying inside would be far more effective

One thing that will be the biggest general qol for your new build is likely to get a M.2 NVMe for your games and OS

Civ 6 is pretty flexible and dwarf fortress will run on a potato, basically anything remotely in the gaming market will play them fine. Civ 7 is more intense, but being turn based cpu tends not to be the bottleneck

Do you have any preferences (distro, cpu/gpu manufacturer, etc) and a budget? Most of the games on your list I am familiar with and will run on damn near anything remotely modern.

Lacing direction, with the fairly low requirements (from what i recognize), and assuming you are price conscious id suggest you poke around the used gaming PC market (either gamer friends, or failing that online), which will also completely bypass the tariff issue too.

PopOS is pretty solid for linux gaming and has a distribution specifically for Nvidia too which handles most of the headache with Nvidia if you go that route.

EDIT: Poked around the requirement pages of the ones i wasn’t familiar with, i didn’t see a single game that had a requirement of anything newer than 10 year old hardware, depending on your friend network, you could get a computer that could play those games well for a song. Civ 7, your ‘evenutally’ game, is the only thing listed that has strongish requirements, and would be what i would pay attention to if you are aiming higher.

Whats your use case?

Was somewhat recently considering a linux laptop myself and ended up deciding the steamdeck fit my needs well.

A dock + portable keyboard & mouse for when i need to do typing or w/e, and a fun handheld console for when i want fun.

That being said, depending on what your “older” laptop is, it might not actually be much stronger, or it might be wildly overpowered for what you need.

So they both store data in a table like structure, but that’s about where the similarities end. Excel is useful for handling smaller more flexible data sets, but has performance, scalibility, storage, and structural deficiencies compared to SQL, it’s also harder for computer languages to communicate with a shared excel dataset and modify it vs SQL.

One of the major issues with excel as a database is data limits, excel only allows for ~1 million rows. Considering there are ~1 billion possible SSNs, excel would not be a great medium for them for that reason alone.

One big advantage of SQL is you need to structure your data on the creation of the table and it’s designed with the expectation that all data will fit a structure, including unique keys, format, and other limits and structures. This allows you to enforce database rules easily and massively reduce storage size and query times.

There are a bunch of other reasons for using SQL but most of it boils down to either it’s faster, easier for multiple computers to access and read/modify simultaneously, or better for enforcing rules and structures when modifying it.

Most body armor is good for 1 strike. Kevlar thread break, ceramic breaks, and you really don’t want to use dented armor, best case it’s a weak point, worst case is pushing in your chest cavity preventing you from breathing. Any body armor that is remotely mobile is effectively one time use. Now admitted (normally) used body armor can still provide some protection and can be better than nothing (except in situations where the damage impacts you, ie the plate metal being dented and pushing into your chest). And some can be repaired or replaced with the right materials and tools, but those are heavy, and take space

To be fair, I didn’t really focus on the biggest annoyance I’ve had with spaces in the file name: going between terminals and the GUI, most filenames you can copy and paste with wild abandon, but filenames with spaces always require special care, sometimes stripping the auto completed escaped space from file names from the terminal, or quoting or escaping the space when taking one from the GUI.

You are correct, that is how I worked around the issue and why I mentioned that work around in my original post

for f in *.txt; do cat $f; done

Will error for example. It works fine for filenames without space, but if the filename has space in it, it will be interpreted wrong. But if your testing batch doesn’t have spaces in the filename, you won’t see the issue until it’s used on a file that does. Note ‘cat’ is a placeholder, any function/script that can be used on a file here will have the same issue.

Something similar to that caught me last week while I was unzipping multiple mods in bulk for a game.

The problem is really that space is an argument separator, so to safely handle filenames with spaces you need to handle them special, either by escaping them, quoting the entire thing. This means that the filename with spaces can’t be just copy pasted wherever you want, you have handle them special. It adds complications that are resolved by just using a separator that isnt used for other things, like underscore, or dash. Dot I also don’t like as much as it’s used as a separator for extensions, but that’s a far easier problem to handle by just ignoring all but the last dot, leaving only one really bad edge case (a file that does not have an extension, that uses dot separator in its filename having the filesystem imply a wrong extension.