Except the only way to find out who shouldn't be given opoids is to give them opoids. Kinda like the cashier at the grocery store doesn't KNOW he's selling matches to an arsonist, especially one who is about to offend for the first time.
What's really despicable is that tapering an addicted patient off of opiates is legally risky for a doctor. They're supposed to cut them off cold turkey so they can be driven to a street dealer if that often ineffective "treatment" doesn't work.
There is no special virtue in luck of genetics and circumstance leaving you without an addiction problem. Count your good blessings but don't look down on others who weren't as fortunate.
Addiction is insidious. By the time someone realizes that their medically justified and prescribed pain medication might become a problem, they're already addicted. In other cases, they may know it could become a problem, but the pain is a problem right now and it just laughs at a couple aspirin.
If someone Was taking prescribed ibuprofen after an accident and developed https://en.wikipedia.org/wiki/...">Toxic epidermal necrolysis, would you be asking what moral failing on their part caused their misfortune?
Really, here in the 21st century you would think we would be past ascribing medical problems to unrepented sin.
In cases where the victim received every assurance from a certified medical professional that it would be just fine, yes.
Especially when we have law enforcement practicing medicine without a license and refusing to allow the resulting addictions to be treated as a complication to be treated medically.
In other words, I'll believe it when I see it. Remember all those people in banking who were in so much 'deep trouble' after they busted the whole world's economy? Other than a few in Iceland, they're doing just fine today, and richer than ever.
I do understand that python isn't the right choice for compute intensive work. With the exception that if it is great for doing setup for something in FORTRAN or C that does the heavy lifting.
I am certain that YOU don't understand that compute intensive work is a small fraction of what is done on computers. For example, I/O intensive work doesn't really care if it is Python or FORTRAN that is waiting for I/O to complete. There is a reason people don't drive a top fuel dragster to work.
If you meant compute intensive, you should have said so in the first place. You might have realized you hadn't if you weren't so busy flinging poop like a disgruntled troglodyte.
I was too busy patching the BIOS, kernel, and network drivers for maximum performance to connect the cables.
Looks like you didn't actually read any of the resulting links, You did however confirm the suspicion that you're stuck in a wierd Calvinist hellworld
Ford did notice, most are like you. They see the evidence and conclude the opposite because they have a pre-set notion that more work is more better. Especially when the workers are salaried and so you don't have to pay them more.
Having actually built a cluster that was in the top 500 for a while, I am well acquainted with compute intensive applications. I am also aware that compute intensive is a subset of "heavy duty" programming which is a subset of general programming.
Now, pull your head out of your ass and look around, you might learn something. And while you're at it, consider working on your social skills.
Well, since 99.99999999999% of all software run by literally everybody is an n-body simulation....
That would be an example of the "some apps" I spoke of. I note that Intel Fortran was at the top of the list (not surprising). Would ifort be your first choice if you were writing a text editor or a tar file splitter? How about an smtp daemon?
Six of one, half dozen of the other. The Python program will be smaller for the same functionality and it won't have buffer overflows and memory leaks The C program will run faster (unless it has to wait on I/O) and will check for variables used before assignment.
It really isn't. There are some apps that actually need something faster and a lot of apps that don't. It really doesn't help if a faster executable ends up waiting for I./O.
Yes, I'm sure the guys assembling the washing machines all transitioned to lucrative software development jobs!
As for service jobs, they pay less typically. So for them, the standard of living is going down, not up.
But on the bright side, we do burn a lot more polluting bunker oil shipping those washers and dryers to the U.S. and we get to be economically dependent on a sort-of communist country that is only sometimes friendly with us.
That's NOT what happened when tariffs were applied to Japanese cars. Lo and behold, they opened factories in the U.S. As a knock-on effect, Detroit auto makers had to up their game.
The part you're missing is you only have to run 15 MPH long enough to stop running when you're hopping off of an electric scooter. That's a LOT easier than trying to maintain that pace for a mile.
Weaving in and out of traffic is another matter. Then you need a helmet because the car windshield your head will soon meet will be going more than 15 MPH. In other words, don't do that, didn't your mother ever tell you not to play in traffic?
If it's the kind of scooter I'm thinking of, that's nonsense. Worst case you can hop off and stay on your feet at 15 MPH. Or do you advocate requiring a helmet for running as well?
Yes, a big deal since if they provide a helmet, it will soon disappear. If they don't, few people who might decide on impulse to rent a scooter will just happen to have their own with them.
N+1 is common. So you take the total cooling need and divide by (for example) 4, then install 5 systems of that size so you can lose one and be at full capacity. That's necessary anyway since you may need to shut one down for routine maintenance from time to time.
Ideally you don't let everything be inter-dependant so if you lose 2, you can still get by with shutting down 1/4 of the hardware.
There are many reasons you might want centrally controlled access control with cards. For example, if 1000 people have legitimate access, how long do you suppose it will be before a copy of THE key goes missing somewhere?
Slashdot Mirror
I draw my conclusions from what you have written in this thread. You see one screw and think NOTHING is a nail.
You don't write a video codec in Python, but it's a great choice for handling the UI and feeding the stream to the codec.
You have much to learn.
Except the only way to find out who shouldn't be given opoids is to give them opoids. Kinda like the cashier at the grocery store doesn't KNOW he's selling matches to an arsonist, especially one who is about to offend for the first time.
What's really despicable is that tapering an addicted patient off of opiates is legally risky for a doctor. They're supposed to cut them off cold turkey so they can be driven to a street dealer if that often ineffective "treatment" doesn't work.
There is no special virtue in luck of genetics and circumstance leaving you without an addiction problem. Count your good blessings but don't look down on others who weren't as fortunate.
Addiction is insidious. By the time someone realizes that their medically justified and prescribed pain medication might become a problem, they're already addicted. In other cases, they may know it could become a problem, but the pain is a problem right now and it just laughs at a couple aspirin.
If someone Was taking prescribed ibuprofen after an accident and developed https://en.wikipedia.org/wiki/...">Toxic epidermal necrolysis, would you be asking what moral failing on their part caused their misfortune?
Really, here in the 21st century you would think we would be past ascribing medical problems to unrepented sin.
As opposed to the safe as candy opoids.
You are exactly the sort of person who is sure all paraplegics are just lazy and could stand up if they set their minds to it.
More likely, you are the shill. Doctors are feeling increasing pressure (again) not to prescribe opiates even where they are clearly called for.
Go away popo, you're neither qualified nor licensed to make this decision.
In cases where the victim received every assurance from a certified medical professional that it would be just fine, yes.
Especially when we have law enforcement practicing medicine without a license and refusing to allow the resulting addictions to be treated as a complication to be treated medically.
In other words, I'll believe it when I see it. Remember all those people in banking who were in so much 'deep trouble' after they busted the whole world's economy? Other than a few in Iceland, they're doing just fine today, and richer than ever.
And yet, Equifax steams on.
Occam's razor suggests otherwise.
So that leaves a 'choice' of zero banks and zero credit cards.
That's how market failure works.
I do understand that python isn't the right choice for compute intensive work. With the exception that if it is great for doing setup for something in FORTRAN or C that does the heavy lifting.
I am certain that YOU don't understand that compute intensive work is a small fraction of what is done on computers. For example, I/O intensive work doesn't really care if it is Python or FORTRAN that is waiting for I/O to complete. There is a reason people don't drive a top fuel dragster to work.
If you meant compute intensive, you should have said so in the first place. You might have realized you hadn't if you weren't so busy flinging poop like a disgruntled troglodyte.
I was too busy patching the BIOS, kernel, and network drivers for maximum performance to connect the cables.
Looks like you didn't actually read any of the resulting links, You did however confirm the suspicion that you're stuck in a wierd Calvinist hellworld
Ford did notice, most are like you. They see the evidence and conclude the opposite because they have a pre-set notion that more work is more better. Especially when the workers are salaried and so you don't have to pay them more.
Having actually built a cluster that was in the top 500 for a while, I am well acquainted with compute intensive applications. I am also aware that compute intensive is a subset of "heavy duty" programming which is a subset of general programming.
Now, pull your head out of your ass and look around, you might learn something. And while you're at it, consider working on your social skills.
Well, since 99.99999999999% of all software run by literally everybody is an n-body simulation....
That would be an example of the "some apps" I spoke of. I note that Intel Fortran was at the top of the list (not surprising). Would ifort be your first choice if you were writing a text editor or a tar file splitter? How about an smtp daemon?
I sure hope not.
Six of one, half dozen of the other. The Python program will be smaller for the same functionality and it won't have buffer overflows and memory leaks The C program will run faster (unless it has to wait on I/O) and will check for variables used before assignment.
It really isn't. There are some apps that actually need something faster and a lot of apps that don't. It really doesn't help if a faster executable ends up waiting for I./O.
That must be an odd package. I have literally NEVER seen that with anything I have wanted to use, including my own pre-2.7.x software.
Yes, I'm sure the guys assembling the washing machines all transitioned to lucrative software development jobs!
As for service jobs, they pay less typically. So for them, the standard of living is going down, not up.
But on the bright side, we do burn a lot more polluting bunker oil shipping those washers and dryers to the U.S. and we get to be economically dependent on a sort-of communist country that is only sometimes friendly with us.
Tough tittie.
Then they get out, apply the lesson learned and say the same thing to you when they clean out your house. Sound good?
Who pays for their hotel stay?
The people who want them to stay there. You can always kick them out if you aren't satisfied with the arrangement.
That's NOT what happened when tariffs were applied to Japanese cars. Lo and behold, they opened factories in the U.S. As a knock-on effect, Detroit auto makers had to up their game.
The part you're missing is you only have to run 15 MPH long enough to stop running when you're hopping off of an electric scooter. That's a LOT easier than trying to maintain that pace for a mile.
Weaving in and out of traffic is another matter. Then you need a helmet because the car windshield your head will soon meet will be going more than 15 MPH. In other words, don't do that, didn't your mother ever tell you not to play in traffic?
If it's the kind of scooter I'm thinking of, that's nonsense. Worst case you can hop off and stay on your feet at 15 MPH. Or do you advocate requiring a helmet for running as well?
Yes, a big deal since if they provide a helmet, it will soon disappear. If they don't, few people who might decide on impulse to rent a scooter will just happen to have their own with them.
N+1 is common. So you take the total cooling need and divide by (for example) 4, then install 5 systems of that size so you can lose one and be at full capacity. That's necessary anyway since you may need to shut one down for routine maintenance from time to time.
Ideally you don't let everything be inter-dependant so if you lose 2, you can still get by with shutting down 1/4 of the hardware.
There are many reasons you might want centrally controlled access control with cards. For example, if 1000 people have legitimate access, how long do you suppose it will be before a copy of THE key goes missing somewhere?