Note that when reading my observations below, please understand that I have the greatest appreciation for both Cloud9 and BeagleBoard support. Their employee’s and community are awesome! Also - I love Python. Have been developing with it since 1995! Back when I was fighting COBOL programmers to give it a try. (wow - that ages me or what!)
IMHO, For either Cloud9 or BeagleBoard to deny this - well, is basically ignoring the elephant in the room. The natural asynchronous(ness) of ECMAScript leads me to believe that it will be a big player in the ‘Internet of Things’ - which the BBB is but a beginning.
I am proposing that instead of using the Cloud9 IDE on the BBB for software development - that developers use a Cloud9 IDE Workspace to develop software for the BBB. Once built on Cloud9 - Git pull/push the software onto the BBB. Thus BBB would not have to run the IDE, The IDE runs on a Cloud9 account used to develop the software for the BBB. Thus having Cloud9’s great support - and the BBB only has to run the released software! ( BTW - I do this all the time right now - develop in a Cloud9 Workspace and push/pull the repo to RedHat OpenShift, Amazon AWS, MS Azure, etc. )
Brilliant! Well, not so much… Unlike OpenShift, AWS, or Azure; the BBB has those pesky GPIO Pin interfaces. To develop software for the BBB on a Cloud9 Workspace would require - a
slug of the
require('bonescript') module - the slug which would mimic (for example, display on the console) the inputs and outputs that would be expected from the actual GPIO Pins on the BBB. A change to the package.json file would be the only thing required to load either the slug (in dev) or actual
bonescript in production.
So, Finally - what is your opinion? Is building a (‘bonescript’) slug allowing BBB development to be done on a Cloud9 Workspace it worth doing? Or should we wait for BBB to support Cloud9 IDE on BBB? Or wait for Cloud9 to support the IDE on BBB? I believe to expect either is kinda doubtful in the near future.
Please reply and thanks for reading!