The scenario is a cross-country trip in an electric car. What actual, specific advantage does a train or bus offer in this scenario? What problem does it solve better?
It's an electric car, so carbon emissions are low.
Most of the route will be in rural areas in the middle of the night, so the impact on traffic will be minimal.
As for the cost to build and maintain the roads, they are already needed so rural areas are accessible. Wear and tear on roads and bridges isn't much of an issue since heavy vehicles like trucks cause massively disproportionate damage[1]. (A bus might actually be worse than the equivalent number of cars in this respect.)
Apparently a common source of problems is taking two different medications without realizing they both contain acetaminophen.
Suppose your arthritis is acting up, so you start taking Tylenol 8hr Arthritis Pain[1]. That's 2 tablets every 8 hours. They're extended-release with 650mg per tablet. A total of 3900 mg in 24 hours.
A few days later you get the flu, so you decide to add what seems like a completely different medication: Theraflu Flu Relief Max Strength[2]. It has a cough suppressant and an antihistamine. But each caplet also contains 500 mg of acetaminophen. It says to take 2 caplets every 6 hours, so you take 8 of them in 24 hours[3]. That's another 4000 mg.
Between the two, you're at 7900 mg.
Then you wake up in the morning and take both medications, but 30 minutes later you've forgotten you took them. You're not thinking straight because you're sick. So you accidentally take a second dose. That additional 2300 mg brings your total to 10200 mg.
[3] You weren't supposed to take 8 of them, though. If you'd read the label very carefully, you'd have seen it also says not to exceed 6 in a 24-hour period.
My personal rule is to only purchase over-the-counter meds with a single active ingredient. I'd rather separately take an antihistamine, expectorant and painkiller than a concoction where I have to read the whole label and do math while sick to separate the doses and timings.
There are some that are very hard to find as a single ingredient. Recently I was purchasing a medication for back pain, I had a choice as to which other ingredient I wanted, but I didn't have the choice of none. I picked the combined ingredient I don't like to take, because I wouldn't be adding it on top.
I did toss on the other option, stand alone, at one point so I could get some sleep.
It left the medication I was more comfortable taking as an add-on option if things got bad enough. (This particular medication has much lower risk of overdose, so if I got stupid and took it again there would be no significant additional risk.)
It's ironic, but taking the combined medication with a known higher risk of its own was better than taking the lower risk medication.
One was controlled, higher risk, taken at specific times, while the other was taken in addition, on demand, as required.
Specifically this is one reason they’ll sell you cocodemol or Vicodin but not codeine or hydrocodone directly — if you take enough to get a codeine high, you’ll have taken a toxic amount of paracetamol/acetaminophen, so they assume you won’t.
A fission power plant simulator lets you have fun playing through a meltdown disaster scenario. A fusion power plant simulator is "worse" because it takes away the "fun" of meltdowns. The humor is in reacting to the simulator as if it were a game (some are, but this one isn't).
I probably could have worded it better but while I understand the process and the inherent safety vs fission, I am no expert in the nuclear field. I suppose what I should have asked is what are the risks of e.g retrofitting a fusion reactor into an existing Con Edison facility in the middle of Manhattn, e.g. the historic IRT Powerhouse on 59th st.
Chips only have a certain number of pins. It probably works out better economically if those pins can be used for either input or output. Chip manufacturers can thus make one product that will fit the needs of more customers instead of (say) 9 different chip variants with 8 inputs and 0 outputs, 7 inputs and 1 output, 6 inputs and 2 outputs, etc.
It could also be useful to the end user. Motherboards have a limited number of ports since the connectors cost money and take up space on the back panel. One user might want a line input (for digitizing old cassettes, for example)[1] and another user might want an extra surround sound output (for 7.1 surround sound instead of just 5.1 surround). With retasking, the motherboard can support both these niche use cases with a single shared port.
---
[1] You can't use a microphone input for this because (a) it's mono and (b) it's a different voltage level.
> Crawlers do not use the browser back button or browser history.
Couldn't you instrument the crawler's browser engine to observe whether (while crawling) the page does any behaviors that would result in back button hijacking? No back buttons have to be clicked.
You just have to watch whether the mousetrap is set. Since you know how mousetraps work, you don't have to grab the cheese.
Maybe this logic should be built into the "kill" command (or some other standard command). Given that this is the right way, it shouldn't be more tedious than the wrong way!
It could also monitor the target process and inform you immediately when it exits, saving you the trouble of using "ps" to confirm that the target is actually gone.
Different programs may take different amounts of time to cleanup and close. To know if a signal failed takes human judgment or heuristic. A program receiving a signal is even able to show a confirmation dialog for the user to save stuff, etc. before closing.
That's a valid point. Another example is SIGHUP, which will cause some programs to exit but other programs to reload their config file. In certain very specific cases, that could even cause harm.
So really what "kill" would be doing is automating a common procedure, which is different than taking responsibility for doing it correctly. It would need to be configurable.
I still think it would be a net benefit since right now incentives push people toward doing something the wrong way (even if they know better). But I can also see how it might give people a false sense of security or something along those lines.
It's not common. If `kill` on its own (which does just SIGTERM) doesn't work, you're already in "something wrong is happening" territory, which is why:
>>> Given that this is the right way, it shouldn't be more tedious than the wrong way!
is also the wrong way to think about this. Trying a sequence of signals is not so much "the right way" as it is "the best way to handle a wrong situation". The right way is just `kill` on it's own. SIGTERM should always suffice. If it doesn't to the user's satisfaction for a nonjustifiable reason, then you can just `kill -9`, but this should be rare.
Trying a sequence of SIGINT, SIGHUP, and SIGABRT is technically better than SIGKILL but not really important unless you also want to write a bug report about the program's signal handling or fix it yourself. About SIGINT and SIGHUP, if SIGTERM doesn't work, it's unlikely that SIGINT or SIGHUP would. Likely, it would only be through oversight and the execution of default handlers.
`kill -9` is just like `rm -rf`. I wouldn't suggest that `rm` automatically run with `-r` or `-f` when `rm` on its own didn't work, and I wouldn't call automatically trying those flags "the right way".
I think that's the reason why the total allowed panel power is only 800W, any more than that and you have to get it properly installed. At least that's ~ the way it is in Austria, it's also pretty easy to check whether you have ~800 or way more hanging on off your balcony.
reply