I play with moderate regularity and have actually never used Dwarf Therapist. (I still regularly consult the wiki though.) The turning point for me that made the game a lot more fun was realizing I could modify the config to set a population cap. If you only every allow 10-20 dwarves you never feel like you're rushing to meet everyones needs and handle new members of your fort all while keeping everyone happy. You can focus on the story and relationships unfolding while meeting every dwarfs individual needs. Suddenly the game is fun again. I also enjoy playing small forts and never breaching into the caverns below. Without the caverns performance stays high. That's mostly a limitation of my computer though.
Surprisingly I've found this isn't quite true for match vs. search in python. You would think that searching using a regex starting with a ^ anchor might avoid scanning the whole string but it will do so anyway. It makes a huge performance difference if you miss it.
This sounds like a backwards description of mmap. This is probably what they're using on the backend. I'm not sure if Windows has this as a feature, but any unixy system will.
Won't nuclear waste decay to safe levels long before the fiberglass windmill blades that last twenty years break down into something that no longer takes space in a landfill? Not to mention the significantly lower volume of waste.
I work at a company that operates much like this. I've passed up on more lucrative opportunities in the past because it's such a great place to work as a developer as a result.
I've actually been meaning to write something up about this. I've found you can get fairly good error messages from a parser combinator style parser just by saving the deepest location you successfully parsed to and the parser you failed in.
I think a component of the issue is that we've spent at least the last decade teaching kids that they should think for themselves as long as what they're thinking is something that an "expert" told them was true. This could not be farther from teaching critical thinking. Primary sources can be wrong. Primary sources can lie. Primary sources can tell the truth, but only the part that supports their argument. There was a great article to this end posted yesterday.
Somewhere in another thread someone suggested that amazon had a program and incentives for employees to represent them positively online so maybe it is just poor PR on their part. Still, these days it's hard to take anything at face value.
Absolutely amazon. I take your point, but when fighting against a much larger organization this is exactly the kind of guerilla warfare tactic you'd need to come out ahead. This kind of information campaign is exactly the sort of thing that the internet makes accessible for groups of all sizes.
The tube goes through the hole in the top of the screw and acts as a handle/lever to use when driving it into the ground. It serves a useful and well defined purpose.
Hey Rodger! The simplicity of Applejak inspired me to work on my own toy APL in the k family and I've really enjoyed it so far. Optimizing for cache coherency and linear memory layout has been the most fun I've had programming in a few years. Keep up the great work!
The mining process is _how_ transactions are verified and recorded. Bitcoin doesn't work without it. Mining is a misnomer. You aren't finding bitcoin. It's a reward for solving a problem that proves you participated in helping record transactions for the network.
Someone has already suggested mastadon, but I think Scuttlebutt is a much better solution for what you want. Totally decentralized, persistent, no need for a hosted server. You can set it up in a few minutes and if you're only using it for your small group there's no need to connect to anyone else.
If I'm selling mostly to businesses does that mean most requirements are avoided? Does that differ between desktop and web?
For context, it's, roughly speaking, a tool for making gantt charts. Not something that would really be central to a role. Just makes a task that could be done in a spreadsheet easier.
> There's a problem with this though. These fans weren't designed to be run with a filter. The filter will restrict air flow which will put a higher strain on the motor causing it to use more electricity and in worse cases could be a fire hazard. The higher the MERV rating (cleaning efficiency) of the filter the more stress it will put on the fan.
I'm fairly certain the opposite is true. In fact, most rowing machines work on this principle. The easiest setting is the one where the fan is as closed off as possible because it's pulling a vacuum. Less air, less resistance, easier to row / less power required to spin the fan. If anything, fans should draw less current with air flow on the inlet side restricted.
I've been using linux for over a decade and never even _heard_ of this or something similar happening. AFAIK the only typical way to configure these things is through the BIOS, well below the OS level. It sounds like something got borked and the computer repair shop decided it was easier to blame linux than to figure out or explain what happened.
I've spent the last decade exclusively on lower-end and more obscure linux laptops. Haven't had a single issue. I'm probably the exception that proves the rule though. I've found that most of the time it's not a linux / kernel issue, it's a udev or config issue. If you write 'mem' to the right file in /proc or /sys (I forget which) they just go to sleep. Any acpi event will wake them back up. I've done this with all sorts of custom kernel configurations on older chromebooks and cheap chinese laptops. Never had an issue. Sleeping to memory works great. Sleeping to disk or 'hybernate' is another story though. You need swap properly configured for that and it's finicky.
The meta-analysis is based on NO levels in the home, not stove use. Primarily this relates to gas heating. I'm aware of what it says. I'm not sure how what you're saying relates to my points.
It looks to me like this article is saying "Here's good research showing that NO is linked to a 40% higher rate of asthma. Stoves produce NO so they must cause a 40% higher rate of asthma." without a study connecting the two directly. And all of this based on a meta-analysis that doesn't attempt to control for a primary trigger of asthma.
It's purely a regression on latitude, temperature, and asthma prevalence by age group. I'm not suggesting that cold weather contributes to gas usage. Gas stoves / heat are more common the further north you get.
I'm going to put together two points that people have raised in this thread:
1) Asthma is strongly correlated with gas heating and stove use.
2) Gas heating and stove use is strongly correlated with latitude.
This is a case of correlation not being causation. One of the primary predictors of asthma is colder winters/latitude [2]. It doesn't look like the study controls for this in any way [1].