There is two ways out of this. One is Bitcoin depreciating substantially, making mining less profitable. The other is having an alternative market for compute power that pays better. Projects such as Golem and (this author's very own) BitWrk are trying to achieve this.
It's all about giving a large (and thereby trustworthy) number of users the incentive to participate in a blockchain. It's about the economical system a blockchain exists in. Just having a blockchain guarantees nothing. Having a blockchain with a difficulty as high as Bitcoin's makes all the difference.
I don't believe in the hype around blockchain "technology". Those who advocate "private" blockchains have, in my opinion, misunderstood the whole concept.
Bitcoin creates so many innovative business opportunities. Knowing that your government is acknowledging it as a legal currency means there is a little bit less risk for running such a business. Which means that there is going to be more innovation.
The bugs fixed in the Oracle JRE are most probably also present (and have also been fixed) in the OpenJDK version, which is GPL-licensed. I don't know what all the Oracle bashing is all about. That's almost like blaming Red Hat every time a bug is found in a Linux device driver.
Java is a popular platform, and it is also a big platform. There will always be bugs, just like in every large piece of software. It has become a critical piece of infrastructure for many businesses. Being popular makes it a preferred target for attackers.
It is very cheap to put the blame on Oracle just at the time they're releasing bug fixes. But we shouldn't forget that they are not the only ones making profit from Java. And instead of crying for alternatives (which are probably less stable and have more undiscovered security holes), we shouldn't forget that most of Java is Open Source and that the Open Source community can actually work on fixing the problems.
Mining wasn't meant to be the biggest business in the world of Bitcoin. It will never be the type of "work" that can feed the masses, just like in the real world, only a few people are miners. But that doesn't make the idea of donating your computing/networking/whatever resources to some crowdsourcing mechanism in exchange for micro-payment invalid. Here is a couple of services that your computer could provide to others in an automated, peer-to-peer fashion for a couple of 'toshis:
I guess there might be some real economic potential for the last couple of items on the list. Has anyone attempted to write some kind of service-for-bitcoin software?
The while loops is where the interesting thing happens. They are like "wait until the looping is completed". As the whole maneuvre takes more than one iteration of the main loop, you need coroutines to write it that way. Instead of keeping your state in a state machine (with states LEVELING_OUT_BEFORE_LOOPING, FIRST_HALF_OF_LOOPING, SECOND_HALF_OF_LOOPING, LEVELING_OUT_AFTER_LOOPING) you keep the state in the execution context of a coroutine, preserving the expressiveness of the imperative programming style.
TFA is talking about the use of coroutines to avoid programming state machines. Coroutines are really very useful, as they allow code as simple as the following:
The code, which is supposed to make an airplane actor fly a looping maneuvre, is much simpler than the corresponding state machine code, which would consist of four states. I used this sort of programming in my hobby flightsim project Thunder&Lightning using this C++ implementation of coroutines. There is also Io, an embeddable language with a very small footprint which is easy to learn and nice to program with and which supports coroutines as well (actors in Io's terminology).
The parent is right. You will not be able to see things that were hidden to the camera.
All you are going to see is the scene as if camera and light source had switched places. Everything that was hidden to the camera in the original image will fall into black shadow regions in the generated image.
While you might suffer spinal injuries from a BRS landing, the same can be said about bailing with a parachute. The parachutes that e.g. glider pilots use are not controllable and will not give you the kind of soft landing that a sports parachute will. You might suffer a broken leg or similar.
Then there are situations where a BRS system does make sense.
Situations in which bailing is impossible due to accelerational or aerodynamic forces, like in a spiral dive.
To prevent the plane from crashing into buildings. Even if the BRS might not prevent this, it will certainly weaken the impact. This could even be used after bailing.
Situations in which bailing would take too long, like during take-off. I am specifically referring to the guy from my former gliding club who died about 1980 due to an misassembled aircraft. His elevator was configured in the wrong direction.
While it is probably also true that using the money for additional training might be the better investment for an individual pilot, keep in mind that many planes are utilized by several pilots.
Can voting over the net be made anonymous? I guess that in order to prevent multiple voting voters will be assigned some kind of serial number, right? (Hopefully not!) So how can secret voting be done?
Slashdot Mirror
There is a difference between power for mining and power employed for a useful purpose.
There is two ways out of this. One is Bitcoin depreciating substantially, making mining less profitable. The other is having an alternative market for compute power that pays better. Projects such as Golem and (this author's very own) BitWrk are trying to achieve this.
It's all about giving a large (and thereby trustworthy) number of users the incentive to participate in a blockchain. It's about the economical system a blockchain exists in. Just having a blockchain guarantees nothing. Having a blockchain with a difficulty as high as Bitcoin's makes all the difference.
I don't believe in the hype around blockchain "technology". Those who advocate "private" blockchains have, in my opinion, misunderstood the whole concept.
Bitcoin creates so many innovative business opportunities. Knowing that your government is acknowledging it as a legal currency means there is a little bit less risk for running such a business. Which means that there is going to be more innovation.
The bugs fixed in the Oracle JRE are most probably also present (and have also been fixed) in the OpenJDK version, which is GPL-licensed. I don't know what all the Oracle bashing is all about. That's almost like blaming Red Hat every time a bug is found in a Linux device driver.
Java is a popular platform, and it is also a big platform. There will always be bugs, just like in every large piece of software. It has become a critical piece of infrastructure for many businesses. Being popular makes it a preferred target for attackers.
It is very cheap to put the blame on Oracle just at the time they're releasing bug fixes. But we shouldn't forget that they are not the only ones making profit from Java. And instead of crying for alternatives (which are probably less stable and have more undiscovered security holes), we shouldn't forget that most of Java is Open Source and that the Open Source community can actually work on fixing the problems.
Mining wasn't meant to be the biggest business in the world of Bitcoin. It will never be the type of "work" that can feed the masses, just like in the real world, only a few people are miners. But that doesn't make the idea of donating your computing/networking/whatever resources to some crowdsourcing mechanism in exchange for micro-payment invalid. Here is a couple of services that your computer could provide to others in an automated, peer-to-peer fashion for a couple of 'toshis:
I guess there might be some real economic potential for the last couple of items on the list.
Has anyone attempted to write some kind of service-for-bitcoin software?
Why should the military only act in its own interest? It should act in the interest of the people it serves and who pay for it.
...at least if you ptogram in C/C++. It's so easy to mess up the stack. Being able to understand what's going on is a necessity.
Just don't use the portuguese you learn on Orkut to apply for a job :-)
Let's hope so. Here is her homepage. Don't be afraid to ask if you need more information.
... and have been used with great success in Iraq.
The while loops is where the interesting thing happens. They are like "wait until the looping is completed". As the whole maneuvre takes more than one iteration of the main loop, you need coroutines to write it that way. Instead of keeping your state in a state machine (with states LEVELING_OUT_BEFORE_LOOPING, FIRST_HALF_OF_LOOPING, SECOND_HALF_OF_LOOPING, LEVELING_OUT_AFTER_LOOPING) you keep the state in the execution context of a coroutine, preserving the expressiveness of the imperative programming style.
TFA is talking about the use of coroutines to avoid programming state machines. Coroutines are really very useful, as they allow code as simple as the following:
The code, which is supposed to make an airplane actor fly a looping maneuvre, is much simpler than the corresponding state machine code, which would consist of four states. I used this sort of programming in my hobby flightsim project Thunder&Lightning using this C++ implementation of coroutines. There is also Io, an embeddable language with a very small footprint which is easy to learn and nice to program with and which supports coroutines as well (actors in Io's terminology).The parent is right. You will not be able to see things that were hidden to the camera.
All you are going to see is the scene as if camera and light source had switched places. Everything that was hidden to the camera in the original image will fall into black shadow regions in the generated image.
This way the U.S. will finally win the hearts and minds of the Iraqi people. Go, America!
- Situations in which bailing is impossible due to accelerational or aerodynamic forces, like in a spiral dive.
- To prevent the plane from crashing into buildings. Even if the BRS might not prevent this, it will certainly weaken the impact. This could even be used after bailing.
- Situations in which bailing would take too long, like during take-off. I am specifically referring to the guy from my former gliding club who died about 1980 due to an misassembled aircraft. His elevator was configured in the wrong direction.
While it is probably also true that using the money for additional training might be the better investment for an individual pilot, keep in mind that many planes are utilized by several pilots.These Bacteria of Mass Destruction have been ignored far too long. Time to liberate Mars!
Can voting over the net be made anonymous?
I guess that in order to prevent multiple voting voters will be assigned some kind of serial number, right? (Hopefully not!)
So how can secret voting be done?
indy