So after the decade is up, we'll be stuck with the nodes and no clear way to upgrade everyone to FTTH. For an additional 20% now we could have a network that can deliver all of our demands for bandwidth for the next century. If you're going to spend billions, do it right.
I've only managed to stick my head into a much smaller quiet space for a few seconds. The silence hits you like the chiming of Old Tom at Unseen University.
Unlocking the bootloader is a direct path to getting an su binary. But android's history is littered with linux exploits that have been automated to give you elevated privileges and install su. Without unlocking the bootloader first, or installing a different ROM.
And all through the 1930's things were getting better. Until the next crash that is, when things were suddenly worse than ever. But don't worry everything is getting better now...
In South Australia, you can't get a thin plastic bag at the checkout at all. But you can buy a much tougher plastic bag for 20c or a canvas(-ish) bag for $1.00.
It took a while to remember to take our reusable bags with us when we go shopping, but we've got so many of them now it just seems normal. Every time I travel interstate, I'm surprised by the stores handing out those nasty thin fragile bags.
Curved LED displays are possible. There's a few demo mockup's of watch form factor displays out there. It's still going to be tricky to build a lens system to project the image as if it is further away.
Bitcoins aren't exactly like dollar notes though. Each transaction can combine any number of coins, or split them up into tiny pieces. Sure you can trace the path of all of those pieces as they are combined and split. But would you taint 100 coins because it was combined with 0.5 that was tainted from some other source?
If I connect to a web server and request a html page, using the published HTTP standard, without any tricks to bypass user authentication. And the server obligingly gives me the content I asked for, have I invaded the privacy of the server? Have I trespassed?
Of course not.
How is using an established P2P standard to request content from your home PC any different?
Mining coins is based on probability. The block length is designed to grow at a fixed rate, and periodically the number of coins mined per block will halve until the number mined drops to zero. The supply is designed to be limited. The production of coins is designed to be controlled. One miner successfully mining a coin, deprives someone else of the possibility of mining it. All miners have to share the coins that are being produced.
Every individual miner judges the odds of getting a bitcoin against the energy they expend and make their own decision about whether to turn their mining hardware on or off. But not everyone who wants bitcoins is a miner, and not every miner has access to the same efficiency hardware. It's easy for the price someone is willing to pay to be significantly different to the production cost of a coin.
Though it is likely that the production cost will follow, or be slightly above the exchange value. The causal relationship is the other way around. Miners will turn their rigs on and off based on the price. The price is not set based on the energy consumed.
It's possible for the electricity actually used to greatly exceed the value of the coins produced. It's possible for miners to produce coins for less electricity than the current exchange value, it certainly happened a lot when GPU mining started to take off.
You cant assume that the exchange value and production cost are in equilibrium. A coin's exchange value is exactly what someone else is willing to give you in exchange. It's the very difference between production cost and exchange value that drives the gold rush fever related to mining. But with bitcoins, the more people who join, the lower the share that each miner can produce.
Plus the current rate that new coins are being created is insignificant when compared to the number of coins being traded.
Firstly, there is a limit to the rate of newly mined bitcoins. The total number of created bitcoins will approach an upper limit and never pass it. If more people want to buy them, they have to be willing to offer more value than anyone else to get them. Since the supply is limited, if the demand goes up, so should the exchange value.
Secondly, bitcoins have absolutely no inherent value. You can't create anything with them directly. You might say that their implicit scarcity gives them some value in the same way that gold, silver and platinum are considered to be valuable, but at least those metals have some utility value as well.
So the only sense that bitcoins have any value at all is in exchanging them. People keep trying to trade bitcoins for more traditional currencies. It's this exchange that we use to measure the value of bitcoins, and it is mainly speculation that drives people to trade them. If someone wants to offer a million dollars for a single bitcoin, then that is by definition the current exchange value.
The difference between the cost of electricity to mine coins, and their current exchange value will have an impact on the willingness of bitcoin miners to run their rigs. But the production cost of bitcoins has no direct impact on the exchange value of existing coins. Instead I'd suggest that the relationship is the other way around. If the exchange value is higher than the production cost, more people would be encouraged to join the mining operation and vice versa.
Clang includes a number of compilation flags that can be used to make sure, or at least as sure as it can, that your code never hits any undefined behaviour at run time.
But normally, yes the compiler may change the behaviour of your application if you are depending on undefined behaviour.
"What every C programmer should know about undefined behaviour" (part 3, see links for first 2 parts).
For example, overflows of unsigned values is undefined behaviour in the C standard. Compilers can make decisions like using an instruction that traps on overflow if it would execute faster, or if that is the only operator available. Since overflowing might trap, and thus cause undefined behaviour, the compiler may assume that the programmer didn't intend for that to ever happen. Therefore this test will always evaluate to true, this code block is dead and can be eliminated.
This is why there are a number of compilation optimisations that gcc can perform, but which are disabled when building the linux kernel. With those optimisations, almost every memory address overflow test would be eliminated.
Though a capacitor inside a CPU may be able to use it's stored energy more efficiently. Or cut off battery / mains power and run from the capacitor for a while during a sleep state.
Charge per unit plans, that don't place any barriers to excessive usage, and unexpected bills, inevitably backfire. One of those least-consuming users will install something, or their kid will, and they'll be facing an unexpectedly huge bill at the end of the month.
This happened many times in Australia in the early days of broadband. In response the ISP's all set up "unlimited" plans, which have a fixed limit of usage per month. After you hit your quota they throttle your connection back to modem-ish speeds to prevent you from using too much more bandwidth. Without cutting you off completely. You may then have the option of paying for another unit of bandwidth, or bumping your monthly plan permanently.
Without onion routing, this VPN solution will expose your social graph to NSA or servers run by other governments operating on the network, one of the key things they are interested in collecting.
Blocking access to something encourages an arms race to bypass the filter. I'd be more concerned about governments that allow you access, but monitor what you are doing and who you are talking to.
Right.... with such details as "autoSpaceLikeWord95, footnoteLayoutLikeWW8, lineWrapLikeWord6,...". Down that path, any competitor must conform to the way Office already does things, with all of the quirks and work arounds that have been built into it over it's lifetime.
That's the wrong way around, and not what I said. Get all the authors of competing office apps in a room to hash out an interchange format, similar to the HTML standards process, with a core grammer that can be used with clearly defined rules to render any document in the same standard way.
Importing a legacy format should involve translating it's quirks into a standard representation. It should not force every document renderer to re-implement each of those quirks in their renderer.
Office is such a complicated beast that no-one can reverse engineer.doc /.docx perfectly. Those formats represent decades of continual minor changes and work-around's as the requirements have changed. This isn't like supporting standards compliant HTML5. Properly documenting the existing doc format is futile, as the only complete specification is the office source code itself.
The only way I can see to get out of this mess is to specify a common document interchange format, and force Microsoft to support it as their default file format.
And then you add integration with all of the 3rd party legacy systems on the back end..., That level of scalability testing is possible, but unlikely. It demands a test system that perfectly mirrors the production system. And I mean perfectly, down to the wiring, switches and routers. Then you have to model your user behaviour accurately, which is difficult for a system that doesn't have any real users yet.
If you can't build such a test system, or your tests don't reflect the typical actions of your users, something could slip through the cracks. If your tests with 100,000 users on one server, that doesn't mean that production will work with 5 million users on 50 servers.
Slashdot Mirror
That $29 has a whole bunch of assumptions...
So after the decade is up, we'll be stuck with the nodes and no clear way to upgrade everyone to FTTH. For an additional 20% now we could have a network that can deliver all of our demands for bandwidth for the next century. If you're going to spend billions, do it right.
I've only managed to stick my head into a much smaller quiet space for a few seconds. The silence hits you like the chiming of Old Tom at Unseen University.
Or so I've heard...
Unlocking the bootloader is a direct path to getting an su binary. But android's history is littered with linux exploits that have been automated to give you elevated privileges and install su. Without unlocking the bootloader first, or installing a different ROM.
And all through the 1930's things were getting better. Until the next crash that is, when things were suddenly worse than ever. But don't worry everything is getting better now...
Though we are buying more plastic bin liners...
In South Australia, you can't get a thin plastic bag at the checkout at all. But you can buy a much tougher plastic bag for 20c or a canvas(-ish) bag for $1.00.
It took a while to remember to take our reusable bags with us when we go shopping, but we've got so many of them now it just seems normal. Every time I travel interstate, I'm surprised by the stores handing out those nasty thin fragile bags.
Curved LED displays are possible. There's a few demo mockup's of watch form factor displays out there. It's still going to be tricky to build a lens system to project the image as if it is further away.
Add an impossible captcha?
Bitcoins aren't exactly like dollar notes though. Each transaction can combine any number of coins, or split them up into tiny pieces. Sure you can trace the path of all of those pieces as they are combined and split. But would you taint 100 coins because it was combined with 0.5 that was tainted from some other source?
If I connect to a web server and request a html page, using the published HTTP standard, without any tricks to bypass user authentication. And the server obligingly gives me the content I asked for, have I invaded the privacy of the server? Have I trespassed?
Of course not.
How is using an established P2P standard to request content from your home PC any different?
What wifi really needs is per packet rate & power control, and for clients to select access points based on the reported QBSS channel utilisation instead of just using rssi measurements.
Mining coins is based on probability. The block length is designed to grow at a fixed rate, and periodically the number of coins mined per block will halve until the number mined drops to zero. The supply is designed to be limited. The production of coins is designed to be controlled. One miner successfully mining a coin, deprives someone else of the possibility of mining it. All miners have to share the coins that are being produced.
Every individual miner judges the odds of getting a bitcoin against the energy they expend and make their own decision about whether to turn their mining hardware on or off. But not everyone who wants bitcoins is a miner, and not every miner has access to the same efficiency hardware. It's easy for the price someone is willing to pay to be significantly different to the production cost of a coin.
Though it is likely that the production cost will follow, or be slightly above the exchange value. The causal relationship is the other way around. Miners will turn their rigs on and off based on the price. The price is not set based on the energy consumed.
It's possible for the electricity actually used to greatly exceed the value of the coins produced. It's possible for miners to produce coins for less electricity than the current exchange value, it certainly happened a lot when GPU mining started to take off.
You cant assume that the exchange value and production cost are in equilibrium. A coin's exchange value is exactly what someone else is willing to give you in exchange. It's the very difference between production cost and exchange value that drives the gold rush fever related to mining. But with bitcoins, the more people who join, the lower the share that each miner can produce.
Plus the current rate that new coins are being created is insignificant when compared to the number of coins being traded.
Seriously? No, you're totally and utterly wrong.
Firstly, there is a limit to the rate of newly mined bitcoins. The total number of created bitcoins will approach an upper limit and never pass it. If more people want to buy them, they have to be willing to offer more value than anyone else to get them. Since the supply is limited, if the demand goes up, so should the exchange value.
Secondly, bitcoins have absolutely no inherent value. You can't create anything with them directly. You might say that their implicit scarcity gives them some value in the same way that gold, silver and platinum are considered to be valuable, but at least those metals have some utility value as well.
So the only sense that bitcoins have any value at all is in exchanging them. People keep trying to trade bitcoins for more traditional currencies. It's this exchange that we use to measure the value of bitcoins, and it is mainly speculation that drives people to trade them. If someone wants to offer a million dollars for a single bitcoin, then that is by definition the current exchange value.
The difference between the cost of electricity to mine coins, and their current exchange value will have an impact on the willingness of bitcoin miners to run their rigs. But the production cost of bitcoins has no direct impact on the exchange value of existing coins. Instead I'd suggest that the relationship is the other way around. If the exchange value is higher than the production cost, more people would be encouraged to join the mining operation and vice versa.
And for extra credit, keep patching 4.0 with bug fixes after 4.1 is released.
Clang includes a number of compilation flags that can be used to make sure, or at least as sure as it can, that your code never hits any undefined behaviour at run time.
But normally, yes the compiler may change the behaviour of your application if you are depending on undefined behaviour.
"What every C programmer should know about undefined behaviour" (part 3, see links for first 2 parts).
For example, overflows of unsigned values is undefined behaviour in the C standard. Compilers can make decisions like using an instruction that traps on overflow if it would execute faster, or if that is the only operator available. Since overflowing might trap, and thus cause undefined behaviour, the compiler may assume that the programmer didn't intend for that to ever happen. Therefore this test will always evaluate to true, this code block is dead and can be eliminated.
This is why there are a number of compilation optimisations that gcc can perform, but which are disabled when building the linux kernel. With those optimisations, almost every memory address overflow test would be eliminated.
I'd say that the transition from bad news to good news usually happens at a single level of management.
Though a capacitor inside a CPU may be able to use it's stored energy more efficiently. Or cut off battery / mains power and run from the capacitor for a while during a sleep state.
Charge per unit plans, that don't place any barriers to excessive usage, and unexpected bills, inevitably backfire. One of those least-consuming users will install something, or their kid will, and they'll be facing an unexpectedly huge bill at the end of the month.
This happened many times in Australia in the early days of broadband. In response the ISP's all set up "unlimited" plans, which have a fixed limit of usage per month. After you hit your quota they throttle your connection back to modem-ish speeds to prevent you from using too much more bandwidth. Without cutting you off completely. You may then have the option of paying for another unit of bandwidth, or bumping your monthly plan permanently.
Without onion routing, this VPN solution will expose your social graph to NSA or servers run by other governments operating on the network, one of the key things they are interested in collecting.
Blocking access to something encourages an arms race to bypass the filter. I'd be more concerned about governments that allow you access, but monitor what you are doing and who you are talking to.
"SMARS is an automated, high speed, algorithmic router that sends orders into the market for execution"
All "High Frequency Trading" is by definition "Algorithmic trading", though the reverse doesn't necessarily hold.
Right.... with such details as "autoSpaceLikeWord95, footnoteLayoutLikeWW8, lineWrapLikeWord6, ...". Down that path, any competitor must conform to the way Office already does things, with all of the quirks and work arounds that have been built into it over it's lifetime.
That's the wrong way around, and not what I said. Get all the authors of competing office apps in a room to hash out an interchange format, similar to the HTML standards process, with a core grammer that can be used with clearly defined rules to render any document in the same standard way.
Importing a legacy format should involve translating it's quirks into a standard representation. It should not force every document renderer to re-implement each of those quirks in their renderer.
Office is such a complicated beast that no-one can reverse engineer .doc / .docx perfectly. Those formats represent decades of continual minor changes and work-around's as the requirements have changed. This isn't like supporting standards compliant HTML5. Properly documenting the existing doc format is futile, as the only complete specification is the office source code itself.
The only way I can see to get out of this mess is to specify a common document interchange format, and force Microsoft to support it as their default file format.
And then you add integration with all of the 3rd party legacy systems on the back end..., That level of scalability testing is possible, but unlikely. It demands a test system that perfectly mirrors the production system. And I mean perfectly, down to the wiring, switches and routers. Then you have to model your user behaviour accurately, which is difficult for a system that doesn't have any real users yet.
If you can't build such a test system, or your tests don't reflect the typical actions of your users, something could slip through the cracks. If your tests with 100,000 users on one server, that doesn't mean that production will work with 5 million users on 50 servers.