I think that the most significant outcome of this whole story is that we've found the only conspiracy theory on this planet that the typical Trump supporter won't buy into.
0F is the temperature of a particular ice/brine mixture, and it was approximately the lowest temperature typically experienced in Fahrenheit's area. I suppose that one advantage of that is not having to use negative values very often.
100F is approximately human body temperature. That's pretty easy to relate to.
One nice property of the system is that 0F is often dangerously cold, and 100F is often dangerously hot.
I never use variable names of more than one character unless all possible single character names have already been used, which rarely happens.
If you're not routinely using up all possible single-character variable names, then you're not making your functions large enough, and/or you're not using enough global variables. You can do better.
Nitromethane is even better for squeezing power out of a small internal combustion engine. Some people running on nitromethane get more than 8000 HP out of a pushrod V8, and they don't need any cooling system at all.
Therefore, everybody should be using top fuel in their cars.
No, "better healthcare outcomes" is a measurment anomaly.
The fact that the average is dragged down because a large percentage of the US population doesn't get adequate health care is not a "measurement anomaly". It's an epic failure.
It's like a C average student claiming: "I'm really a straight-A student! I got As in all the classes I didn't flunk. (And BTW, for some reason my education cost twice as much as that of any other student.)"
Reformatting code is a big no-no in shared version-controlled environments.
In many version-controlled environments, a hook is added to the check-in command to automatically run the reformatter, so there are never any diffs in the history caused by the formatting process.
I really don't like some of the settings that were made on the formatter my current project is using, but at least I never have to worry about things like typing lines too long. They're automatically fixed up on commit.
Not having a single sports molecule in my body, I had no clue what they meant by "Juno is a spinning, robotic probe as wide as a basketball court."
Remember when you were in high school and they sometimes made all the students go to a big room where you sat on hard benches and the principal emceed for some brief talks and activities?
That word, as defined by pedants, is utterly useless. Other than those who hail from one particular ancient civilization that had a certain peculiar military punishment, nobody kills exactly 1 in 10 of anything.
That's why the vast majority of the population who have normal minds use an entirely different definition of the word. A definition that's actually relevant to enough real situations to justify the word's existence.
No, not nearly that hot. Most drip coffee machines *brew* it at the McDonald's temperature, but it is kept at a much lower temperature (around 160F) in the carafe. One reason for this is that it rapidly loses quality if you keep it too hot.
People know what temperature coffee is almost universally served at, and they take the appropriate care. If you fill a cup of coffee from a coffee machine to the brim and carry it around, you just don't need to be that careful because it's just not that hot (unless it's from McDonald's). If you fill the same cup to the brim with water at a full rolling boil out of a pot, you're damned well going to be instinctively much more careful with it, because a small splash could give you serious burns.
You may now post one of your typical obscenity-laced abusive replies. It won't make you any less wrong.
You'd be free to use their code without restriction, so they wouldn't be selling it back to you. They could try to lock it up in a hardware device, but there'd be no DMCA to prevent people from cracking such attempts and freely distributing cracking tools and software extracted with them. You might need a decompiler in the worst case, but I imagine that in such a world highly refined decompilers would be one of the most popular developer tools.
If it exists, what is the name of the economic principle that explains why people can't reliably effect policy change by way of boycott?
The situation is a variation of the multi-player "prisoner's dilemma" game. Basic game theory says that the best choice for any individual player is "defect", which in this case means sign the agreement and take the job.
Simulating a world without copyrights would mean they should be ok with someone taking their code and reusing it however they want.
You can't have it both ways.
If the world actually had no copyright, in turn you could use whatever *they* did to your code however *you* want.
Given that the simulation isn't perfect and that's not possible, you're stuck with the restrictions that come with viral licenses. I'm sure that most free software advocates would happily ditch those viral restrictions in return for abolishing copyright laws.
This is the sort of thing people on slashdot always say until someone rips of open source code without giving changes back...
That's because the creators of the "viral" licenses you refer to used licensing to try to roughly simulate a world without copyrights. (Hence, they are often tagged with the ironic name "copyleft license".) People get mad in your example because somebody else is trying to pull the content out of this simulated non-copyright world and put it back under the usual copyright restrictions.
I'm hoping that knocking sound goes away. Sometimes these things fix themselves, you know?
The knocking sound means that your system is low on hard drive oil.
Just get a can of WD-40, drill a small (1/8") hole in the drive, and spray a couple of healthy blasts of the WD-40 into the drive. This will almost always cure the knocking sound.
People never seem to get this straight: WD-40 is a water displacer. While it may help keep your hard drive from corroding, it won't properly lubricate the moving parts.
You need to squirt a generous amount of a suitable machine oil into your hard drive to properly address the noise. And don't forget to tape the hole when you're done: the oil can attract dirt that would mess up the delicate drive heads.
Oh gee, multiple pages of documentation to achive the equivalent of:
$ cmd &
But it's all worth it, because now my background command is a frigging "service"! I always wanted to create my own service! I'm doing really important stuff now!
In Unix and its derivatives, frequently used commands are terse. If there's something new for me to learn, it ought to be a half-dozen keystrokes.
No, I am not going to learn to use a new command that has over 40 extra keys to type to support a misfeature that has no benefits to me. No, I am not going to look up that damned command sequence in the man pages every time I'm on a new system and it's not in the history stack.
No other Unix command line utility imposes that burden on the user.
You just start them with "systemd-run --user --scope screen" and everything works as before
No it does not work as before. Before you just typed "screen", and it worked on any system.
Life is too short to spend time committing all that extra crap to memory or else having to configure every system you touch with custom shortcuts.
If you think that having to remember to type "systemd-run --user --scope-screen" in front of a frequently used utility (and having the system silently clobber your work if you forget) is reasonable, you're deluded.
The most commonly used x86 instructions need no classical microcode. They're no more complex than three RISC instructions (address computation, load plus ALU). They get split into corresponding micro-ops by hardware (not microcode), and are run concurrently in the various CPU logic units, just like modern RISC CPUs. An added bonus is the compact encoding is very beneficial to instruction cache bandwidth.
I think that you're confusing the issue with the poorly-conceived 80286 era task-level instructions, which nobody uses anymore. That unused microcode languishes in an insignificant lonely corner somewhere on the die.
If the compiler had more valuable insight into low-level instruction ordering than the actual CPU itself does, then the Itanium would not have been such an epic failure.
Hint: Since the days of the Pentium II, the instructions and registers programmer perceives have had almost zero resemblance to the internal instructions and registers actually used inside the CPU.
Slashdot Mirror
I think that the most significant outcome of this whole story is that we've found the only conspiracy theory on this planet that the typical Trump supporter won't buy into.
What does Fahrenheit relate to? Who knows?
0F is the temperature of a particular ice/brine mixture, and it was approximately the lowest temperature typically experienced in Fahrenheit's area. I suppose that one advantage of that is not having to use negative values very often.
100F is approximately human body temperature. That's pretty easy to relate to.
One nice property of the system is that 0F is often dangerously cold, and 100F is often dangerously hot.
I never use variable names of more than one character unless all possible single character names have already been used, which rarely happens.
If you're not routinely using up all possible single-character variable names, then you're not making your functions large enough, and/or you're not using enough global variables. You can do better.
Nitromethane is even better for squeezing power out of a small internal combustion engine. Some people running on nitromethane get more than 8000 HP out of a pushrod V8, and they don't need any cooling system at all.
Therefore, everybody should be using top fuel in their cars.
No, "better healthcare outcomes" is a measurment anomaly.
The fact that the average is dragged down because a large percentage of the US population doesn't get adequate health care is not a "measurement anomaly". It's an epic failure.
It's like a C average student claiming: "I'm really a straight-A student! I got As in all the classes I didn't flunk. (And BTW, for some reason my education cost twice as much as that of any other student.)"
Reformatting code is a big no-no in shared version-controlled environments.
In many version-controlled environments, a hook is added to the check-in command to automatically run the reformatter, so there are never any diffs in the history caused by the formatting process.
I really don't like some of the settings that were made on the formatter my current project is using, but at least I never have to worry about things like typing lines too long. They're automatically fixed up on commit.
Not having a single sports molecule in my body, I had no clue what they meant by "Juno is a spinning, robotic probe as wide as a basketball court."
Remember when you were in high school and they sometimes made all the students go to a big room where you sat on hard benches and the principal emceed for some brief talks and activities?
That was probably a basketball court.
That word, as defined by pedants, is utterly useless. Other than those who hail from one particular ancient civilization that had a certain peculiar military punishment, nobody kills exactly 1 in 10 of anything.
That's why the vast majority of the population who have normal minds use an entirely different definition of the word. A definition that's actually relevant to enough real situations to justify the word's existence.
Coffee is to be served hot.
No, not nearly that hot. Most drip coffee machines *brew* it at the McDonald's temperature, but it is kept at a much lower temperature (around 160F) in the carafe. One reason for this is that it rapidly loses quality if you keep it too hot.
People know what temperature coffee is almost universally served at, and they take the appropriate care. If you fill a cup of coffee from a coffee machine to the brim and carry it around, you just don't need to be that careful because it's just not that hot (unless it's from McDonald's). If you fill the same cup to the brim with water at a full rolling boil out of a pot, you're damned well going to be instinctively much more careful with it, because a small splash could give you serious burns.
You may now post one of your typical obscenity-laced abusive replies. It won't make you any less wrong.
You'd be free to use their code without restriction, so they wouldn't be selling it back to you. They could try to lock it up in a hardware device, but there'd be no DMCA to prevent people from cracking such attempts and freely distributing cracking tools and software extracted with them. You might need a decompiler in the worst case, but I imagine that in such a world highly refined decompilers would be one of the most popular developer tools.
If it exists, what is the name of the economic principle that explains why people can't reliably effect policy change by way of boycott?
The situation is a variation of the multi-player "prisoner's dilemma" game. Basic game theory says that the best choice for any individual player is "defect", which in this case means sign the agreement and take the job.
Simulating a world without copyrights would mean they should be ok with someone taking their code and reusing it however they want.
You can't have it both ways.
If the world actually had no copyright, in turn you could use whatever *they* did to your code however *you* want.
Given that the simulation isn't perfect and that's not possible, you're stuck with the restrictions that come with viral licenses. I'm sure that most free software advocates would happily ditch those viral restrictions in return for abolishing copyright laws.
This is the sort of thing people on slashdot always say until someone rips of open source code without giving changes back...
That's because the creators of the "viral" licenses you refer to used licensing to try to roughly simulate a world without copyrights. (Hence, they are often tagged with the ironic name "copyleft license".) People get mad in your example because somebody else is trying to pull the content out of this simulated non-copyright world and put it back under the usual copyright restrictions.
He wrote one of Johnny Cash's best songs.
They need to be extremely careful about this scheme of mixing CO2 with rocks. Don't forget that this is how "Mikey" got killed.
If all of the countries other than the US were to agree to use the same fork, then the original DNS system would become the USA's very own intranet.
That's no more than nine phones world wide!
I find that the results from numerical computations on today's transistor-based CPUs often have an undesirable "harshness".
Vacuum tube CPUs will hopefully yield richer, more mellow computational results.
The blurb is probably talking about the scale in one dimension. The volume ratio would be 1,000,000 cubed.
I'm hoping that knocking sound goes away. Sometimes these things fix themselves, you know?
The knocking sound means that your system is low on hard drive oil.
Just get a can of WD-40, drill a small (1/8") hole in the drive, and spray a couple of healthy blasts of the WD-40 into the drive. This will almost always cure the knocking sound.
People never seem to get this straight: WD-40 is a water displacer. While it may help keep your hard drive from corroding, it won't properly lubricate the moving parts.
You need to squirt a generous amount of a suitable machine oil into your hard drive to properly address the noise. And don't forget to tape the hole when you're done: the oil can attract dirt that would mess up the delicate drive heads.
Oh gee, multiple pages of documentation to achive the equivalent of:
$ cmd &
But it's all worth it, because now my background command is a frigging "service"! I always wanted to create my own service! I'm doing really important stuff now!
In Unix and its derivatives, frequently used commands are terse. If there's something new for me to learn, it ought to be a half-dozen keystrokes.
No, I am not going to learn to use a new command that has over 40 extra keys to type to support a misfeature that has no benefits to me. No, I am not going to look up that damned command sequence in the man pages every time I'm on a new system and it's not in the history stack.
No other Unix command line utility imposes that burden on the user.
As I originally suspected, you are delusional.
You just start them with "systemd-run --user --scope screen" and everything works as before
No it does not work as before. Before you just typed "screen", and it worked on any system.
Life is too short to spend time committing all that extra crap to memory or else having to configure every system you touch with custom shortcuts.
If you think that having to remember to type "systemd-run --user --scope-screen" in front of a frequently used utility (and having the system silently clobber your work if you forget) is reasonable, you're deluded.
The most commonly used x86 instructions need no classical microcode. They're no more complex than three RISC instructions (address computation, load plus ALU). They get split into corresponding micro-ops by hardware (not microcode), and are run concurrently in the various CPU logic units, just like modern RISC CPUs. An added bonus is the compact encoding is very beneficial to instruction cache bandwidth.
I think that you're confusing the issue with the poorly-conceived 80286 era task-level instructions, which nobody uses anymore. That unused microcode languishes in an insignificant lonely corner somewhere on the die.
If the compiler had more valuable insight into low-level instruction ordering than the actual CPU itself does, then the Itanium would not have been such an epic failure.
Hint: Since the days of the Pentium II, the instructions and registers programmer perceives have had almost zero resemblance to the internal instructions and registers actually used inside the CPU.