Cynical thought - this is a good way to thwart ex-co-founders who're building your hardware and forking your open source software IDE.
If this is part of that plan, I'd expect to see significant new work and features in this "web based" version of the software which never end up in the open source version that people (including your new-found competitors) can download and fork.
I wonder if we'll ever see an FTDI-style USB firmware bricking from either side of the Arduino war?
Would be one way to do it : Install an app, let it bind to a http protocol to communicate with the website ( like the following popular protocols magnet:// , itunes:// or steam:// ).
Save the code-history in git and let the app download the git and compile it + upload it to the Arduino, would be the next step. So the only thing you have to "transfer" is the git-hash + app id or an appid and a version number. Or generate the binary on the webserver, download it with the app and upload it to the arduino.
10 comments
[ 319 ms ] story [ 1354 ms ] threadYou're not climbing a mountain stealthily, you're allowing people to "peek" into an early version of your product.
How hard is it to just use common sense before writing words, seriously?
If this is part of that plan, I'd expect to see significant new work and features in this "web based" version of the software which never end up in the open source version that people (including your new-found competitors) can download and fork.
I wonder if we'll ever see an FTDI-style USB firmware bricking from either side of the Arduino war?
Save the code-history in git and let the app download the git and compile it + upload it to the Arduino, would be the next step. So the only thing you have to "transfer" is the git-hash + app id or an appid and a version number. Or generate the binary on the webserver, download it with the app and upload it to the arduino.