I want a CodeBug

Practice with the emulator, stick a piece of card with a hole cut out of it on your monitor and you can pretend to have the first in the country

Greg

Thanks for responding - please just shove the stuff on to Github (or wherever) - the format and gloss don't matter at all but you have the chance to claim the moral high ground over the BBC - take it !!

MK

The "There is no attempt not to publish" bit? It is why I rarely support kickstarter campaigns - so many crowdfunding examples of

deadlines with no firm date, or vague promises that are not binding (or even if they are, in practice are not easily enforceable).

There is another thread here Codebug partial teardown where someone has taken a not-insignificant attempt to reverse-engineer the board in the absence of schematics.

I don't like you guys any more .....

After your postings I decided it would remiss of me not to have one to show the kids when we do the Arduino courses so I ordered one.

Mark

Element 14 addicted !

Enrico

Early on in really innovative projects there are many uncertainties, and Kickstarter is suited for these products. Kickstarter is about backers for a project -- people that want to support it's aims, and for CodeBug we're very grateful to these people for helping us;  it's not a contractual arrangement. I think it's important people realise this, and if people are uncomfortable with this it they can wait until the commercial version of products come out and not back Kickstarters.

If we'd done it as a commercial project, the offering would be very different and probably not ultimately creative commons. And although the project has been delayed (though not as much as micro:bit The BBC micro:bit will, predictably, be delayed until 2016 (Wired UK)) we're really pleased through the help of our backers we've got Code Bugs out into the hands of people and they're learning to code with them, which is what the project was really about.

codebug wrote:

 

  it's not a contractual arrangement.

I think this is the point I was making. You're under no obligation (legally) to release the  schematics, although morally you should do so having made the promise.

The unpredictability of Kickstarter project timelines, and promises unmet, and (often) poor excuses for delays, is why it is wise to wait for the commercial offering for at least the non-innovative projects, or to purchase a close-alternative product that is already available.

I think a major difference between micro:bit and codebug is that the micro:bit project has not taken any funding from consumers expecting hardware and software to be supplied to them, whereas codebug has.

Chance to win a CodeBug over the weekend, if anyone fancies one

CodeBuggin' Competition: Tweet to Win a CodeBug

I was wondering why the comparison of project delay with the micro:bit was brought up.

This explains the relationship between the two projects a bit: How the BBC micro:bit will kick-start a coding revolution (Wired UK)

About half-way down is a comment about the University of Manchester team's role (and the role of Andrew Robinson - creator

of the Piface series of boards as I understand, which Problemchild had to reverse-engineer in order for effective support).