So I guess then, with your logic, you can't steal one's ideas either
As a matter of fact, you can't steal ideas. You may be able to plagiarize a work or infringe on a patent, but neither of those violations is theft. (And outside those two cases, copying others' ideas isn't even wrongful.)
Why would it raise concerns about the GPL in particular? If the GPL can be revoked after the fact, then *any* software license (proprietary, FOSS or whatever) could likewise be revoked. Any 3rd party code of any kind in commercial applications would be at similar risk.
The CPU is way faster than RAM.Replacing the cache (which is large physically compared to RAM) with normal DRAM would be a disaster for performance.
That doesn't necessarily matter if the DRAM were freed of external pin packaging constraints. For example, imagine if the CPU had an SRAM L1 cache, no L2 cache and on-chip DRAM main memory. With DRAM, you can internally access an entire row at one time. Using row-wide access, you could fill entire virtual memory pages into the L1 cache in a single RAM cycle.
Getting the most out of such a setup might require changes to the way the memory and cache have been managed for the last 20 years, but the total potential bandwith available from on-chip DRAM could be staggering.
Am I really the only one worried that determining the precise weight of the Higgs Boson will result in the Earth being crushed into a tiny particle the size of a pea?
Perhaps, but in the process we'd obtain important new data that greatly reduces the uncertainty in the parameters of the Drake Equation.
No, you can't. Unless you're an utter fool, you have some kind of insurance so that if you get sick, other people will pay your bills. I guarantee that you can't personally afford to pay the entire bill for the worst case health problems.
Now the only question becomes: who is in the insurance risk pool, and how do the premiums get paid. The current US healthcare system wastes 30% of the incoming money on pencil pushers who try to grapple with those questions, when it could be more simply solved at a fraction of the cost with a single risk pool and uniform premiums. This is underscored by the fact that essentially every other developed country in the world does that, all at a much lower cost per capita, and many with significantly healthier and longer living populations.
So in theory your argument sounds good, but in practice the US healthcare system is an expensive, stressful mess compared to other real-world government run systems. Any savings you think you're getting by hanging out in a low risk pool (at least for now while you're healthy and don't have any family obligations) are being squandered in the costs of accounting for those separate risk pools.
Why in the hell, in Texas, rich oil state with lots of land, do we need tolls?
Because one of the fundamental platforms of the dominant party in Texas is that government should be run "more like a business". What would be more businesslike than charging people for what they use?
You're the one doing the handwaving if you seriously claim that $RANDOM_PROPRIETARY_NDA_LICENSE_FROM_EARLY_1990S is statistically more likely than not to be compatible with current popular FOSS licenses.
There's way too many people on/. who think that open source licenses are legally mystically different from the myriad of commercial licenses out there. They're not.
That's right: many open source licenses are incompatible with each other. It just happens that the license for this code is almost certainly incompatible with most any open source license.
Any dependencies on restrictively licensed subroutine libraries can be re-engineered.
Since Microsoft did half the work on the early releases of OS/2, the problem is a little more involved than that. Why would IBM bother to invest the $millions it would take to sanitize, untangle and rewrite huge chunks of an entire dead operating system?
Every command line I've ever seen has all of one real UI difference with the DOS commandline -- variable color. That's it.
There's one other little difference: If you know anything about using shells, CMD.EXE will make you want to tear your hair out within 30 seconds. (And COMMAND.COM would make you want to shoot yourself.) Real shells don't make you want to do those things.
I've been watching a lot of the old Twilight Zone episodes lately, and based on the examples they show, asteroids look like a better destination than the moon anyway. Asteroids seem much more habitable to humans. It looks like they have breathable atmospheres, earth-like gravity, and in fact they look almost exactly like our own Mohave Desert. In comparison, the moon is a bleak airless wasteland. I'm all for it.
Your ancient history knowledge is 50 years out of date. Archaeological evidence shows that they were built with paid labor, not slaves.
The world has changed a bit, Enlightenment, Capitalism, Individual Rights, Socialism/Communism(failed)...
And in every single stage of history you mention, people were taxed to pay for big government projects. They still are. Why do some people act as if they're surprised by this?
I can think of one drawback which is premature wear on the compressor contactors.
Well, I'm in a similar program. I get a small discount on rates, and the power company is supposed to pay me a few bucks each time they cut power to my A/C unit. In six years, they have yet to cut the power even a single time, so I don't think that the compressor wear issue will be much of a problem for me.
So, if this is a problem, and as I pointed out it's doubtful that it is, then have a small tank of hydrogen (or a chemical generator) to replace the leakage. It wouldn't be a significant cost, nor would it be any bigger problem than a car that leaks a little oil. Why do you keep making this out to be a bigger deal than it is?
Ok, please find me a link that documents prototype hydrogen vehicles (some of which are in actual daily use as city buses, etc) leaking significant amounts of their fuel. This would be a dangerous situation; we'll need to alert the drivers. Thx.
The key steals valuable space from the spacebar (no pun intended).
OTOH, I really like an unintended consequence of the Windows key. I've got a MS "Natural Multimedia" keyboard where the Windows key shoves the left Alt key over to where it's comfortably positioned directly under my left thumb. Since the vim editor ships without any Alt combos premapped, all of them are free for me to customize for may favorite commands and macros. I get easy access to a couple of dozen of my most frequently used commands while barely moving any fingers. (Most importantly, I mapped Alt+F to replace the infamous ESC mode switch.)
The truly stupid thing about this keyboard is Microsoft's brain-dead idea for the "F-Lock" key, which replaces all the function keys with bogus new fixed function keycodes like "Open" and "Send". The keyboard comes up by default with the function keys disabled, and there's no way to switch the mode via software; you have to physically press the F-lock button to switch modes. I had to find and install a special script to make Linux reinterpret the stupid new keycodes as regular function keys.
Given that prototype vehicles are currently in use which are fueled by hydrogen gas pressurized in tanks at hundreds of atmospheres, I doubt that the leakage problem is as severe as you make it out to be. What's more, if hydrogen is cheap enough to burn like gasoline, then replacing a little leaked working fluid that will get cycled hundreds of times in the engine wouldn't be any big deal.
It's not meaningless the way security professionals use it. You'd just like to redefine it to be meaningless with your own private definition. Have fun.
The commonly accepted use of the term "security through obscurity" does not include encryption keys. While your line of reasoning may be technically true in some sense, it would render the term completely meaningless.
There's a bit of difference between a closed source system that is trivially reverse engineered and a properly managed encryption key that would take millions of times longer than the age of the universe to decipher.
I'm not talking about Windows in particular. I'm saying that *security through obscurity* is an ineffective strategy. You say it's like a lock; I say it's like a limp noodle.
It's barely a speed bump for the evil hackers who feed garbage into programs to crash them, then poke around in a debugger to find where they broke, then write some machine code to take advantage of the bugs. Thinking that lack of access to source code is anything like a "lock" is just self delusion.
It's like arguing that there's no point in locking your door because 100,000 houses with locks were broken into.
A more apt analogy would be: There's no point in locking your door using a limp spaghetti noodle because a limp noodle makes a completely ineffective lock.
What about skipping this step for data centres, where all equipment runs on DC anyway?
Because to power each server at 12VDC from the 1 megavolt long-distance DC transmission line, you have to string together more than 80,000 servers in series. Then when one server blows out, all 80,000 go down along with it. Then you have to test them one at a time like a string of Christmas lights until you find the bad server, which could take weeks.
Slashdot Mirror
As a matter of fact, you can't steal ideas. You may be able to plagiarize a work or infringe on a patent, but neither of those violations is theft. (And outside those two cases, copying others' ideas isn't even wrongful.)
Why would it raise concerns about the GPL in particular? If the GPL can be revoked after the fact, then *any* software license (proprietary, FOSS or whatever) could likewise be revoked. Any 3rd party code of any kind in commercial applications would be at similar risk.
That doesn't necessarily matter if the DRAM were freed of external pin packaging constraints. For example, imagine if the CPU had an SRAM L1 cache, no L2 cache and on-chip DRAM main memory. With DRAM, you can internally access an entire row at one time. Using row-wide access, you could fill entire virtual memory pages into the L1 cache in a single RAM cycle.
Getting the most out of such a setup might require changes to the way the memory and cache have been managed for the last 20 years, but the total potential bandwith available from on-chip DRAM could be staggering.
Perhaps, but in the process we'd obtain important new data that greatly reduces the uncertainty in the parameters of the Drake Equation.
No, you can't. Unless you're an utter fool, you have some kind of insurance so that if you get sick, other people will pay your bills. I guarantee that you can't personally afford to pay the entire bill for the worst case health problems.
Now the only question becomes: who is in the insurance risk pool, and how do the premiums get paid. The current US healthcare system wastes 30% of the incoming money on pencil pushers who try to grapple with those questions, when it could be more simply solved at a fraction of the cost with a single risk pool and uniform premiums. This is underscored by the fact that essentially every other developed country in the world does that, all at a much lower cost per capita, and many with significantly healthier and longer living populations.
So in theory your argument sounds good, but in practice the US healthcare system is an expensive, stressful mess compared to other real-world government run systems. Any savings you think you're getting by hanging out in a low risk pool (at least for now while you're healthy and don't have any family obligations) are being squandered in the costs of accounting for those separate risk pools.
Because one of the fundamental platforms of the dominant party in Texas is that government should be run "more like a business". What would be more businesslike than charging people for what they use?
You're the one doing the handwaving if you seriously claim that $RANDOM_PROPRIETARY_NDA_LICENSE_FROM_EARLY_1990S is statistically more likely than not to be compatible with current popular FOSS licenses.
That's right: many open source licenses are incompatible with each other. It just happens that the license for this code is almost certainly incompatible with most any open source license.
Any dependencies on restrictively licensed subroutine libraries can be re-engineered.Since Microsoft did half the work on the early releases of OS/2, the problem is a little more involved than that. Why would IBM bother to invest the $millions it would take to sanitize, untangle and rewrite huge chunks of an entire dead operating system?
There's one other little difference: If you know anything about using shells, CMD.EXE will make you want to tear your hair out within 30 seconds. (And COMMAND.COM would make you want to shoot yourself.) Real shells don't make you want to do those things.
I've been watching a lot of the old Twilight Zone episodes lately, and based on the examples they show, asteroids look like a better destination than the moon anyway. Asteroids seem much more habitable to humans. It looks like they have breathable atmospheres, earth-like gravity, and in fact they look almost exactly like our own Mohave Desert. In comparison, the moon is a bleak airless wasteland. I'm all for it.
Why yes, during WWI air defenses used to routinely light up German Zeppelin bombers over England like roman candles.
Contrary to the conventional wisdom on /., hydrogen does burn.
Your ancient history knowledge is 50 years out of date. Archaeological evidence shows that they were built with paid labor, not slaves.
The world has changed a bit, Enlightenment, Capitalism, Individual Rights, Socialism/Communism(failed)...And in every single stage of history you mention, people were taxed to pay for big government projects. They still are. Why do some people act as if they're surprised by this?
Because that's the way the world has worked since the time the Pyramids were built.
Well, I'm in a similar program. I get a small discount on rates, and the power company is supposed to pay me a few bucks each time they cut power to my A/C unit. In six years, they have yet to cut the power even a single time, so I don't think that the compressor wear issue will be much of a problem for me.
Because that's the way the world works.
If everyone had a proper respect for each otherBut they don't. They never have at any time in the history of the human race, and they almost certainly never will.
You don't vote it out. The warlord who comes out victorious in the ensuing battle for power will end up abolishing the state of anarchy.
So, if this is a problem, and as I pointed out it's doubtful that it is, then have a small tank of hydrogen (or a chemical generator) to replace the leakage. It wouldn't be a significant cost, nor would it be any bigger problem than a car that leaks a little oil. Why do you keep making this out to be a bigger deal than it is?
Ok, please find me a link that documents prototype hydrogen vehicles (some of which are in actual daily use as city buses, etc) leaking significant amounts of their fuel. This would be a dangerous situation; we'll need to alert the drivers. Thx.
OTOH, I really like an unintended consequence of the Windows key. I've got a MS "Natural Multimedia" keyboard where the Windows key shoves the left Alt key over to where it's comfortably positioned directly under my left thumb. Since the vim editor ships without any Alt combos premapped, all of them are free for me to customize for may favorite commands and macros. I get easy access to a couple of dozen of my most frequently used commands while barely moving any fingers. (Most importantly, I mapped Alt+F to replace the infamous ESC mode switch.)
The truly stupid thing about this keyboard is Microsoft's brain-dead idea for the "F-Lock" key, which replaces all the function keys with bogus new fixed function keycodes like "Open" and "Send". The keyboard comes up by default with the function keys disabled, and there's no way to switch the mode via software; you have to physically press the F-lock button to switch modes. I had to find and install a special script to make Linux reinterpret the stupid new keycodes as regular function keys.
Given that prototype vehicles are currently in use which are fueled by hydrogen gas pressurized in tanks at hundreds of atmospheres, I doubt that the leakage problem is as severe as you make it out to be. What's more, if hydrogen is cheap enough to burn like gasoline, then replacing a little leaked working fluid that will get cycled hundreds of times in the engine wouldn't be any big deal.
It's not meaningless the way security professionals use it. You'd just like to redefine it to be meaningless with your own private definition. Have fun.
There's a bit of difference between a closed source system that is trivially reverse engineered and a properly managed encryption key that would take millions of times longer than the age of the universe to decipher.
It's barely a speed bump for the evil hackers who feed garbage into programs to crash them, then poke around in a debugger to find where they broke, then write some machine code to take advantage of the bugs. Thinking that lack of access to source code is anything like a "lock" is just self delusion.
A more apt analogy would be: There's no point in locking your door using a limp spaghetti noodle because a limp noodle makes a completely ineffective lock.
Because to power each server at 12VDC from the 1 megavolt long-distance DC transmission line, you have to string together more than 80,000 servers in series. Then when one server blows out, all 80,000 go down along with it. Then you have to test them one at a time like a string of Christmas lights until you find the bad server, which could take weeks.