"More realtime?" I doesn't sound like you know what you are talking about either. All of the poster's points about DOS > standard Linux for predictable control of CPU time were correct. I can't say anything about Win3.1 because I have long forgotten about how the "multi-tasking" was implemented. The writer never claimed Win95 would be real-time.
Your comment history doesn't seem too trollish, so here goes. I'll be getting modded offtopic with the rest of the thread, but what's new.
This "thrown free" bullshit cracks me up every time.
A previous poster has already addressed the reality of landing. Now, before we even get there: what about the construction of your car makes you think that you'll be "thrown free" if broadsided by a train? Let's look at a passenger-side impact, since you'd be dead in either case if hit from the driver's side. In fact, even if hit from the passenger side, your chances are slim.
At impact, the train will continue towards you, through your car. Your car will gain velocity in the direction of the train. If you're "thrown" anywhere, you'll be thrown towards the front of the train as it plows through and accelerates your car, and that's only because you remained at rest since you weren't attached to the car.
Your new relative velocity to the car/train system means that your unrestrained torso will be thrown over the center console (assuming you're not in a truck), allowing your head to meet the passenger side of your car as it's crushed inwards by the impact. Game over.
With the seatbelt on, you remain (relatively) planted in your seat. You might injure your neck, as your head doesn't have lateral restraints, but the entire right side of the car is available to absorb the energy of the collision without your body being present. If you're in a car with side curtain airbags, so much the better. You will then slowly come to a halt as the train stops.
The "being plowed along" part is not really the variable affected by seat belt use. You will be plowed along whether you're wearing a seat belt or not; there is no way the impact of the train would "throw you free" in a side collision. If your car disintegrates and is mowed over by the train during the ensuing slowdown, you'll die either way. Seat belt use will, however, affect what happens to your body during impact.
I would challenge any advocate of the "thrown free" argument to explain a single situation in which a body could be "thrown free" from a car in a way that would result in less injury than remaining restrained in the vehicle, even ignoring the hazard from landings.
Rear-end collision? You gain relative velocity towards your seat, no problem.
Side collision? Detailed as above - you gain relative velocity towards whatever hits you, not some magical boost away from it and out the (open? do you ride everywhere with your windows open for safety?) window to "safety."
Front collision? Hey, you might indeed be "thrown free", but there's going to be unpleasant encounters first: steering wheel vs. torso, and head vs. windshield. Airbags and or seatbelts prevent or lesson the impact of both of these encounters. People smarter than you designed and throughly tested these systems.
Those rare collisions in which the car flips are the only kind that might result in you being thrown free, and even in these cases the odds of you being better off outside the vehicle are slim (as in the case below of the half-in/half-out person).
If you're riding without your airbag and seatbelt because you know the risks and accept them because your prefer to be comfortable, fine. But don't go around telling people that they're better off. If you're riding w/o a seatbelt or airbag you're much more likely to get in a garden-variety head-on collision and shatter your skull on the windshield than you are to be flipped and safely thrown free.
When I took work measurement a few years ago, the best approach to running a three-shift as understood at the time was forward-rotation schemes like:
S M T W R F S 1 1 2 2 3 3 O O O 1 1 2 2 3 3 O O 1 1 2 2 3 3 O O 1 1 2
etc.
As previous posters have pointed out, people generally have an easier time staying up longer than 24h than going to bed sooner. Keeping a certain set of workers permenantly on night duty is not a good option either - turnover is increased due to social factors, health problems due to circadian rhythms (your body can never really fully adjust to a night schedule), etc.
Also, if you make permenant shift teams, you'll tend to get lower quality output in night shifts; if there is a semi-permenant set of workers for a given shift, the decision of who goes on what team is most likely made entirely on seniority.
This scheme makes all workers share the responsibility of night work. Nobody gets permenantly stuck on a night shift, and the three-day weekend that coincides with the real world's weekend sweetens the deal for everyone a little bit while keeping work days per month down to a reasonable 21.
There are some variations on this, and I may have gotten some of the details wrong, but this is basically it.
Of course, the headaches of actually implementing something like this in your average unionized manufacturing environment may be prohibitive - this is just what they were teaching as the ideal arrangement when I was a sophomore.
1. J. Random SlashMod saw an apparently helpful comment, and moderated it informative without bothering to check the link.
2. J. Random SlashMod clicked the link, read an article mocking virus hoaxes and those who fall for them, thought it funny, but chose to mod it informative in a random anonymous display of irony (which would probably be negatively metamoderated by anyone paying attention).
3. The moderator was trolling.
If it's 3, well then IHL, IHBT, FOAD.
If you think 2 is more likely than 1, then you should probably take a moment to consider why Slashdot moderators are exempt from your painfully trendy views on the intelligence of Americans.
Hey, perhaps the real explanation isn't "Slashcode suxx0rz ghey more like MashCode ROFL@#." Perhaps it's that while you slowly read all the page one comments at -1 nested while eating your "Hungry Man" dinner with your left hand, some of the other readers of this fine site post replies to page one comments, thus pushing comments that were page 1 half an hour ago onto page 2, forcing you furiously mash the page down key for untold seconds.
This doesn't sound so much like a webserver problem as a website implemented with absolutely no thought whatsoever given to security. Also, a freakin' idiot AC problem.
Some info on the widespread abuse and resulting public anti-nuclear sentiment in Japan.
Some more info on the Tokaimura incedent. There's an interesting bit about 2/3rds of the way down about how they needed to replace a core shroud (this is INSIDE the reactor) at one of the flagship plants. They just hired about 1,000 unskilled laborers, and each one worked inside the reactor for their legally allowable annual dose of 3 minutes. Note: I'm not a socialist - this was just one of the more informative Google hits.
Unfortunately the recoil would generate enough torque to be interpreted by the Segway as a strong lean backwards. Unless, of course, he only fires his shotgun along the Y axis of the segway.
Re:Not inteded to be a callus question
on
Surviving Tornadoes
·
· Score: -1, Flamebait
Slashdot Mirror
Let me second your cry for help here. The documentation is pathetic.
"More realtime?" I doesn't sound like you know what you are talking about either. All of the poster's points about DOS > standard Linux for predictable control of CPU time were correct. I can't say anything about Win3.1 because I have long forgotten about how the "multi-tasking" was implemented. The writer never claimed Win95 would be real-time.
Damn, am I showing my age here?
Unfortunately, no. Fortran 90 is still used in many Intro to CS for Non-Majors courses today.
Eight posts and still no obligatory Penny Arcade link. *sigh*
I believe ObviousGuy is to blame for the tangent. Also, your sig has some insight on your question.
Your comment history doesn't seem too trollish, so here goes. I'll be getting modded offtopic with the rest of the thread, but what's new.
This "thrown free" bullshit cracks me up every time.
A previous poster has already addressed the reality of landing. Now, before we even get there: what about the construction of your car makes you think that you'll be "thrown free" if broadsided by a train? Let's look at a passenger-side impact, since you'd be dead in either case if hit from the driver's side. In fact, even if hit from the passenger side, your chances are slim.
At impact, the train will continue towards you, through your car. Your car will gain velocity in the direction of the train. If you're "thrown" anywhere, you'll be thrown towards the front of the train as it plows through and accelerates your car, and that's only because you remained at rest since you weren't attached to the car.
Your new relative velocity to the car/train system means that your unrestrained torso will be thrown over the center console (assuming you're not in a truck), allowing your head to meet the passenger side of your car as it's crushed inwards by the impact. Game over.
With the seatbelt on, you remain (relatively) planted in your seat. You might injure your neck, as your head doesn't have lateral restraints, but the entire right side of the car is available to absorb the energy of the collision without your body being present. If you're in a car with side curtain airbags, so much the better. You will then slowly come to a halt as the train stops.
The "being plowed along" part is not really the variable affected by seat belt use. You will be plowed along whether you're wearing a seat belt or not; there is no way the impact of the train would "throw you free" in a side collision. If your car disintegrates and is mowed over by the train during the ensuing slowdown, you'll die either way. Seat belt use will, however, affect what happens to your body during impact.
I would challenge any advocate of the "thrown free" argument to explain a single situation in which a body could be "thrown free" from a car in a way that would result in less injury than remaining restrained in the vehicle, even ignoring the hazard from landings.
Rear-end collision? You gain relative velocity towards your seat, no problem.
Side collision? Detailed as above - you gain relative velocity towards whatever hits you, not some magical boost away from it and out the (open? do you ride everywhere with your windows open for safety?) window to "safety."
Front collision? Hey, you might indeed be "thrown free", but there's going to be unpleasant encounters first: steering wheel vs. torso, and head vs. windshield. Airbags and or seatbelts prevent or lesson the impact of both of these encounters. People smarter than you designed and throughly tested these systems.
Those rare collisions in which the car flips are the only kind that might result in you being thrown free, and even in these cases the odds of you being better off outside the vehicle are slim (as in the case below of the half-in/half-out person).
If you're riding without your airbag and seatbelt because you know the risks and accept them because your prefer to be comfortable, fine. But don't go around telling people that they're better off. If you're riding w/o a seatbelt or airbag you're much more likely to get in a garden-variety head-on collision and shatter your skull on the windshield than you are to be flipped and safely thrown free.
I should also note that this is not a new concept.
When I took work measurement a few years ago, the best approach to running a three-shift as understood at the time was forward-rotation schemes like:
S M T W R F S
1 1 2 2 3 3 O
O O 1 1 2 2 3
3 O O 1 1 2 2
3 3 O O 1 1 2
etc.
As previous posters have pointed out, people generally have an easier time staying up longer than 24h than going to bed sooner. Keeping a certain set of workers permenantly on night duty is not a good option either - turnover is increased due to social factors, health problems due to circadian rhythms (your body can never really fully adjust to a night schedule), etc.
Also, if you make permenant shift teams, you'll tend to get lower quality output in night shifts; if there is a semi-permenant set of workers for a given shift, the decision of who goes on what team is most likely made entirely on seniority.
This scheme makes all workers share the responsibility of night work. Nobody gets permenantly stuck on a night shift, and the three-day weekend that coincides with the real world's weekend sweetens the deal for everyone a little bit while keeping work days per month down to a reasonable 21.
There are some variations on this, and I may have gotten some of the details wrong, but this is basically it.
Of course, the headaches of actually implementing something like this in your average unionized manufacturing environment may be prohibitive - this is just what they were teaching as the ideal arrangement when I was a sophomore.
No, they just wrap around. The parent is correct - research shows this is the correct way to manage shift work.
Nice troll.
I see three explanations for this.
1. J. Random SlashMod saw an apparently helpful comment, and moderated it informative without bothering to check the link.
2. J. Random SlashMod clicked the link, read an article mocking virus hoaxes and those who fall for them, thought it funny, but chose to mod it informative in a random anonymous display of irony (which would probably be negatively metamoderated by anyone paying attention).
3. The moderator was trolling.
If it's 3, well then IHL, IHBT, FOAD.
If you think 2 is more likely than 1, then you should probably take a moment to consider why Slashdot moderators are exempt from your painfully trendy views on the intelligence of Americans.
Or perhaps I'm just feeding a troll right now.
And again...
MODERATORS! Are you in such a hurry to get rid of your points that you can't MOUSE OVER THE LINKS?
THIS CRAP IS NOT INFORMATIVE! Funny would be a stretch!
Yes, I am shouting! I've HAD it with you idiots!
MODERATORS! Are you in such a hurry to get rid of your points that you can't MOUSE OVER THE LINKS?
THIS CRAP IS NOT INFORMATIVE!
Yes, I am shouting! I've HAD it with you idiots!
This is offtopic? I wonder about the kickbacks the janitors must be getting from bn.com.
Hey, perhaps the real explanation isn't "Slashcode suxx0rz ghey more like MashCode ROFL@#." Perhaps it's that while you slowly read all the page one comments at -1 nested while eating your "Hungry Man" dinner with your left hand, some of the other readers of this fine site post replies to page one comments, thus pushing comments that were page 1 half an hour ago onto page 2, forcing you furiously mash the page down key for untold seconds.
Welcome to Slashdot. It's kind of funny watching witty posts that unintentionally end up functioning as trolls.
I predict USB 10-key pads with non-shift colon keys available at ThinkGeek within a year.
Ermm, do you type 32 digits to enter your IP's now? Bits != digits. You type 12 at the most right now. You'll be typing 48 digits at the most in IPv6.
Or does it take the high road and use hexidecimal? That'd just be 32 characters not counting delimiters.
Please forgive my IPv6 ignorance.
This doesn't sound so much like a webserver problem as a website implemented with absolutely no thought whatsoever given to security. Also, a freakin' idiot AC problem.
Yes. Has everyone forgotten 1999?
Some info on the widespread abuse and resulting public anti-nuclear sentiment in Japan.
Some more info on the Tokaimura incedent. There's an interesting bit about 2/3rds of the way down about how they needed to replace a core shroud (this is INSIDE the reactor) at one of the flagship plants. They just hired about 1,000 unskilled laborers, and each one worked inside the reactor for their legally allowable annual dose of 3 minutes. Note: I'm not a socialist - this was just one of the more informative Google hits.
Your sig kicks ass.
Unfortunately the recoil would generate enough torque to be interpreted by the Segway as a strong lean backwards. Unless, of course, he only fires his shotgun along the Y axis of the segway.
Nice troll.
It would be nice if we could count on things to work that way.
It's the only shareware I've ever registered. Fast, stable, great functionality, nice "Save To FTP" feature.
I use it for all my development (Java, C, C++, occasional F90 for the number crunching stuff).