bam13302

Dex would be super important for them too. Cannons of all flavors aim with dex due to being ranged weapons.

I have issue with almost all of your points.

• Dex & wisdom would be the important stats for sailors IMO (i am not saying strength and con are useless, but just not as important, they would be 3rd and 4th IMO).
• Darkvision wouldn't do a damn thing, its range would barely get off the side of the boat.
• Poison resistance is not disease resistance.
• Some spoiled food would be poison, but some would also be disease (depends on how it spoiled and the food).
• In order for short stature to be relevant to ship design, they would need a completely custom designed ship tailor made for them, which would have benifits but sounds unlikely for what pirates would be sailing. (That being said, a dwarven merchant ship designed speciifcally for their stature would be a massive pain for normal height characters to battle on)
• lower speed means they swim slower too which means going overboard is even worse.

EDIT: dwarven submarines!

• short stature actually hugely relevant as submarines are notoriously cramped
• darkvision means no need for lights in the sub, beneficial for multiple (admittedly somewhat minor) reasons.
• honestly no clue what stats would be important for a sub, no argument here
• toxic gasses less of a problem thanks to poison resistance
• Dont even need to go to the surface, a fully underwater submarine port could be connected to existing dwarven settlements near the ocean with the correct design and planning.
• Also benefits from legendary dwarven engineering.

Both are important, even if everyone is getting lots of action (feels fast), if combats end up needing to be split between multiple sessions, people are going to complain that the story isn't moving or that they have been stuck in combat forever. If people are waiting 30+ minutes for their turn, they are going to stop paying attention and do something else while waiting.

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

Found this applies nicely to my career. Routineish work? Drag my feet and fight myself to do anything. Fixing problems (bigger the better)? Everybody stand back, I got it.

Whole damn system failed due to a database failure that propagated to our secondary host too. Hacked our backup to usable in a day (meeting most requirements, including transition requirements) with a path forward for total system recovery on the main system.

Documentation on any of that though, that was a .. struggle.

Took me way too long to figure out the graph wasn't telling me the murder rate I. 2006 was ~75%

I can not state my love for this game enough, it may not be flawless, but everyone working on it is doing it for love of the game, and is doing great work.

Top comment on the lemmy world this was cross posted with points out among other things that the app isn't a system app and doesn't otherwise have permissions to access most of what is claimed here, and from a cursory glance at the app on my phone that claim looks correct. is there something I'm missing or is this post just wrong?

Comment in question: https://discuss.tchncs.de/comment/16670102

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.

Holy hell thats a huge temp range where the hell is that?!?

read the community name friend