I am an Android user, but I've always said that iOS wasn't designed for me. I've said it is great a great product if you want a simple to use smartphone that just works. I think this type of failure really makes me think twice about repeating that advice. Apple success has depended on creating clean products with extreme attention to detail. I'm really disappointed.
In their introduction they use the term meta-operating system.
ROS is an open-source, meta-operating system for your robot. It provides the services you would expect from an operating system, including hardware abstraction, low-level device control, implementation of commonly-used functionality, message-passing between processes, and package management. It also provides tools and libraries for obtaining, building, writing, and running code across multiple computers. http://wiki.ros.org/ROS/Introd...
Heres the thing about R/T robotic control systems in industrial robotics. The tasks that they run are well defined repetitive tasks that don't change much. The kinds of robotics that we see in Hollywood block busters require significant more intelligence and perception that require a little looser definition of real-time computing.
What you're talking about is hard real-time requirements. This means that if we miss some timing we have a total systems failure. ROS does not guarantee timing, so you'll have to come up with a different way to handle these. One solution is to have specialized, verifiable hardware the handles those hard real-time requirements. Usually these are things that prevent the robot from damaging itself, property or others.
There are many applications of robotics that have firm or soft real-time requirements. These are real-time tasks that can be handled by ROS. Robotic perception is something that doesn't really fit into the hard real-time requirement, so we have to think about ways that these systems degrade and fail gracefully when deadlines are missed.
Android is Java. Although ROS supports multiple language bindings the core is written in cpp.
Google has a rosjava port. Multiple machines can run in a single ROS system, so the rosjava port is usually used to create Android UI applications to control or view information in a multi-machine ROS system.
ROS development is tied very closely to Ubuntu. Some things work on Mac OSX, but that's because it's Unix based and the built system was easier to adapt. Windows support is practically non-existent because to build system is not well-suited for non-unix systems. You would have an easier time getting rosjava to work.
Really the reason ARM is supported easily is because it's simply a recompilation. Most of the Ubuntu packages that are required are already available for ARM. Full Android support is significantly more difficult.
I can send money from my GMail account. Why would I used amazon? Smart move on amazons part.
I can't imagine the identities of a bunch of ex-cons are that valuable.
You only need to learn one oo procedure based language. All others are just a book exercise.
The problem with that is most people think because they can program in that language they understand the paradigm.
There are tons of c++ and c# programmers out there who think object orientation is only about turning UI controls into objects. All other code is more of a mix of bad OO and imperative programming.
I would revise your original statement to you only need to learn one oo language well. Same for functional languages. You are have to know a language well to understand the paradigm.
I just don't agree with him. Bitcoins have some serious issues. If someone develops a digital currency that addresses those issues and makes them more practical for every day use I support it. If I had to wait for 10 minutes to get my starbucks coffee paid for I'd probably decide to just pay cash. I also wonder how quickly the blockchain would grow if bitcoin became more mainstream. Anonymity is also an issue. I think competition between digital currencies will only make them more practical and robust. That can only be a good thing for digital currencies in the long run. If progress is not made digital currencies will never replace conventional ones.
I think you missed the point of the article. Demand is far easier to manipulate. Cost incentives that match demand to supply will work if you scale the cost dynamically to match the instantaneous capacity of the grid. Turn a factory on full power when the wind is blowing and slow it down when the wind isn't.
and catch a ride with those SpaceX guys? I'd rather deal with the Russians.
Russia has a stock market?
I'd install Eucalyptus and develop an application. Then when my lease ran out I'd redeploy it on AWS.
I was just thinking "I don't own enough expensive single-use gadgets whose meagre functionality could be replaced by a few lines of code."
Yeah and this one comes with it's very own useless HD h.264 video decoder and HDMI port.
Reminds me of running instances on AWS. AT&T has no financial incentive to reduce these surprise charges. Seriously there should be a hard cap that we can set. Sure we are responsible for these charge, but most of the times naive consumers are not aware. Amazon clearly posts the prices of their instances, but it's not uncommon to get a $30,000 bill accidentally due to some developer testing out their application by spinning off instances. You get charged for the whole hour when an instance starts on AWS and things can show up on their accounting system weeks later.
A real time system for monitoring usage should be mandated by law and sufficient warning should be available. A data roaming plan should automatically be applied if it will save you money. Most importantly we should have the ability to set a cap.
Yeah we know....Did you even read the summary?