Next in: "We couldn't detect this attack because it was performed over the internet. If the attacker had tried to enter the building physically, we surely would have caught him before he could do any damage."
I don't think at the current point you could even define inflation rates for bitcoin. There's up to now no genuine bitcoin market of measurable size. Bitcoins are typically used as transaction medium, where the price is based on another currency, and as investment, where bitcoins are treated as asset instead of currency. Since inflation is defined as price growth (the price of goods sold in the currency, not the price of the currency in other currencies), and AFAICT virtually no goods are genuinely priced in bitcoins (what's the current price of butter in bitcoins, for example? Note that getting the price in dollars, and converting the value according to current exchange rates doesn't count), an inflation rate cannot be meaningfully defined.
Now I understand the fear about the GPL being contagious. People just fear that he didn't wash his hands before writing it, and therefore it is full of pathogens!;-)
If the patch comes from the original developer of the fix, they certainly can take it, because the original developer owns the copyright of the patch and therefore is not bound by the GPL (other than if he patches GCC, he must distribute that patched version of GCC under the GPL; but a patch for LLVM obviously is not a derived work of GCC).
It's valuable to say what they suggest to whitelist. When I read "whiltelisting" I thought it's about restricting internet access to known good addresses. Only the explanation told me that what they mean is whitelisting software.
While the modern Olympic games are inspired by the ancient ones, they are not the same. There's no line of continuity; the first modern games were already quite different from the last ancient ones. Note that the ancient games were to a large extent also a religious event.
You don't need pimpl for that; what you need is identical representations in memory. Then it doesn't matter if different code manipulates those representations, since all the next function will see is the representation, not how it was created.
It is not compatible with current libstdc++. But if the short string optimization (and/or some other representation changes in other classes) are considered advantageous enough, there's no reason why they could not, at some point, make a single incompatible change to libstdc++ (preferably at the same time when also the next compiler ABI update is necessary, which causes incompatible changes to compiled libraries anyway). The old libstdc++ implementation could still be available by a compiler flag or #define, for those cases where you need compatibility with old libraries which cannot be updated.
Of course a prerequisite would be that the authors of both standard libraries agree on the best implementation. Which probably is the largest hurdle.
Except that originally they made their Objective C front end proprietary, violating the GPL. Only after that license violation was pointed out to them by the FSF, they released it, as otherwise they would have to have do all the work of writing a compiler back end. Yes, they were never against taking code. However without the GPL, they might never have given code.
So the most stable value would be a combination of gold and platinum? Well, one could use gold-pressed platinum in that case. Well, let's drop the "p" of "platinum" to make it sound more fancy.;-)
Saying it is valuable for jewelry begs the question
Not really. Not everything that is expensive is valuable for jewellery (you'll not find much jewellery made of rhodium, for example). What makes gold perfect for jewellery even apart from its price is:
* It looks good * It doesn't corrode * It doesn't cause allergies * It is soft enough to be relatively easily brought into the desired form
After talking with several people who are rather educated in finance and the banking industry they all come back with the same response about fiat currencies: the entire system is built on bullshit
Slashdot Mirror
Measurements will reveal that the emitted frequency is actually 666 MHz, pointing to a less divine source. ;-)
Next in: "We couldn't detect this attack because it was performed over the internet. If the attacker had tried to enter the building physically, we surely would have caught him before he could do any damage."
I don't think at the current point you could even define inflation rates for bitcoin. There's up to now no genuine bitcoin market of measurable size. Bitcoins are typically used as transaction medium, where the price is based on another currency, and as investment, where bitcoins are treated as asset instead of currency. Since inflation is defined as price growth (the price of goods sold in the currency, not the price of the currency in other currencies), and AFAICT virtually no goods are genuinely priced in bitcoins (what's the current price of butter in bitcoins, for example? Note that getting the price in dollars, and converting the value according to current exchange rates doesn't count), an inflation rate cannot be meaningfully defined.
Yeah, posts are being deleted.
Now if that's true, that's a deviation from classic Slashdot that's a few orders of magnitude more worrying than the beta redesign.
Wait, they are Borg? That means, resistance is futile?
If this is the average quality of future stories, I don't need a beta to keep me away.
Which should never influence your moderation.
I've seen Star Trek, and thus I know that in an Enterprise environment, keys are always spoken aloud, for everyone to hear. ;-)
It's the equivalent to a text-on-one-page link for multipage stories. I've never seen any of those modded down.
Now I understand the fear about the GPL being contagious. People just fear that he didn't wash his hands before writing it, and therefore it is full of pathogens! ;-)
Nice ad hominem. Which is usually the last resort if you have no further factual arguments. I leave the conclusion to the reader.
If the patch comes from the original developer of the fix, they certainly can take it, because the original developer owns the copyright of the patch and therefore is not bound by the GPL (other than if he patches GCC, he must distribute that patched version of GCC under the GPL; but a patch for LLVM obviously is not a derived work of GCC).
It's valuable to say what they suggest to whitelist. When I read "whiltelisting" I thought it's about restricting internet access to known good addresses. Only the explanation told me that what they mean is whitelisting software.
Have the change require a hardware dongle. Lock the hardware dongle away where only the sysadmins have the (physical) keys. Problem solved.
Unless the sysadmin wants to see the porn, of course. ;-)
While the modern Olympic games are inspired by the ancient ones, they are not the same. There's no line of continuity; the first modern games were already quite different from the last ancient ones. Note that the ancient games were to a large extent also a religious event.
You don't need pimpl for that; what you need is identical representations in memory. Then it doesn't matter if different code manipulates those representations, since all the next function will see is the representation, not how it was created.
It is not compatible with current libstdc++. But if the short string optimization (and/or some other representation changes in other classes) are considered advantageous enough, there's no reason why they could not, at some point, make a single incompatible change to libstdc++ (preferably at the same time when also the next compiler ABI update is necessary, which causes incompatible changes to compiled libraries anyway). The old libstdc++ implementation could still be available by a compiler flag or #define, for those cases where you need compatibility with old libraries which cannot be updated.
Of course a prerequisite would be that the authors of both standard libraries agree on the best implementation. Which probably is the largest hurdle.
Except that originally they made their Objective C front end proprietary, violating the GPL. Only after that license violation was pointed out to them by the FSF, they released it, as otherwise they would have to have do all the work of writing a compiler back end. Yes, they were never against taking code. However without the GPL, they might never have given code.
So the most stable value would be a combination of gold and platinum? Well, one could use gold-pressed platinum in that case. Well, let's drop the "p" of "platinum" to make it sound more fancy. ;-)
Not really. Not everything that is expensive is valuable for jewellery (you'll not find much jewellery made of rhodium, for example). What makes gold perfect for jewellery even apart from its price is:
* It looks good
* It doesn't corrode
* It doesn't cause allergies
* It is soft enough to be relatively easily brought into the desired form
So you say I can use it as fertilizer? ;-)
Whoever modded this troll probably didn't try to follow the link. It works.
You forgot developers-beta, science-beta, etc.
Make your on /.? Someone should do that if /. is forcing this beta crap design. :(
See here.
All your examples are not a stopped clock, but a broken clock.