I have often wondered if the wave function of a single photon can collapse in transit. Creating both the observed red-shift and scattering low energy CMB photons in the process. But I don't have the maths skills to explore the idea properly.
Personally, I think we need a user level API standard that has those guarantee's. This would most likely contain a wrapper around the POSIX compliant API, but may use a different approach for different filesystems that provide different guarantee's.
How do you spider the internet, if you are only checking headers. The whole point of a spider is that you recursively follow all the links returned from each page.
If you do throttle, do it by tweaking the QOS not by a hard rate limit. I'd suggest raising the QOS of some known time sensitive protocols (VOIP / online gaming...), and lowering the QOS of the customers who download the most in a given period. That way your bandwidth hogs can still flood your pipe and use all the available bandwidth, but they won't impact other customers.
God damn it. It's about time we had application level control of file system transactions, so a commit to the FS must either completely happen or be completely rolled back. With the option of a soft checkpoint, ie the application may or may not care if the changes are actually on disk, provided they are rolled back in the event of a power failure.
Ah, that nasty anti-pattern. Definitely not a good model.
If you need to store data that you can't define at design time, you're still better off creating an actual table, or set of tables. Yes it can make the rest of the application that references these values more complex, but it pays off in the long run.
Another nasty anti-pattern we have to deal with is the compound value stored in a single column. The worst example I've seen involves storing XML strings to define the state of an object. The only reliable way to manipulate the XML is to serialise it to a class, modify the class properties and serialise it back again. Nasty nasty stuff. You can't report on it, you can't write simple update statements to fix something.
Yeah, and noone seems to detect the sarcasm.... If you're handing out gift cards, you're handing out money. You'd better be sure it can't be duplicated. Either apple have built an algorithm that is simple to guess, or the activation checks were done client side and someone stepped through the code.
The DRM on DVD's was initially thought to be hard to break. But the lock on the safe was designed internally and eventually found to be vulnerable to a pick gun. You didn't need to find the key in the room, since a tool could be built that could push the pins in the lock to the right position in a matter of seconds.
With more modern DRM, eg AACS on HD-DVD's and BlueRay players. They've actually consulted with the best safe builders and used standard components to build it. The lock on the safe isn't vulnerable. You could be sitting there trying random keys for your entire life and you wont find one. They've even built a second smaller safe in the room to store the key. And this safe can be opened by a number of keys that each guard (software or hardware player) has on their belt. The guards keys, and the key in the smaller safe can be replaced as new contents are stored in the main safe. So at best we now face a continual arms race of new keys being issued and discovered.
Alright I think I've pushed that as far as I can...
I think you are vastly underestimating the JIT engines of Chrome and FF. While these JIT engines still have a way to go, I would expect the execution speed of Javascript to approach the performance of other modern virtual machines like the JVM.
What really annoys me in some RDBMS implementations is that NULL = NULL is false. So if you have a variable that might be NULL and you want to find all the rows that match the variable you have to test for NULL values separately.
Nope, it was Irving Fisher's "The Debt-Deflation Theory of Great Depressions" I was trying to allude to. "the more debtors pay, the more they owe. The more the economic boat tips, the more it tends to tip. It is not tending to right itself, but is capsizing" (Fisher 1933)
My point was that as the whole economy focuses on repaying debt, unemployment rises and collective incomes drop. I didn't mean that the debt goes up when measured in dollars, but that the debt goes up when compared against our dwindling income.
Correction: most of today's economic recession was caused by economists providing flawed models of the economy that ignored excessive debt and encouraged wild asset speculation on borrowed money.
Banks wouldn't have lent the money if they knew the real long term risk, but their models were completely broken.
This debt bubble has been building for the last 50 years. After each recession, the worst effected parties stopped borrowing as much. Governments and banks then kick started the economy again by finding another sucker to lend money to.
The problem is, the world has run out of suckers willing to foot the bill.
Bingo, I was going to post basically the same thing once I read the summary. Reducing salaries will not save jobs. We are in the beginning stages of a debt deflation cycle.
Everyone is trying to pay off their debts, so they are not spending as much as they used to, this started in early / mid 2008. As a result of that there is less money flowing around the economy. So there is less money to pay in salaries, and we started to see massive layoffs in late 2008 / early 2009. So employees will have less money to pay off their debts... and the cycle continues.
This leads to the paradox that the more everyone tries to pay off their debts, the higher the debt becomes in real terms (eg in relation to inflation / deflation adjusted incomes).
Slashdot Mirror
So I pick up this meme and throw it to Who?
On that topic, here's some required reading.
I have often wondered if the wave function of a single photon can collapse in transit. Creating both the observed red-shift and scattering low energy CMB photons in the process. But I don't have the maths skills to explore the idea properly.
Here's the wikipedia page about the case. I think the original source of the news is in German though.
Christ, you guys are merciless. Next you'll be wanting to nail him to a tree or something.
Jesus, I come here for the intellectual discussion. I didn't expect this kind of Spanish Inquisition.
Hmmmm... Are browsers fast enough now to run something like dosbox ported to javascript / dhtml...
Personally, I think we need a user level API standard that has those guarantee's. This would most likely contain a wrapper around the POSIX compliant API, but may use a different approach for different filesystems that provide different guarantee's.
How do you spider the internet, if you are only checking headers. The whole point of a spider is that you recursively follow all the links returned from each page.
If you do throttle, do it by tweaking the QOS not by a hard rate limit. I'd suggest raising the QOS of some known time sensitive protocols (VOIP / online gaming...), and lowering the QOS of the customers who download the most in a given period. That way your bandwidth hogs can still flood your pipe and use all the available bandwidth, but they won't impact other customers.
Yeah, it's a tough problem.
While moving config to a database would help, it adds a dependency on the database driver and GUI wrapper if you ever want to change something.
I guess what I was thinking of could be done using POSIX semantics with a journal, and you could write a friendly wrapper around it.
It would be nice to have an optional kernel interface implemented in the filesystem, falling back to POSIX semantics when it isn't supported.
God damn it. It's about time we had application level control of file system transactions, so a commit to the FS must either completely happen or be completely rolled back. With the option of a soft checkpoint, ie the application may or may not care if the changes are actually on disk, provided they are rolled back in the event of a power failure.
Ah, that nasty anti-pattern. Definitely not a good model.
If you need to store data that you can't define at design time, you're still better off creating an actual table, or set of tables. Yes it can make the rest of the application that references these values more complex, but it pays off in the long run.
Another nasty anti-pattern we have to deal with is the compound value stored in a single column. The worst example I've seen involves storing XML strings to define the state of an object. The only reliable way to manipulate the XML is to serialise it to a class, modify the class properties and serialise it back again. Nasty nasty stuff. You can't report on it, you can't write simple update statements to fix something.
Yeah, and noone seems to detect the sarcasm.... If you're handing out gift cards, you're handing out money. You'd better be sure it can't be duplicated. Either apple have built an algorithm that is simple to guess, or the activation checks were done client side and someone stepped through the code.
We're at the start of Depression #2
Nah, this is at least #4. Just because you don't remember 1837 or 1873 doesn't mean they didn't happen.
Why prosecute? If you can identify the illegitimate cards, you can revoke the license to all the downloaded music. Isn't this what DRM is for?
I wouldn't call GPGPU a new term. There's been heaps of stories here about it.
Extending still further...
The DRM on DVD's was initially thought to be hard to break. But the lock on the safe was designed internally and eventually found to be vulnerable to a pick gun. You didn't need to find the key in the room, since a tool could be built that could push the pins in the lock to the right position in a matter of seconds.
With more modern DRM, eg AACS on HD-DVD's and BlueRay players. They've actually consulted with the best safe builders and used standard components to build it. The lock on the safe isn't vulnerable. You could be sitting there trying random keys for your entire life and you wont find one. They've even built a second smaller safe in the room to store the key. And this safe can be opened by a number of keys that each guard (software or hardware player) has on their belt. The guards keys, and the key in the smaller safe can be replaced as new contents are stored in the main safe. So at best we now face a continual arms race of new keys being issued and discovered.
Alright I think I've pushed that as far as I can...
Which is also holding back DIY PVR adoption since there is no legal source of TV show timetables.
I think you are vastly underestimating the JIT engines of Chrome and FF. While these JIT engines still have a way to go, I would expect the execution speed of Javascript to approach the performance of other modern virtual machines like the JVM.
What really annoys me in some RDBMS implementations is that NULL = NULL is false. So if you have a variable that might be NULL and you want to find all the rows that match the variable you have to test for NULL values separately.
Or just a bug with slashcode. We all know how often this code base is screwed around with.
Nope, it was Irving Fisher's "The Debt-Deflation Theory of Great Depressions" I was trying to allude to. "the more debtors pay, the more they owe. The more the economic boat tips, the more it tends to tip. It is not tending to right itself, but is capsizing" (Fisher 1933)
My point was that as the whole economy focuses on repaying debt, unemployment rises and collective incomes drop. I didn't mean that the debt goes up when measured in dollars, but that the debt goes up when compared against our dwindling income.
Correction: most of today's economic recession was caused by economists providing flawed models of the economy that ignored excessive debt and encouraged wild asset speculation on borrowed money.
Banks wouldn't have lent the money if they knew the real long term risk, but their models were completely broken.
This debt bubble has been building for the last 50 years. After each recession, the worst effected parties stopped borrowing as much. Governments and banks then kick started the economy again by finding another sucker to lend money to.
The problem is, the world has run out of suckers willing to foot the bill.
Bingo, I was going to post basically the same thing once I read the summary. Reducing salaries will not save jobs. We are in the beginning stages of a debt deflation cycle.
Everyone is trying to pay off their debts, so they are not spending as much as they used to, this started in early / mid 2008. As a result of that there is less money flowing around the economy. So there is less money to pay in salaries, and we started to see massive layoffs in late 2008 / early 2009. So employees will have less money to pay off their debts... and the cycle continues.
This leads to the paradox that the more everyone tries to pay off their debts, the higher the debt becomes in real terms (eg in relation to inflation / deflation adjusted incomes).