How much can you spend in a year as an individual? Simple; your gross income, plus any new debt you take on.
How much debt can be issued to the entire economy in a year? Is it limited to savings? Nope. Banks issue loans against the assets you have. And through the magic of double entry book-keeping, the loan creates a deposit. Reserve requirements don't limit new debt, mainly because banks look to fulfil their requirements from the reserve bank one month after the loans have been created.
How much spending is there in the entire economy? Total income (GDP) plus growth of debt.
How much growth is there in the economy? Well that would be income growth (velocity of GDP) plus acceleration of debt.
Unemployment, asset prices, and economic growth all show a very strong correlation to the acceleration of debt. And the correlation is very strong when debt levels are high.
So why are we in a financial crisis? Well the debt bubble leading up to 2008 slowed down and then reversed. In 2008 there was an absolutely massive deceleration in the level of debt. This triggered an absolutely massive shrink in spending, in the US spending in one year shrank by almost 2 trillion dollars. Since then conditions have improved a bit. The level of debt is still falling, but the acceleration is positive.
To fix the economy, with the least pain possible, we need to keep the velocity of debt negative. With the acceleration level of debt averaging just below zero for around 10-15 years, until the level of debt has drastically reduced. Any sudden drop in the acceleration of debt will indicate a crisis, any jump in the acceleration will indicate a bubble.
Or we need to write off the debts now, which would require a massive coordinated effort from governments to restructure the entire economy. A process that would disadvantage one section of the economy more than another no matter how it was done.
Forcing the user to turn their face around a bit so you can check their features against a 3d model might work. But would be more difficult to implement, and probably more error prone.
There are cases where the system libraries define something as a class when it should have been defined as an interface, perhaps with a default abstract implementation. InputStream / OutputStream spring to mind.
SCTP's a neat protocol. But by itself, it won't help to accelerate HTTP. SDPY is designed to quickly load all of the different resources you'll need to render a web page with a much lower latency. Standard HTTP over SCTP wouldn't have as much of an impact on latency.
storing people's deposits that are not to be loaned out and making loans with deposits that can be loaned out, where the client of the bank is informed that his deposit is partially loaned out but he is making some interest on it
If banks actually worked that way, sure. But they really don't. Banks create a loan and a deposit *at the same time* through the magic of double entry book-keeping.
No thank you. I don't have a phone contract, and I don't have any plans to get one.
Store a cookie of some kind on my PC if you want, and send me an email when I login from somewhere else before allowing access. But don't force me to sign up for a mobile phone plan.
If this demo was waiting for a screen repaint before drawing the next frame (and since there's no flickering it's either doing that or triple buffering). Then if the cpu can paint the screen at 65fps, but your monitor can only do 60fps, then the demo will run at 60fps. However if the cpu can only paint at 55fps, then the demo will actually run at 30fps. eg each frame will be displayed by the monitor for 2 screen refreshes and the demo will take twice as long to run.
That's the point I was trying to make. That if you are waiting for the monitor to paint each frame, a small difference in rendering speed can cause a large difference in fps.
30fps vs 60fps? The speed difference could actually be very minor. It could be simply that the google version just misses a screen refresh and waits for the next one, where the linaro version doesn't. Obviously there's no doubt that it is faster, but a single fps number doesn't give you all the details.
Speaking of shields, I'm involved in a project that is looking at embedding an Arduino type micro-controller into a small cheap android phone. If we can get the project off the ground that is.
The system should allow the train to break into smaller trains, and rejoin into a larger one. If the train is too long, it will need to allow for merging traffic as well as aborted overtaking. But every vehicle needs to be smart enough to take over the lead role.
Just remember that when the money supply shrinks, your debts are worth more.
Some time around 2008, the rate that new loans were being issued plummeted. And the value of existing loans dropped as well through repayments or bankruptcies.
This is the real cause of the problem with the economy. Not that the supply of cash (M0 - M3) is rising, but that the supply of credit money, issued by banks, is shrinking *fast*. The US Fed's recent attempts to "print money" are about 20x too small to touch on the credit money that is being destroyed.
Deflation is nasty, especially when everyone has large debts denominated in that currency. As everyone tries to pay down their debts, the velocity of money shrinks reducing incomes. So in real terms your debt actually increases. The more you pay, the more you owe.
Letting people pay less to access something popular can give you a much larger income stream. How many times has this happened recently with computer games? For example, making Team Fortress 2 "free to play" gave valve a 12x increase in revenue.
I've worked on quite a few large-ish database applications (eg 800 - 2000 tables, some with multi-million rows), and I'd say I'm fluent with SQL. But the thing that annoys me most about SQL, from a maintenance perspective, is how much of the database structure ends up strewn around in your code base. SQL is *not* good at encapsulation.
When a new requirement comes in that should cause you to change some of the primary relationships in your database, you have a look at how much code you'd need to change to do it properly, and end up just hacking in something really ugly instead. Maybe you should be able to use a foreign key, or many-to-many join table relationship, just by using its name (or something like that). Instead, every query must list the entire set of columns involved. And often provide hints to the database engine on which indexes to use first.
And the problem gets much worse if you build your schema "properly" and heavily normalise the structure of everything. Because then any "simple" query easily involves 7 tables. And you probably need to code it into a stored procedure so you can build the data manually in a temporary table, since the database engine can't choose the right indexes and processing order and ends up scanning through millions of records to find the half dozen you actually wanted.
Sure you could write a set of classes to build the SQL query strings for you, so you can encapsulate these details in one place. But then you'll probably end up with an ugly inner-platform that only the original designers really understand and your skills with using it wont translate directly into any other application or language.
I'm not saying the NO-SQL folks have reduced any of the complexity of working with large complicated data sets. But SQL is not the silver bullet you make it out to be either.
At a friends house, they have all their AV equipment in cupboards embedded in the wall. If you need to reach the back of something, you walk around into the corridor and open the cupboard. The same thing could easily work with a rack assuming you allow for ventilation.
The worst offender IMHO is steam pricing. Since on steam the prices are quoted in USD, but are still 30-60% higher. Heck I can buy some steam games over the counter for less than the online price.
I think that optus used to route to blizzards SEA servers via the US. But not all ISP's do. The recent Diablo III open beta highlighted a similar issue with Adam Internet, as an unexpected surge of UDP packets on a weekend, on a previously unknown port didn't play well with their packet prioritisation.
* Of course being omnipotent means there is no curiosity, as God already knows everything... Thus why bother with the first world (assuming that's us) in the first place?
That could be a good reason to build a universe based on probabilities rather than certainties, eg quantum mechanics. That way, even though you may already know the outcome, you can claim that you didn't cause it and didn't interfere where you weren't welcomed.
The browser only downloads the update. The launcher needs the extra permission, (though I'm mainly guessing, I don't really know how it is implemented). This is no worse security than the previous click through UAC. Do you expect every user to verify the contents of each update?
I have heard of an alternative theory; that waves are constantly emitted from everything, and quantum particles probabilistically choose a path to follow based on the strength of the incoming waves, following them back to their source along a single path. The maths is basically the same, but there is no need for entanglement or collapse of wave states.
Correct. In essence there is a cost function that can give a single number for the travel between any two cities. It could be based purely on distance, or you could estimate the physical time / fuel required for each leg. The basic algorithm is the same.
Slashdot Mirror
But their current testing process is copying your web traffic overseas. And is most certainly not opt-in.
How much can you spend in a year as an individual? Simple; your gross income, plus any new debt you take on.
How much debt can be issued to the entire economy in a year? Is it limited to savings? Nope. Banks issue loans against the assets you have. And through the magic of double entry book-keeping, the loan creates a deposit. Reserve requirements don't limit new debt, mainly because banks look to fulfil their requirements from the reserve bank one month after the loans have been created.
How much spending is there in the entire economy? Total income (GDP) plus growth of debt.
How much growth is there in the economy? Well that would be income growth (velocity of GDP) plus acceleration of debt.
Unemployment, asset prices, and economic growth all show a very strong correlation to the acceleration of debt. And the correlation is very strong when debt levels are high.
So why are we in a financial crisis? Well the debt bubble leading up to 2008 slowed down and then reversed. In 2008 there was an absolutely massive deceleration in the level of debt. This triggered an absolutely massive shrink in spending, in the US spending in one year shrank by almost 2 trillion dollars. Since then conditions have improved a bit. The level of debt is still falling, but the acceleration is positive.
To fix the economy, with the least pain possible, we need to keep the velocity of debt negative. With the acceleration level of debt averaging just below zero for around 10-15 years, until the level of debt has drastically reduced. Any sudden drop in the acceleration of debt will indicate a crisis, any jump in the acceleration will indicate a bubble.
Or we need to write off the debts now, which would require a massive coordinated effort from governments to restructure the entire economy. A process that would disadvantage one section of the economy more than another no matter how it was done.
Forcing the user to turn their face around a bit so you can check their features against a 3d model might work. But would be more difficult to implement, and probably more error prone.
There are cases where the system libraries define something as a class when it should have been defined as an interface, perhaps with a default abstract implementation. InputStream / OutputStream spring to mind.
SCTP's a neat protocol. But by itself, it won't help to accelerate HTTP. SDPY is designed to quickly load all of the different resources you'll need to render a web page with a much lower latency. Standard HTTP over SCTP wouldn't have as much of an impact on latency.
storing people's deposits that are not to be loaned out and making loans with deposits that can be loaned out, where the client of the bank is informed that his deposit is partially loaned out but he is making some interest on it
If banks actually worked that way, sure. But they really don't. Banks create a loan and a deposit *at the same time* through the magic of double entry book-keeping.
No thank you. I don't have a phone contract, and I don't have any plans to get one.
Store a cookie of some kind on my PC if you want, and send me an email when I login from somewhere else before allowing access. But don't force me to sign up for a mobile phone plan.
If this demo was waiting for a screen repaint before drawing the next frame (and since there's no flickering it's either doing that or triple buffering). Then if the cpu can paint the screen at 65fps, but your monitor can only do 60fps, then the demo will run at 60fps. However if the cpu can only paint at 55fps, then the demo will actually run at 30fps. eg each frame will be displayed by the monitor for 2 screen refreshes and the demo will take twice as long to run.
That's the point I was trying to make. That if you are waiting for the monitor to paint each frame, a small difference in rendering speed can cause a large difference in fps.
30fps vs 60fps? The speed difference could actually be very minor. It could be simply that the google version just misses a screen refresh and waits for the next one, where the linaro version doesn't. Obviously there's no doubt that it is faster, but a single fps number doesn't give you all the details.
I'd pick Sheldon Cooper ;). The episode almost writes itself...
Speaking of shields, I'm involved in a project that is looking at embedding an Arduino type micro-controller into a small cheap android phone. If we can get the project off the ground that is.
The system should allow the train to break into smaller trains, and rejoin into a larger one. If the train is too long, it will need to allow for merging traffic as well as aborted overtaking. But every vehicle needs to be smart enough to take over the lead role.
Just remember that when the money supply shrinks, your debts are worth more.
Some time around 2008, the rate that new loans were being issued plummeted. And the value of existing loans dropped as well through repayments or bankruptcies.
This is the real cause of the problem with the economy. Not that the supply of cash (M0 - M3) is rising, but that the supply of credit money, issued by banks, is shrinking *fast*. The US Fed's recent attempts to "print money" are about 20x too small to touch on the credit money that is being destroyed.
Deflation is nasty, especially when everyone has large debts denominated in that currency. As everyone tries to pay down their debts, the velocity of money shrinks reducing incomes. So in real terms your debt actually increases. The more you pay, the more you owe.
Do they really?
Letting people pay less to access something popular can give you a much larger income stream. How many times has this happened recently with computer games? For example, making Team Fortress 2 "free to play" gave valve a 12x increase in revenue.
Because you run into the exact same problems with efficiency.
I've worked on quite a few large-ish database applications (eg 800 - 2000 tables, some with multi-million rows), and I'd say I'm fluent with SQL. But the thing that annoys me most about SQL, from a maintenance perspective, is how much of the database structure ends up strewn around in your code base. SQL is *not* good at encapsulation.
When a new requirement comes in that should cause you to change some of the primary relationships in your database, you have a look at how much code you'd need to change to do it properly, and end up just hacking in something really ugly instead. Maybe you should be able to use a foreign key, or many-to-many join table relationship, just by using its name (or something like that). Instead, every query must list the entire set of columns involved. And often provide hints to the database engine on which indexes to use first.
And the problem gets much worse if you build your schema "properly" and heavily normalise the structure of everything. Because then any "simple" query easily involves 7 tables. And you probably need to code it into a stored procedure so you can build the data manually in a temporary table, since the database engine can't choose the right indexes and processing order and ends up scanning through millions of records to find the half dozen you actually wanted.
Sure you could write a set of classes to build the SQL query strings for you, so you can encapsulate these details in one place. But then you'll probably end up with an ugly inner-platform that only the original designers really understand and your skills with using it wont translate directly into any other application or language.
I'm not saying the NO-SQL folks have reduced any of the complexity of working with large complicated data sets. But SQL is not the silver bullet you make it out to be either.
What's the dalvik vm running again? It doesn't run java bytecode either.
At a friends house, they have all their AV equipment in cupboards embedded in the wall. If you need to reach the back of something, you walk around into the corridor and open the cupboard. The same thing could easily work with a rack assuming you allow for ventilation.
The worst offender IMHO is steam pricing. Since on steam the prices are quoted in USD, but are still 30-60% higher. Heck I can buy some steam games over the counter for less than the online price.
I think that optus used to route to blizzards SEA servers via the US. But not all ISP's do. The recent Diablo III open beta highlighted a similar issue with Adam Internet, as an unexpected surge of UDP packets on a weekend, on a previously unknown port didn't play well with their packet prioritisation.
* Of course being omnipotent means there is no curiosity, as God already knows everything... Thus why bother with the first world (assuming that's us) in the first place?
That could be a good reason to build a universe based on probabilities rather than certainties, eg quantum mechanics. That way, even though you may already know the outcome, you can claim that you didn't cause it and didn't interfere where you weren't welcomed.
BTW I don't own a mobile phone, can you add an option to quit bugging me about 2-factor authentication?
The browser only downloads the update. The launcher needs the extra permission, (though I'm mainly guessing, I don't really know how it is implemented). This is no worse security than the previous click through UAC. Do you expect every user to verify the contents of each update?
I have heard of an alternative theory; that waves are constantly emitted from everything, and quantum particles probabilistically choose a path to follow based on the strength of the incoming waves, following them back to their source along a single path. The maths is basically the same, but there is no need for entanglement or collapse of wave states.
Correct. In essence there is a cost function that can give a single number for the travel between any two cities. It could be based purely on distance, or you could estimate the physical time / fuel required for each leg. The basic algorithm is the same.