Collective bargaining, currently being one of the few bargaining tools useful in a wide range of environments, needs to be available.
It's like outlawing the ability of government workers to strike. If you do, they're now working on their employer's terms. And their employer may not have their best interest at heart. Or even balanced interests.
I'd love to see an effective alternative, though. In my negligible experience, unions tend to get greedy. I understand a school's staff not wanting to take half their pay out for insurance, but I don't understand seniority-over-value rules that end up in place in unionized factories.
As another poster pointed out, it depends on the composition of the asteroid. If it's methane ice, there may not be any fireworks at all.
And of course there are pressure differences in solid masses. Construction engineers have to deal with it all the time.
As an example, take my monitor stand at home. It's a cradle lattice of wooden 1x2s that I threw together since the original monitor stand broke. If I set the monitor's weight on a pair of 1x2s laying their two-inch surface, they'll break. However, if I set them on their one-inch surface (making them two inches tall), they'll hold up just fine.
The original arrangement would break because there's too much negative pressure in the lower portion of the 1x2, causing it to tear apart. However, the top of the 1x2 stays intact (except as the tear rises, but I'll get to that.) because there's only compressive forces at work.
(As the tear rises, the portion of the 1x2 experiencing the negative pressure changes to wherever the top of the split is, causing more wood to split.)
Here's a couple of concepts to wrap your brain around that aren't specific to C: global data, locking and blocking.
If you have global data, you really don't want one thread to change that data while another is reading it. Imagine someone talking to you, and they change sentences halfway through.
The solution to this is something called locking. You set a variable that says "Hey, this data is in use", so that other sections of code won't touch it while you are. When you're done, you unset that variable, which lets other programs know that they can use it.
As a result, you have somthing called blocking. A thread may not be able to continue to operate until it has access to the data, so it waits for that data to become available.
Other things to learn about that involve SMP are: read-copy-update (rcu), race conditions. Learn about the importance and repercussions of them, and you'll be know a bit more about kernel behavior.
Disclaimer: I haven't done any kernel work; I've only read a lot about development in the Linux kernel. I can only assume that kernel issues are similar in other kernels.
The balloon is already at a higher altitude than the jet stream, but that's not much of a problem if you don't mind dropping down first. (Though you'd have a hard time convincing a layman of the need for the "obvious" inefficiency of going to 70,000 feet, then dropping down to the altitude of the jet stream.
Unfotunately, the jet stream moves along at far less than Mach 1. Even at the surface of the ocean, Mach 1 is only about 700mph, which is only a fraction of the speed you need to achieve orbit. In addition, the higher you go, the slower sound travels, so the lower your mach speed is, anyway.
Even if you had all of that, I bet the amount of gas generated by the explosion of a SAM would rip apart your partitions.
A worse scenario? The missile actually being inside the baloon before it blew up. (Meaning, it didn't hit a sufficiently rigid portion until it was already inside.)
You'd need to expend more energy to stay where you want to be. However, solar panels powering electric fans make it a relatively simple problem. And bouyancy would already do the heavy lifting for you.
SAMS developed by the former Soviet Union have been able to do that for years. And if a SAM is able to hit a highly maneuverable target moving at Mach 1, I don't think it's going to have a hard time hitting a target that's standing still.
Ah, but what if you could run GNOME instead of Explorer as your window manager/desktop environment on a 'Doze box? It would make for a great development platform.
Granted, someone should have tried that with Java a long time ago, just as a proof of concept.
Well, thinking about the nature of the X-Prize (straight up, then straight down), a bouyant launch platform sounds to me like an excellent idea.
Geosynchronisity without requiring a high orbit.
Of course, there are technical issues to work out regarding flame safetey, what to do if you lose pressure in your balloon, etc. But it's definately worth a look.
Never heard of a superoxide. Perhaps you meant "peroxide", which is an O2(-1) ion?
Granted, H2O2 (hydrogen peroxide) is a carcinogen that until the last twenty years or so was recommended as a valuable disinfectant. Heck, my grandmother put it on my skinned knee in the mid eighties.
Play around with cubanes. But be very careful. octanitrocubane is considered the most powerful non-nuclear explosive yet sythesized. And it's shock-insensitive.
Slashdot Mirror
We need a better employee-employer negotiating mechanism to eliminate the necessity of strikes.
A collective lawsuit might work; let the two sides argue the facts in front of a judge or a jury.
Collective bargaining, currently being one of the few bargaining tools useful in a wide range of environments, needs to be available.
It's like outlawing the ability of government workers to strike. If you do, they're now working on their employer's terms. And their employer may not have their best interest at heart. Or even balanced interests.
I'd love to see an effective alternative, though. In my negligible experience, unions tend to get greedy. I understand a school's staff not wanting to take half their pay out for insurance, but I don't understand seniority-over-value rules that end up in place in unionized factories.
Read Lucifer's Hammer ... It's an excellent book by Jerry Pournell that covers that scenario.
Wow, that's silly.
As another poster pointed out, it depends on the composition of the asteroid. If it's methane ice, there may not be any fireworks at all.
And of course there are pressure differences in solid masses. Construction engineers have to deal with it all the time.
As an example, take my monitor stand at home. It's a cradle lattice of wooden 1x2s that I threw together since the original monitor stand broke. If I set the monitor's weight on a pair of 1x2s laying their two-inch surface, they'll break. However, if I set them on their one-inch surface (making them two inches tall), they'll hold up just fine.
The original arrangement would break because there's too much negative pressure in the lower portion of the 1x2, causing it to tear apart. However, the top of the 1x2 stays intact (except as the tear rises, but I'll get to that.) because there's only compressive forces at work.
(As the tear rises, the portion of the 1x2 experiencing the negative pressure changes to wherever the top of the split is, causing more wood to split.)
So where can I reach you if you're wrong?
Until you get more than 255 possible errors! Duh!
Er...wait. I guess that would be a bad thing, wouldn't it?
Here's a couple of concepts to wrap your brain around that aren't specific to C: global data, locking and blocking.
If you have global data, you really don't want one thread to change that data while another is reading it. Imagine someone talking to you, and they change sentences halfway through.
The solution to this is something called locking. You set a variable that says "Hey, this data is in use", so that other sections of code won't touch it while you are. When you're done, you unset that variable, which lets other programs know that they can use it.
As a result, you have somthing called blocking. A thread may not be able to continue to operate until it has access to the data, so it waits for that data to become available.
Other things to learn about that involve SMP are: read-copy-update (rcu), race conditions. Learn about the importance and repercussions of them, and you'll be know a bit more about kernel behavior.
Disclaimer: I haven't done any kernel work; I've only read a lot about development in the Linux kernel. I can only assume that kernel issues are similar in other kernels.
The balloon is already at a higher altitude than the jet stream, but that's not much of a problem if you don't mind dropping down first. (Though you'd have a hard time convincing a layman of the need for the "obvious" inefficiency of going to 70,000 feet, then dropping down to the altitude of the jet stream.
Unfotunately, the jet stream moves along at far less than Mach 1. Even at the surface of the ocean, Mach 1 is only about 700mph, which is only a fraction of the speed you need to achieve orbit. In addition, the higher you go, the slower sound travels, so the lower your mach speed is, anyway.
I'd be more worried about those poor little packets. I doubt the blimp would have a crew.
Talk about a blimp that wouldn't die.
Even if you had all of that, I bet the amount of gas generated by the explosion of a SAM would rip apart your partitions.
A worse scenario? The missile actually being inside the baloon before it blew up. (Meaning, it didn't hit a sufficiently rigid portion until it was already inside.)
Forget Skynet. Say hello to Jane.
You'd need to expend more energy to stay where you want to be. However, solar panels powering electric fans make it a relatively simple problem. And bouyancy would already do the heavy lifting for you.
Nations? Maybe. But shoulder-launched SAMS have been on the market for years. (Illegal or not.)
SAMS developed by the former Soviet Union have been able to do that for years. And if a SAM is able to hit a highly maneuverable target moving at Mach 1, I don't think it's going to have a hard time hitting a target that's standing still.
Not only that, you won't have shrapnel occupying the former "orbit" of a blimp.
Ah, but what if you could run GNOME instead of Explorer as your window manager/desktop environment on a 'Doze box? It would make for a great development platform.
Granted, someone should have tried that with Java a long time ago, just as a proof of concept.
Well, thinking about the nature of the X-Prize (straight up, then straight down), a bouyant launch platform sounds to me like an excellent idea.
Geosynchronisity without requiring a high orbit.
Of course, there are technical issues to work out regarding flame safetey, what to do if you lose pressure in your balloon, etc. But it's definately worth a look.
A friend of mine created his own tld for use in his network. He has "yamaguchi.cstt" "giles.cstt" etc.
I guess I better strip Perl out of my Debian machine, then. Er...that'd kill it.
Seriously, code inside VMs has advantages, such as security and portability.
That's because you were using busybox, a lightweight utility that builds in some of the functionality of some of the most commonly used tools.
That way you can get the install process started from only two floppies. (Assuming the rest is a network install.)
I bet he filters out any email that wasn't posted via Exchange Server.
Never heard of a superoxide. Perhaps you meant "peroxide", which is an O2(-1) ion?
Granted, H2O2 (hydrogen peroxide) is a carcinogen that until the last twenty years or so was recommended as a valuable disinfectant. Heck, my grandmother put it on my skinned knee in the mid eighties.
Why shouldn't a company's OSS contributions be self-serving? Isn't that possibility one of the biggest hopes for such software?
People who use the Itanic (not necessarily HP customers) still find HP's contributions useful.
Play around with cubanes. But be very careful. octanitrocubane is considered the most powerful non-nuclear explosive yet sythesized. And it's shock-insensitive.
Here are some links.
I was at a hotel room. I didn't see the title scene, so I didn't know what show it was.