never really understood the appeal of the arduino interface or cloud9. Well, for the arduino i can at least try to explain that, same with android, there are so many bad tutorials based on copy/past and boasting those IDE, that lots and lots of people start already thinking that is their only option.
No need for the negativity, can't blame those guys for wanting to get a larger userbase by making things easy. In the end the larger volume/bigger community is beneficial to everyone.
Once you get someone past the basics and into the 'advanced' mode setting them up with ssh, vim, and screen is a great way to be productive on a linux machine.
[1] Putty in this case being the terminal emulator for PC's which can also talk to serial ports.
There are so many awesome kits coming down the pipeline:
http://www.kickstarter.com/projects/1106670630/mojo-digital-...
http://www.kickstarter.com/projects/adapteva/parallella-a-su...
I'm hoping that BBB's (3B's?) are going to take their place in the fall. They seem much more suited to tinkering than raspis. A very exciting platform!
How so?
I thought RasPi has plenty of I/O, but I'm not familiar with BB.
Minor quibble: The lack of analog sound output. It shows that their mindset was not entirely focused on the robotics / DIY genre, but more on the miniature computer thing. You don't do sound output on a robot or controller from HDMI.
1. Looks like it's been out for a while. If you were getting a similar thing today, would you stick with it or go for something else [1]?
2. When you drop the beaglebone into the Rovio, would you actually be replacing its OEM controller, or just interacting with it over WiFi?
[1] http://www.amazon.com/Rover-App-Controlled-Tank-Night-Vision...
The big hold-up is lack of access to (or maybe pure lack of) encoders on the wheels (we were using the wifi/web interface). It's impossible to move by dead reckoning. This was actually part of our class, to teach us how bad dead reckoning is and then we moved on to CV for tracking and control.
I originally was attempting to use an MK802 android stick running ubuntu and interfacing it with an Arduino Micro.
However, for $45, it saves much time and "just works".
Also, like you said, it cannot do 1080p, so if you want that for XBMC get a Pi, but for a robot, this, to me, seems ideal.
Something that sets these apart from the Raspberry Pi are that they full of easy access I/O, and two the Cloud9 IDE.
It is insanely fun to write javascript code in a browser talking to this thing wirelessly and have it do stuff. For me who likes to do mobile robots this is the really really great. I've got one of the old Rovio telepresence [1] things (its a mobile base with a Web cam and a WiFi link) and this board is going to be its new brain. The angstrom distro on it is very similar to the distro that the Chumby came with only a bit more stuff (Python, yay!).
The HDMI output is ok (its not 1080p so don't even think you're going to do XMBC on this thing) but nothing to write home about.
One USB port so get a hub, but on the plus side you can provide you own 5V power supply and that means you don't need a powered hub (unless you're trying to run high power peripherals). The Logitech Unifying receiver works well if you want to add a keyboard and mouse in one plug. (Now if that Unifying Reciever did WiFi it would kick butt)
All in all I think its a really good board. Nice mix of features. It will put pricing pressure on the Arduino Due I suspect.
[1] http://www.amazon.com/WowWee-Rovio-Enabled-Robotic-WebCam/dp...