Yep, I agree that the language seems pointless, but you'd have a way better reception if you criticised the language (or the "advanced primitives" phrase), instead of arguing against well known and rightly used jargon.
"So if you were to take a year off from work, like a friend of mine did, to write a book, you'd be fine with people stealing copies of it?"
Way to miss the point. The current system is so flawed that we'd be better without it, even if nobody takes a year off anymore to write a book. I have some doubts if no copyright would be the best possible system, but the point is that it is way better than the current situation.
You still haven't heard about that idea of making punishment greater than the earnings from the missbehaviour, did you? You know, if punishment is smaller than the eranings, why would the offender stop the missbehaviour?
No need for your Kill-A-Watt. The GP is way off. A fridge that uses 50kWh in a month (that is a very big one, or a very old one) averages at approximately 70W.
You have quite a good point. If syntax weirdeness were a problem, C would have never taken off. Lack of decent I/O is the problem with most languages that are easy to paralelize. It seems that most such languages aren't defined with I/O in mind, and it is easy to imagine why, doing I/O in a paralel environment is very complex.
Maybe they were fired because they complained too much that Sony didn't care about security. Or that they upped that complain into the CEO, that preferred the CIO version. Maybe they threatened to make the problem public and their boss didn't like it. Maybe they weren't seen as productive because they kept fixing things the entire day, instead of helping build new things, and were understaffed. Maybe the company didn't like the policies they tried to put in place, so not only didn't accept the policies, but also fired them (this option seems to be quite likely). Maybe they weren't competent enough to put some good security in place, but still dedicated enough to security so that they anoyed people. Or, finally maybe they were justly fired by incompentence.
If its metabolism was enough to keep it warm, and it has some mechanism to reduce the metabolism or get ride of the extra heat when it gets too warm, we have a warm blooded creature!!! Now it its metabolism was enough to keep it warm, it does not have some mechanism to slow that metabolism or get ride of the extra heat when it gets too warm, we have a dead creature!!! So, I guess stating that its metabolism can keep it warm is enough here.
Please compare a cold blooded creature (like a snake, for example) that often pass through months without eating and is ok with that, and a warm blooded creature that must eat every week (or even more often). Metabolism seems to be the biggest difference here, altough, IAMN a biologist...
To be fair, it is hard to be more expensive than Visa/MC/ACH. Also, one would work on some money that isn't the desired currency if the other party is willing to work such currency. If you can exchange it imediately, why would you refuse a currency that isn't your preferred one (maybe add a small amount for conversion, but not refuse).
I never expected Bitcoin to get where it is, and I don't expect it to go much further. But I was wrong once...
It may even have protection against a thermonuclear bomb exploding in the middle of the city, but I doubt the insurer will be able to pay if that happens.
"There is a reason that less than 1/5 of one percent of the US population are pilots."
Yeah, there is. It is because it is very expensive to get a license. Anyway, The GP is arguing for automitized flight, there is a reason the biggest airplanes aren't yet fully automatized, that is beause the technology is new, and society still didn't have the time to adapt to it.
Error: cast from 'const int*' to 'int' loses precision
Not at all what I was expecting. It didn't refuse to lose constness (I was expecting that), didn't complain about the & operator aplied to a const (that would be the right behaviour), and didn't work! Amazing. Pedantic and Wall changes nothing, changing i to 'const short' also changes nothing.
That said, that is a problem of the compilers. The standard says the & operator can't apply to a const.
Thread safety is quite an important requisite for a general porpouse library. You could already use COW on your code, but there is no good way that I'm aware of to implement it at the std libraries.
Just this one: "You don't see a problem with borrowing an inherently deflationary currency? Deflation makes it harder to repay a loan." Deflation makes interest rate go down, as inflation makes it go up. Unless the deflation is so severe that interest would go negative to compensate, there is no problem. People also aren't able to lend/borrow in a hightly inflationary currency. Also, being able to borrow in a currency isn't a requisite for that currency to be used on transactions.
Slashdot Mirror
I beg to differ. Where do you think that worldwide crisis we are having today comes from?
Yep, I agree that the language seems pointless, but you'd have a way better reception if you criticised the language (or the "advanced primitives" phrase), instead of arguing against well known and rightly used jargon.
Way to miss the point. The current system is so flawed that we'd be better without it, even if nobody takes a year off anymore to write a book. I have some doubts if no copyright would be the best possible system, but the point is that it is way better than the current situation.
You still haven't heard about that idea of making punishment greater than the earnings from the missbehaviour, did you? You know, if punishment is smaller than the eranings, why would the offender stop the missbehaviour?
Here, that may help you:
1kWh = 3600kJ
No need for your Kill-A-Watt. The GP is way off. A fridge that uses 50kWh in a month (that is a very big one, or a very old one) averages at approximately 70W.
No, normaly dumb people prefer to cast doubt on perfectly made arguments when they want to sound important.
Those words have a meaning, a quite clear and well define done. Learn those meanings if you want to talk about the subject in question.
You have quite a good point. If syntax weirdeness were a problem, C would have never taken off. Lack of decent I/O is the problem with most languages that are easy to paralelize. It seems that most such languages aren't defined with I/O in mind, and it is easy to imagine why, doing I/O in a paralel environment is very complex.
And there lies the problem. How do you trust a device that you can't touch?
Maybe they were fired because they complained too much that Sony didn't care about security. Or that they upped that complain into the CEO, that preferred the CIO version. Maybe they threatened to make the problem public and their boss didn't like it. Maybe they weren't seen as productive because they kept fixing things the entire day, instead of helping build new things, and were understaffed. Maybe the company didn't like the policies they tried to put in place, so not only didn't accept the policies, but also fired them (this option seems to be quite likely). Maybe they weren't competent enough to put some good security in place, but still dedicated enough to security so that they anoyed people. Or, finally maybe they were justly fired by incompentence.
And THAT explains the breaches.
I'd be quite surprized if sauropodes did need to look for shade in hot days. Finding some could be quite a challenge.
If its metabolism was enough to keep it warm, and it has some mechanism to reduce the metabolism or get ride of the extra heat when it gets too warm, we have a warm blooded creature!!! Now it its metabolism was enough to keep it warm, it does not have some mechanism to slow that metabolism or get ride of the extra heat when it gets too warm, we have a dead creature!!! So, I guess stating that its metabolism can keep it warm is enough here.
Please compare a cold blooded creature (like a snake, for example) that often pass through months without eating and is ok with that, and a warm blooded creature that must eat every week (or even more often). Metabolism seems to be the biggest difference here, altough, IAMN a biologist...
The bad news is that reputation nowadays is something you buy (from the mass media). That saying doesn't work anymore.
Why would anybody care about a liquidity trap in Bitcoin? The monetary politic is fixed, and there isn't anybody able to print it.
To be fair, it is hard to be more expensive than Visa/MC/ACH. Also, one would work on some money that isn't the desired currency if the other party is willing to work such currency. If you can exchange it imediately, why would you refuse a currency that isn't your preferred one (maybe add a small amount for conversion, but not refuse).
I never expected Bitcoin to get where it is, and I don't expect it to go much further. But I was wrong once...
Well, not for throwing your high tech devices into, that is for sure.
It may even have protection against a thermonuclear bomb exploding in the middle of the city, but I doubt the insurer will be able to pay if that happens.
Yeah, there is. It is because it is very expensive to get a license. Anyway, The GP is arguing for automitized flight, there is a reason the biggest airplanes aren't yet fully automatized, that is beause the technology is new, and society still didn't have the time to adapt to it.
In gcc (Debian 4.4.5-8):
Error: cast from 'const int*' to 'int' loses precision
Not at all what I was expecting. It didn't refuse to lose constness (I was expecting that), didn't complain about the & operator aplied to a const (that would be the right behaviour), and didn't work! Amazing. Pedantic and Wall changes nothing, changing i to 'const short' also changes nothing.
That said, that is a problem of the compilers. The standard says the & operator can't apply to a const.
It describes better the current Microsoft than an assimilated person...
Thread safety is quite an important requisite for a general porpouse library. You could already use COW on your code, but there is no good way that I'm aware of to implement it at the std libraries.
Just this one: "You don't see a problem with borrowing an inherently deflationary currency? Deflation makes it harder to repay a loan." Deflation makes interest rate go down, as inflation makes it go up. Unless the deflation is so severe that interest would go negative to compensate, there is no problem. People also aren't able to lend/borrow in a hightly inflationary currency. Also, being able to borrow in a currency isn't a requisite for that currency to be used on transactions.
The other problems are quite real.
Yet, Bitcoin is fiat money. It was created by fiat (of the person that published the algorithms), and has only the value that people assign to it.
The fact that it lacks other characteristics that are correlated with fiat money doesn't make it less so.
How do you know?