Someday, you'll learn that coming up with the answer is not as hard as coming up with the right question. And yes, I'm a technical guy. I just came to realise that very often once you define the question/problem correctly, then any competent person can solve it.
And what's your plan when you run out of screeners? Presumably, I doubt even the most qualifies ones have 100% success, so if you test enough, two things will happen; 1) Few screeners will last more than one year, meaning you will have people who are even more inexperienced 2) Who the hell wants to go through a stressful career where you get fired after a few months and have to find something else.
So you're have two choices: accept the risks, or stop flying.
Is there so much snow that they can't use a plow and shove it up on the sidewalk?
If Russia is anything like Canada, that option is only possible in suburbs where there's a sufficiently large area in front of the houses. It just doesn't work in cities. I live in Montreal. We usually get anywhere between 2 and 4 meters of snow in the winter. If you somehow managed to push all of that on the sidewalks, you would end up with 10+ m walls.
...I'll stop flying as soon as someone tries blowing up a plane with a rectal bomb or by making his underwear explode. "Please stand in line for a short rectal bomb check"
"violating the GPL" (technically it's just infringing copyright) may put you in trouble with the other copyright owners, but I don't see how it prevents you from filing a lawsuit against other people who also violate the GPL if you own part of the copyright.
I doubt any of the modern laptops can run Core 2 Duo CPUs at full throttle without it going supernova. Laptops are just plain too thin to dissipate that much heat through mere air cooling of CPU heat sinks.
I happen to have a 3-year old Core2 2 GHz Dell D820 laptop and I can run it fine at full throttle (both CPUs) without heat problems (provided I dust off the fan every few months). Now, the laptop is generally poor quality (and don't get me started on the batteries -- my 3rd one is about to die), but at least heat is not an issue.
Actually, the main problem I have with bonuses in the financial industries is not that much about "they're already making so much money", but the fact that they are an incentive to do the "wrong" thing. If you give the reward based on how much money the investments returned, then you are simply rewarding risk-taking. Not only because risky investments pay more, but because bonuses cannot be negative. Hence if you were to "bet" one billion with 50% odds, it would be profitable in terms of bonus. If you win, you make a huge bonus (and you're a hero). If you lose, you get fired and you get to bet again in your next job. I'm of course simplifying a bit, but that still describes the fundamental problem IMO.
I meant "playback/capture parameters". For example, if you want low delay audio, you need to set the period size and the number of periods, but there's no set of values that are guaranteed to work. A good API should be transparent and work the same way for any card.
10 years ago, you couldn't play two sounds at the same time unless your card could handle it in hardware. Also, that's about when (IIRC) they started introducing cards (e.g. AC97) that could only two one or two rates or (in some cases) could only do stereo. The driver would simply refuse to handle mono or 8 kHz so you had to resample by yourself. ALSA was *generally* a good idea, but with a bad implementation. It's better than OSS, but still suffers from some of the same problems, like the fact that the range of many hardware parameters is decided by the card (but at least the sampling rate was OK) and makes it near impossible to write code that works with all cards. As far as I'm concerned, *all* the sound servers on Linux (can't speak for other OSs) prior to PulseAudio were complete garbage. PulseAudio may have issues, but it's the first one to at least do its job.
If Mozilla had been installing Firefox without the users' consent and prevented the same users from uninstalling it, then yes, Microsoft would have been justified to hit the kill switch. The same way, if it was just a regular Firefox Addon that MS distributed (that the user explicitly installs and can uninstall at any time), I doubt Mozilla would have made a fuss about it.
There's no issue in particular, just the fact that it uses QString instead of std::string, QMap instead of std::map, and so on. That's annoying, but you learn to live with it.
I've once attempted to use Gtkmm for a new project. While the API is generally well designed, I found that the documentation for many features was totally inexistant. Even more annoying was the fact that some components were either buggy or not wrapped (from C Gtk) at all. Combined with the fact that components get created and deprecated at a huge rate, you don't even know what you should be using. Overall, I've had a really bad experience with Gtk (and especially gnome) development. I've only tried using Qt a little bit and so far I like it a lot. I've never done GUI with it though. I've used the "platform independent system library" part for things like threads, sockets and the like. The only thing I found a bit annoying was that it didn't integrate well with the STL.
Compensating for how healthy the people are is probably not too hard (and they probably did it). What's harder to compensate is the fact that people that are more exposed to the flu (e.g. nurses, school teachers, daycare children) are also more likely to get a flu shot. If you never get the flu, how likely are you to get the vaccine?
What I meant by "extracting" Plutonium was extracting it from the rest of the nuclear waste. Also, as far as I understand, the problem with the Plutonium bomb isn't that it's hard to build a critical mass. The problem is that there's a "contaninating" isotope that has a very high rate of spontaneous emission so you have to build the critical mass *very* quickly. If you don't, the reaction will start too early and the bomb will be destroyed with only a tiny part of the reaction completed. With the "gun" method used for the Uranium bomb, there's no way to assemble that critical mass quickly enough, so they had to do it with a very complicated use of high-explosives.
Almost anyone could make an A-bomb if they had sufficient amount of weapons grade uranium 235, or plutonium. The real challenge is extracting the uranium 235 isotope from uranium ore.
Actually, anyone can build a Uranium bomb given the Uranium and anyone can extract Plutonium. The tough part with the Plutonium bomb is not to extract the plutonium, but to make a bomb that achieves critical mass quickly enough.
I think a lot of OSS software (I'm think about gnome in particular) is so focused on "grandma can use it" that they're ending up in a state of "grandma's the only on who will want to use it". It's nice to be simple to use, but in the end if I can't do the more complicated things I want, then what's the point. Again, a gnome example. To make everything "so much simpler" I now have to use gconf-editor to configure many of the apps/tools because the option I was isn't considered "mainstream" enough. Now, talk about user-friendliness.
Using acceleration to counteract undesirable effects of microgravity appears to be a universally ignored solution. It's like people are so amazed by how awesome zero-g is that they can't accept that working against it might be the best option.
Even considered that it's not as easy as it sounds? One of the main problems (I'm sure there's more) is that unless your "vehicle" is huge, then making it spin causes both a "gravity gradient (gravity on your head will be smaller than on your feet) and strong Coriolis forces (people and objects cannot follow a straight line).
Slashdot Mirror
Police and fire officials also will not seek to recover costs associated with responding to the incident, the spokesman said.
Translation: We realize we screwed up and don't want to be laughed at in court.
Someday, you'll learn that coming up with the answer is not as hard as coming up with the right question. And yes, I'm a technical guy. I just came to realise that very often once you define the question/problem correctly, then any competent person can solve it.
And what's your plan when you run out of screeners? Presumably, I doubt even the most qualifies ones have 100% success, so if you test enough, two things will happen;
1) Few screeners will last more than one year, meaning you will have people who are even more inexperienced
2) Who the hell wants to go through a stressful career where you get fired after a few months and have to find something else.
So you're have two choices: accept the risks, or stop flying.
Exactly the same in Montreal. I was just saying that if you never removed the snow, it just wouldn't work.
Is there so much snow that they can't use a plow and shove it up on the sidewalk?
If Russia is anything like Canada, that option is only possible in suburbs where there's a sufficiently large area in front of the houses. It just doesn't work in cities. I live in Montreal. We usually get anywhere between 2 and 4 meters of snow in the winter. If you somehow managed to push all of that on the sidewalks, you would end up with 10+ m walls.
...I'll stop flying as soon as someone tries blowing up a plane with a rectal bomb or by making his underwear explode. "Please stand in line for a short rectal bomb check"
This isn't about terrorism, it's all about reducing carbon emissions by convincing people to stop flying.
"violating the GPL" (technically it's just infringing copyright) may put you in trouble with the other copyright owners, but I don't see how it prevents you from filing a lawsuit against other people who also violate the GPL if you own part of the copyright.
don't forget about your American audience
Then shouldn't that be BTUs -- or slug*feet^2/second^2 ?
I have the Intel card because I specifically wanted that (OSS drivers). But that's not really the issue here.
Sometimes I think we're alone in the universe, and sometimes I think we're not. In either case the idea is quite staggering -- Arthur C. Clarke
I doubt any of the modern laptops can run Core 2 Duo CPUs at full throttle without it going supernova. Laptops are just plain too thin to dissipate that much heat through mere air cooling of CPU heat sinks.
I happen to have a 3-year old Core2 2 GHz Dell D820 laptop and I can run it fine at full throttle (both CPUs) without heat problems (provided I dust off the fan every few months). Now, the laptop is generally poor quality (and don't get me started on the batteries -- my 3rd one is about to die), but at least heat is not an issue.
Ouch. I thought Jaunty was already pretty bad. I guess I'll give Fedora another try.
Actually, the main problem I have with bonuses in the financial industries is not that much about "they're already making so much money", but the fact that they are an incentive to do the "wrong" thing. If you give the reward based on how much money the investments returned, then you are simply rewarding risk-taking. Not only because risky investments pay more, but because bonuses cannot be negative. Hence if you were to "bet" one billion with 50% odds, it would be profitable in terms of bonus. If you win, you make a huge bonus (and you're a hero). If you lose, you get fired and you get to bet again in your next job. I'm of course simplifying a bit, but that still describes the fundamental problem IMO.
I meant "playback/capture parameters". For example, if you want low delay audio, you need to set the period size and the number of periods, but there's no set of values that are guaranteed to work. A good API should be transparent and work the same way for any card.
10 years ago, you couldn't play two sounds at the same time unless your card could handle it in hardware. Also, that's about when (IIRC) they started introducing cards (e.g. AC97) that could only two one or two rates or (in some cases) could only do stereo. The driver would simply refuse to handle mono or 8 kHz so you had to resample by yourself. ALSA was *generally* a good idea, but with a bad implementation. It's better than OSS, but still suffers from some of the same problems, like the fact that the range of many hardware parameters is decided by the card (but at least the sampling rate was OK) and makes it near impossible to write code that works with all cards. As far as I'm concerned, *all* the sound servers on Linux (can't speak for other OSs) prior to PulseAudio were complete garbage. PulseAudio may have issues, but it's the first one to at least do its job.
If Mozilla had been installing Firefox without the users' consent and prevented the same users from uninstalling it, then yes, Microsoft would have been justified to hit the kill switch. The same way, if it was just a regular Firefox Addon that MS distributed (that the user explicitly installs and can uninstall at any time), I doubt Mozilla would have made a fuss about it.
For pirates, the message is clear: there is more money to be made slinking around cinema car parks looking for laptop bags.
Now that is how you keep pirates outside of the movie theater!
There's no issue in particular, just the fact that it uses QString instead of std::string, QMap instead of std::map, and so on. That's annoying, but you learn to live with it.
I've once attempted to use Gtkmm for a new project. While the API is generally well designed, I found that the documentation for many features was totally inexistant. Even more annoying was the fact that some components were either buggy or not wrapped (from C Gtk) at all. Combined with the fact that components get created and deprecated at a huge rate, you don't even know what you should be using. Overall, I've had a really bad experience with Gtk (and especially gnome) development. I've only tried using Qt a little bit and so far I like it a lot. I've never done GUI with it though. I've used the "platform independent system library" part for things like threads, sockets and the like. The only thing I found a bit annoying was that it didn't integrate well with the STL.
Compensating for how healthy the people are is probably not too hard (and they probably did it). What's harder to compensate is the fact that people that are more exposed to the flu (e.g. nurses, school teachers, daycare children) are also more likely to get a flu shot. If you never get the flu, how likely are you to get the vaccine?
What I meant by "extracting" Plutonium was extracting it from the rest of the nuclear waste. Also, as far as I understand, the problem with the Plutonium bomb isn't that it's hard to build a critical mass. The problem is that there's a "contaninating" isotope that has a very high rate of spontaneous emission so you have to build the critical mass *very* quickly. If you don't, the reaction will start too early and the bomb will be destroyed with only a tiny part of the reaction completed. With the "gun" method used for the Uranium bomb, there's no way to assemble that critical mass quickly enough, so they had to do it with a very complicated use of high-explosives.
Almost anyone could make an A-bomb if they had sufficient amount of weapons grade uranium 235, or plutonium. The real challenge is extracting the uranium 235 isotope from uranium ore.
Actually, anyone can build a Uranium bomb given the Uranium and anyone can extract Plutonium. The tough part with the Plutonium bomb is not to extract the plutonium, but to make a bomb that achieves critical mass quickly enough.
I think a lot of OSS software (I'm think about gnome in particular) is so focused on "grandma can use it" that they're ending up in a state of "grandma's the only on who will want to use it". It's nice to be simple to use, but in the end if I can't do the more complicated things I want, then what's the point. Again, a gnome example. To make everything "so much simpler" I now have to use gconf-editor to configure many of the apps/tools because the option I was isn't considered "mainstream" enough. Now, talk about user-friendliness.
Using acceleration to counteract undesirable effects of microgravity appears to be a universally ignored solution. It's like people are so amazed by how awesome zero-g is that they can't accept that working against it might be the best option.
Even considered that it's not as easy as it sounds? One of the main problems (I'm sure there's more) is that unless your "vehicle" is huge, then making it spin causes both a "gravity gradient (gravity on your head will be smaller than on your feet) and strong Coriolis forces (people and objects cannot follow a straight line).