Other than... precedent, history, and the 24 states with laws punishing faithless voters, and the myriad of states with laws making it very difficult to be a faithless elector...
Well, it wasn't added to the rules until 1906, and traditionally, we didn't have a national language, because the framers didn't see a need, and the colonies at the time housed people from many European descents (especially since colonies such as New York weren't originally British, many portions of the newly formed country were very recently French, lost during the French-Indian War, and disputed with Spain, like western Georgia). Later on, it became increasingly relevant as the US "acquired" territories with predominantly non-English speakers (everything west of the Mississippi) through either Conquest (Mexico, Hawaii) or purchase/treaty (France - The entire midwest and Louisiana, Spain - Florida).
Teddy Roosevelt was the first major person I know of to champion the English-only movement, in the early 20th century, and several states outright rejected it, having de jure multi-lingual government document requirements, and Louisiana having 2 de jure official languages (English, French).
I don't really see what the benefit of enforcing a national language is. I don't see a multi-lingual government as a shortcoming, I guess; and a majority of the continental US is in fact land that was acquired while populated with Spanish and French speakers. I say let the language demographics evolve naturally.
or pay 200% overtime and deal with law mandated recovery time?
Wait... what? Do we live in the same US?
A salaried programmer making more than $455 a week (see: all of them) in the US is exempt from FLSA overtime pay requirements (yay!)
You think German is more intelligible to an English speaker than ebonics?
Anti-social? I suspect it isn't that at all to those who speak it with each other.
Anti-assimilationist? Ahhh, and your true colors show. Perhaps it's you who is failing to assimilate with the movement of demographics and culture.
It's not at all uncommon for those who are standing still to look at the vast majority of mankind passing them by and think that it is they who are failing to assimilate. You must be some kind of genius.
ELF binaries in linux have what is called an interpreter in the header. It's a binary that the kernel actually loads to setup the ELF in memory before execution. That binary is responsible for the start-time aspect of run-time linking (setup the delayed-load tables, GOT, PLT, etc.)
For 32-bit binaries, the 32-bit loader is specified as the interpreter (at compile time), for 64-bit binaries, the 64-bit loader is.
The loaders maintain caches of what libraries of what architecture are where, this cache is loaded every time the loader is fired off by the kernel to setup an ELF program for execution. There is no trying to load different loaders or libraries from different architectures. It just doesn't work that way.
Context switches between long-mode and protected-mode code are not any more expensive (practically speaking) than homogenous context switches. This has all been profiled. If SGI offered the ability to not support 32-bit userspace code at the kernel level (certainly doesn't matter at the kernel level- it's not like people are allowed to jump into the kernel.) it was likely because of an architectural nightmare like their 64-bit kernel running on the Itanic.
In a way, it does make it easy to get your game running on multiple platforms. The base dependencies for Steam are also basic middleware installed on virtually every Linux machine, and Steam ensures that it is there. SDL/OpenGL are easier to use than DirectX (IMO, I concede), and making sure that Steam enforces the dependencies across multiple flavors of platforms does in fact overcome the most difficult aspect of Linux development- dealing with the nightmare of different ways or slight variations in the details for pulling in dependencies on different platforms.
Need the 32-bit version of of the Pulseaudio libraries, but you refuse to install that stuff on your machine? Don't worry, Steam has you covered.
Steam is, in essence, a portion of the middleware, a compatibility layer, to a point.
It's certainly dick-headed... But profoundly and willfully ignorant? I don't know. The Minecraft engine is pure shit. I work with the base classes frequently while work with mods. It really does take an i7 with a decent GPU and a couple gigs of ram to really run it worth a shit with any kind of mods that make the game anything more than a simple sandbox, and the graphics really are terrible... That being said, the game itself is great, and the ease with which it can be modified is also great, so this shouldn't be construed as a dig against Minecraft, I'm just not a defender of the faith.
I suppose if someone wanted to get pedantically technical, one could argue that the extra lib directory in/usr causes a several microsecond increase on latency during the runtime linker's initialization....... if you're running a non-hashed directory inode filesystem....
Once the law says so, and the schools must teach that it is so, it's only a matter of time before it is effectively 3. Our scientific knowledge and progress is in fact bounded by our laws, even if the physical laws themselves are not.
I don't think the science itself is. I do think that the science is being abused by profiteers in both directions (both supporting anthropogenic cause, and denying it)
I do not, however, think that it's healthy to continue to deny the science just because you don't like what one side of the profiteers are lobbying for us to do about it. Instead, lobby for saner solutions. Putting one's head in the sand and screaming that it isn't happening is just lunacy. You're presenting no real alternative to the other side, and they're going to get their way, and it's going to be your fault.
Very likely it will be rotating about its long axis as well
I'm sorry, are you saying it'll be rotating with the pointy end down? Why can you not simply keep it pointed at the nose? Or are you saying it will be tumbling? If so, I guess that would make it pretty damn hard to do much damage.
I think maybe you're underestimating the power of a 30kW beam collimated to a few square inches of area when fire through a mile of thick atmosphere, nevermind fired upward into atmosphere of rapidly dropping density? (The test scored the kill in seconds at 1 mile- and I imagine did plenty of damage in fractions of a second. The "seconds" was for complete burn through to disable the engine block)
My understanding is that ICBM RVs are very aerodynamic (sharp cones), entering at a significant enough velocity as to undergo massive friction and compression wave heating, and have quite stable trajectories, atmosphere be damned (Enough momentum and aerodynamic shape should reduce the ability of the atmosphere to move it around much, yes?) and pictures I've seen of MIRV re-entries do in fact look unnaturally straight.
I'm also not sure disrupting the airframe of an RV is much use. Again, it's a small, dense cone, in a high velocity ballistic trajectory. I'm not sure even significant damage to that airframe is going to cause destruction of the warhead even should the airframe come entirely apart.
I still don't think you could hope for much more than disabling the warhead in the RV, dropping a tumbling nuke onto the ground at high velocity, hopefully not spreading too much isotopic matter all over the place, and that applies for ballistic weaponry applied against the RV as well.
No, because the material with 95% reflectivity will not have that after it begins to heat up and is destroyed catastrophically.
One does not mirror 30kW in a few square inches of area. 99% still wouldn't be enough. It would no longer be reflective in milliseconds, and then it would burn like anything else.
I don't know if staying on target is a problem. The RVs are on a ballistic trajectory. However, completely destroying them may be a bit of a trick. I think the best you can hope for is disabling the warhead and having a dirty bomb fall on your head.
Other than... precedent, history, and the 24 states with laws punishing faithless voters, and the myriad of states with laws making it very difficult to be a faithless elector...
as the Donner Party
Or their dinner
Well, it wasn't added to the rules until 1906, and traditionally, we didn't have a national language, because the framers didn't see a need, and the colonies at the time housed people from many European descents (especially since colonies such as New York weren't originally British, many portions of the newly formed country were very recently French, lost during the French-Indian War, and disputed with Spain, like western Georgia). Later on, it became increasingly relevant as the US "acquired" territories with predominantly non-English speakers (everything west of the Mississippi) through either Conquest (Mexico, Hawaii) or purchase/treaty (France - The entire midwest and Louisiana, Spain - Florida).
Teddy Roosevelt was the first major person I know of to champion the English-only movement, in the early 20th century, and several states outright rejected it, having de jure multi-lingual government document requirements, and Louisiana having 2 de jure official languages (English, French).
I don't really see what the benefit of enforcing a national language is. I don't see a multi-lingual government as a shortcoming, I guess; and a majority of the continental US is in fact land that was acquired while populated with Spanish and French speakers. I say let the language demographics evolve naturally.
Informative.. Educational... Depressing.
And a cocked smile in America, if you asked for a rubber.
or pay 200% overtime and deal with law mandated recovery time?
Wait... what? Do we live in the same US? A salaried programmer making more than $455 a week (see: all of them) in the US is exempt from FLSA overtime pay requirements (yay!)
Holy fucking racist bullshit, batman!
You think German is more intelligible to an English speaker than ebonics?
Anti-social? I suspect it isn't that at all to those who speak it with each other.
Anti-assimilationist? Ahhh, and your true colors show. Perhaps it's you who is failing to assimilate with the movement of demographics and culture.
It's not at all uncommon for those who are standing still to look at the vast majority of mankind passing them by and think that it is they who are failing to assimilate. You must be some kind of genius.
Also possibly a Canuck, they too forsake the Queen's spelling of apologise.
Apologize? Now, that's not how the Queen spells it, is it mate?
Hoser, or self-loathing American?
Na, the US never has, and never will have a national language ;)
Don't like the demographics? Become a fascist, or breed more.
Sorry, but that's false.
ELF binaries in linux have what is called an interpreter in the header. It's a binary that the kernel actually loads to setup the ELF in memory before execution. That binary is responsible for the start-time aspect of run-time linking (setup the delayed-load tables, GOT, PLT, etc.)
For 32-bit binaries, the 32-bit loader is specified as the interpreter (at compile time), for 64-bit binaries, the 64-bit loader is.
The loaders maintain caches of what libraries of what architecture are where, this cache is loaded every time the loader is fired off by the kernel to setup an ELF program for execution. There is no trying to load different loaders or libraries from different architectures. It just doesn't work that way.
Context switches between long-mode and protected-mode code are not any more expensive (practically speaking) than homogenous context switches. This has all been profiled. If SGI offered the ability to not support 32-bit userspace code at the kernel level (certainly doesn't matter at the kernel level- it's not like people are allowed to jump into the kernel.) it was likely because of an architectural nightmare like their 64-bit kernel running on the Itanic.
He's getting 32-bit libs that he didn't realize he was getting.
Not that that's a problem... in any way, whatsoever.
I would love to hear what the speed benefit is of not having 2 separate runtime linkers that each only apply to binaries of their architecture.
In a way, it does make it easy to get your game running on multiple platforms. The base dependencies for Steam are also basic middleware installed on virtually every Linux machine, and Steam ensures that it is there. SDL/OpenGL are easier to use than DirectX (IMO, I concede), and making sure that Steam enforces the dependencies across multiple flavors of platforms does in fact overcome the most difficult aspect of Linux development- dealing with the nightmare of different ways or slight variations in the details for pulling in dependencies on different platforms.
Need the 32-bit version of of the Pulseaudio libraries, but you refuse to install that stuff on your machine? Don't worry, Steam has you covered.
Steam is, in essence, a portion of the middleware, a compatibility layer, to a point.
It's certainly dick-headed... But profoundly and willfully ignorant? I don't know. The Minecraft engine is pure shit. I work with the base classes frequently while work with mods. It really does take an i7 with a decent GPU and a couple gigs of ram to really run it worth a shit with any kind of mods that make the game anything more than a simple sandbox, and the graphics really are terrible... That being said, the game itself is great, and the ease with which it can be modified is also great, so this shouldn't be construed as a dig against Minecraft, I'm just not a defender of the faith.
I suppose if someone wanted to get pedantically technical, one could argue that the extra lib directory in /usr causes a several microsecond increase on latency during the runtime linker's initialization....... if you're running a non-hashed directory inode filesystem....
Or the claim is entirely bullsh.
For now.
Once the law says so, and the schools must teach that it is so, it's only a matter of time before it is effectively 3. Our scientific knowledge and progress is in fact bounded by our laws, even if the physical laws themselves are not.
I don't think the science itself is. I do think that the science is being abused by profiteers in both directions (both supporting anthropogenic cause, and denying it)
I do not, however, think that it's healthy to continue to deny the science just because you don't like what one side of the profiteers are lobbying for us to do about it. Instead, lobby for saner solutions. Putting one's head in the sand and screaming that it isn't happening is just lunacy. You're presenting no real alternative to the other side, and they're going to get their way, and it's going to be your fault.
Very likely it will be rotating about its long axis as well
I'm sorry, are you saying it'll be rotating with the pointy end down? Why can you not simply keep it pointed at the nose? Or are you saying it will be tumbling? If so, I guess that would make it pretty damn hard to do much damage.
I think maybe you're underestimating the power of a 30kW beam collimated to a few square inches of area when fire through a mile of thick atmosphere, nevermind fired upward into atmosphere of rapidly dropping density? (The test scored the kill in seconds at 1 mile- and I imagine did plenty of damage in fractions of a second. The "seconds" was for complete burn through to disable the engine block)
My understanding is that ICBM RVs are very aerodynamic (sharp cones), entering at a significant enough velocity as to undergo massive friction and compression wave heating, and have quite stable trajectories, atmosphere be damned (Enough momentum and aerodynamic shape should reduce the ability of the atmosphere to move it around much, yes?) and pictures I've seen of MIRV re-entries do in fact look unnaturally straight.
I'm also not sure disrupting the airframe of an RV is much use. Again, it's a small, dense cone, in a high velocity ballistic trajectory. I'm not sure even significant damage to that airframe is going to cause destruction of the warhead even should the airframe come entirely apart.
I still don't think you could hope for much more than disabling the warhead in the RV, dropping a tumbling nuke onto the ground at high velocity, hopefully not spreading too much isotopic matter all over the place, and that applies for ballistic weaponry applied against the RV as well.
No, because the material with 95% reflectivity will not have that after it begins to heat up and is destroyed catastrophically. One does not mirror 30kW in a few square inches of area. 99% still wouldn't be enough. It would no longer be reflective in milliseconds, and then it would burn like anything else.
No, because it's only white for a fraction of a millisecond at that energy.
I imagine not very long before it causes enough damage (melting?) to make the shell's formerly ballistic trajectory no longer a threat to you
I don't know if staying on target is a problem. The RVs are on a ballistic trajectory. However, completely destroying them may be a bit of a trick. I think the best you can hope for is disabling the warhead and having a dirty bomb fall on your head.
You'd perhaps be surprised how difficult it is to mirror 40kW of coherent light without liquid nitrogen.