I did mean to suggest that I don't understand the common definition of 0.999...=1, I understand the notation. It was this very definition of 1/3 = 0.333... I was arguing against because I believe that 0.333... with an infinite number of 3's is a useless concept. The action of writing out 1/3 in decimal notation is a process, as is the process of writing out the first 1 trillion decimal digits to pi. Both are numbers that decimal notation cannot accurately represent as neither number can be expressed precisely as a fraction with denominator divisible by only 2's and 5's. I was simply stating my belief that it is misleading to simply say that these digits continue to infinity, instead of leaving an explicit remainder or error bounds information from such a representation.
I believe the worst problem with recurring decimal notation is dropping the implied remainder. My point was that the expansion of 1/3 to any finite number of decimal points always has an implied fractional remainder that is usually not written down. Each step of the expansion process to another digit reduces but does not eliminate the remainder. Therefore, even if you continue this expansion to infinity, the remainder in your calculation never disappears. Even if its limit approaches zero, it is *not* zero.
I prefer to think that 1/3 expressed as a decimal is *not* a number, but a description of a process that in some cases can only calculate an approximate value. For example when you expand the answer to 2 decimal places you get; 1/3 = 0.33 + 0.01 / 3. The notation 0.333... (usually with a dot above the last 3) suggests that you expand the answer to an infinite number of places, but even this will have a left over infinitesimal fraction.
The problem here is that decimal notation can only express the precise values of fractions if their denominator is divisible by only 2 and 5. If the denominator has any other prime factors, the value can only be approximated.
And that's not counting business domain knowledge. Knowing your employer's business inside out can be more valuable than knowledge of any one programming language.
While Peep Wireless seems to be a scam, Serval's Batphone shows some promise. Their working prototype was a port/hack of asterisk, batmand, sipdroid and their own Distributed Numbering Architecture software all running on an Android phone. Also all their source code has been released under the GPL.
If you separate the UI for the two main functions of the status bar, "where does this link go" and "I'm still loading something" (which doesn't need that much room). Just put the link url in the address bar in a lighter shade of grey.
I was sharing a connection with a friend once who was throttling my upload bandwidth in an attempt at fairness. Trying to run something like bittorrent would fill all the buffers in my PC, his router and his modem, adding 1.5 seconds of latency to the link (I used to ping the host on the other end of the modem to confirm it).
He's using small probes vs the kindles much larger surface area sockets and he's posing for the camera. Plus would a sweaty palm on the outside of the case make any difference?
Meanwhile, the page has been updated;
There's been a stunning amount of feedback from the slashdot audience on the original post. Seems we need to go test some things. Clearly, metal is getting exposed, and making contact inside the Kindle. Which circuit is being closed is less clear. More testing is needed. We'll get back to you... Thanks.
If you are a programmer, BE A PROGRAMMER and manage the pointers and memory allocations yourself
I look at the problem like this;
I've solved a fair number of sudoku puzzles in my time. You build a mental set of rules and patterns you look for, and you repeatedly apply them to the remaining squares. On a really hard puzzle you'll often reach a point where you get stuck. You keep scanning for patterns in the remaining numbers but you just can't see the one clue that causes the rest of the solution to fall out.
But a computer program? Once you tell it how to find something, it never forgets to apply a rule. You may think you can keep following a small set of simple rules while building a complex software solution. But chances are pretty good that you'll miss something. If you can hand a task like memory management to a software solution, there's a good chance it will do a better job at tracking memory than you will.
Not necessarily. With properly implemented public/private crypto you can make it basically impossible to hijack. It might still be possible to disrupt it though.
I can't tell you how many programming horror stories have started with a marketer or sales person receiving a fat bonus from making a sale. Knowing how to bring money into a company is certainly essential to the running of a business, but it can easily give you a very warped picture of your place in the world.
I said something to this effect yesterday. You'd generate a private key, hand your public key to a trusted certificate authority who would issue you a name then sign your key and domain name. You then use your key and signature to sign your current DNS records and publish them in a p2p distributed hash table. You could use the same key, or another key published in the same way via DNS, to initiate an SSL connection when the user connects to you. That way the user can be certain they are connecting to the correct host.
While you could also allow self signed DNS records in this model, or build a "web of trust" by signing each others keys. This could be a lot harder to trust, end to end, when you connect to a name you've never tried before.
There's no reason for DNS resolution to go through any centralised server. Use a distributed hash table to publish and retrieve records and sign them. Of course you'd still need a central authority to issue and sign certificates.
The last day of the Julian calendar was Thursday, 4 October 1582 and this was followed by the first day of the Gregorian calendar, Friday, 15 October 1582
Britain and the British Empire (including the eastern part of what is now the United States) adopted the Gregorian calendar in 1752 by which time it was necessary to correct by 11 days. Wednesday, 2 September 1752 was followed by Thursday, 14 September 1752
Um, no. That may be true now, but that's a fairly recent change. It wasn't that long ago that new games targeted bleeding edge hardware at the time of release. I think roughly the release of Half-life 2 & Doom 3 were the turning point. That's the last time I remember people planning a hardware upgrade specifically to coincide with a game purchase.
You are confusing a stock (debt) with a flow (income). It is quite possible for money to circulate around the economy more than once in a year. Assuming bankers spend the money they make from interest, it is entirely possible for debt's and interest payments to reach an equilibrium in the economy without the continual creation of new debt. See the video from Why credit money fails linked earlier for more details and simulations of such a working economy. Of course it never works in practice because bankers are greedy.
... I highly recommend people read up on the work of Steve Keen.
a professional economist and a long time critic of conventional economic thought. As well as attacking mainstream thought in Debunking Economics, I am also developing an alternative dynamic approach to economic modelling. The key issue I am tackling here is the prospect for a debt-deflation on the back of the enormous debts accumulated in Australia, and our very low rate of inflation
I did mean to suggest that I don't understand the common definition of 0.999...=1, I understand the notation. It was this very definition of 1/3 = 0.333... I was arguing against because I believe that 0.333... with an infinite number of 3's is a useless concept. The action of writing out 1/3 in decimal notation is a process, as is the process of writing out the first 1 trillion decimal digits to pi. Both are numbers that decimal notation cannot accurately represent as neither number can be expressed precisely as a fraction with denominator divisible by only 2's and 5's. I was simply stating my belief that it is misleading to simply say that these digits continue to infinity, instead of leaving an explicit remainder or error bounds information from such a representation.
I believe the worst problem with recurring decimal notation is dropping the implied remainder. My point was that the expansion of 1/3 to any finite number of decimal points always has an implied fractional remainder that is usually not written down. Each step of the expansion process to another digit reduces but does not eliminate the remainder. Therefore, even if you continue this expansion to infinity, the remainder in your calculation never disappears. Even if its limit approaches zero, it is *not* zero.
I prefer to think that 1/3 expressed as a decimal is *not* a number, but a description of a process that in some cases can only calculate an approximate value. For example when you expand the answer to 2 decimal places you get; 1/3 = 0.33 + 0.01 / 3. The notation 0.333... (usually with a dot above the last 3) suggests that you expand the answer to an infinite number of places, but even this will have a left over infinitesimal fraction.
The problem here is that decimal notation can only express the precise values of fractions if their denominator is divisible by only 2 and 5. If the denominator has any other prime factors, the value can only be approximated.
And that's not counting business domain knowledge. Knowing your employer's business inside out can be more valuable than knowledge of any one programming language.
Jim_Higgins posted a column that cited the columnist but failed to cite the original LVRJ article
Huh? The url is right there at the top of his post, it's just been shortened;
JOHN L. SMITH: Somehow, patting down disabled, elderly improves security
http://tinyurl.com/2a5y2ho
But they attach interest to each dollar they create. That means there are not enough total dollars in the system to pay back all of the debt
You are confusing a stock with a flow. Money circulates the economy many times in a year, making it perfectly possible to repay debt & interest.
While Peep Wireless seems to be a scam, Serval's Batphone shows some promise. Their working prototype was a port/hack of asterisk, batmand, sipdroid and their own Distributed Numbering Architecture software all running on an Android phone. Also all their source code has been released under the GPL.
When it clutters the options window, or the menu's, yes it is.
If you separate the UI for the two main functions of the status bar, "where does this link go" and "I'm still loading something" (which doesn't need that much room). Just put the link url in the address bar in a lighter shade of grey.
I was sharing a connection with a friend once who was throttling my upload bandwidth in an attempt at fairness. Trying to run something like bittorrent would fill all the buffers in my PC, his router and his modem, adding 1.5 seconds of latency to the link (I used to ping the host on the other end of the modem to confirm it).
He's using small probes vs the kindles much larger surface area sockets and he's posing for the camera. Plus would a sweaty palm on the outside of the case make any difference?
Meanwhile, the page has been updated;
There's been a stunning amount of feedback from the slashdot audience on the original post. Seems we need to go test some things. Clearly, metal is getting exposed, and making contact inside the Kindle. Which circuit is being closed is less clear. More testing is needed. We'll get back to you... Thanks.
what I'm getting now would cost about $20 more a month
What you're getting now is crap. Adding $20 a month would, in this instance, get you something *better*.
If you are a programmer, BE A PROGRAMMER and manage the pointers and memory allocations yourself
I look at the problem like this;
I've solved a fair number of sudoku puzzles in my time. You build a mental set of rules and patterns you look for, and you repeatedly apply them to the remaining squares. On a really hard puzzle you'll often reach a point where you get stuck. You keep scanning for patterns in the remaining numbers but you just can't see the one clue that causes the rest of the solution to fall out.
But a computer program? Once you tell it how to find something, it never forgets to apply a rule. You may think you can keep following a small set of simple rules while building a complex software solution. But chances are pretty good that you'll miss something. If you can hand a task like memory management to a software solution, there's a good chance it will do a better job at tracking memory than you will.
Not necessarily. With properly implemented public/private crypto you can make it basically impossible to hijack. It might still be possible to disrupt it though.
I can't tell you how many programming horror stories have started with a marketer or sales person receiving a fat bonus from making a sale. Knowing how to bring money into a company is certainly essential to the running of a business, but it can easily give you a very warped picture of your place in the world.
Capitalism doesn't work when we live off credit. When we mainly extend credit to those speculating on the prices of existing assets.
I said something to this effect yesterday. You'd generate a private key, hand your public key to a trusted certificate authority who would issue you a name then sign your key and domain name. You then use your key and signature to sign your current DNS records and publish them in a p2p distributed hash table. You could use the same key, or another key published in the same way via DNS, to initiate an SSL connection when the user connects to you. That way the user can be certain they are connecting to the correct host.
While you could also allow self signed DNS records in this model, or build a "web of trust" by signing each others keys. This could be a lot harder to trust, end to end, when you connect to a name you've never tried before.
There's no reason for DNS resolution to go through any centralised server. Use a distributed hash table to publish and retrieve records and sign them. Of course you'd still need a central authority to issue and sign certificates.
The last day of the Julian calendar was Thursday, 4 October 1582 and this was followed by the first day of the Gregorian calendar, Friday, 15 October 1582
Britain and the British Empire (including the eastern part of what is now the United States) adopted the Gregorian calendar in 1752 by which time it was necessary to correct by 11 days. Wednesday, 2 September 1752 was followed by Thursday, 14 September 1752
Debt's that cant be repaid, wont be repaid. The only question is how you intend not to pay them.
Um, no. That may be true now, but that's a fairly recent change. It wasn't that long ago that new games targeted bleeding edge hardware at the time of release. I think roughly the release of Half-life 2 & Doom 3 were the turning point. That's the last time I remember people planning a hardware upgrade specifically to coincide with a game purchase.
He's one of 12 economists recognised with predicting the crisis, who had a model to back up their claim.
You are confusing a stock (debt) with a flow (income). It is quite possible for money to circulate around the economy more than once in a year. Assuming bankers spend the money they make from interest, it is entirely possible for debt's and interest payments to reach an equilibrium in the economy without the continual creation of new debt. See the video from Why credit money fails linked earlier for more details and simulations of such a working economy. Of course it never works in practice because bankers are greedy.
a professional economist and a long time critic of conventional economic thought. As well as attacking mainstream thought in Debunking Economics, I am also developing an alternative dynamic approach to economic modelling. The key issue I am tackling here is the prospect for a debt-deflation on the back of the enormous debts accumulated in Australia, and our very low rate of inflation
This quote from the West wing seems appropriate...