Other Boards - Unsupported?
..the reason why I don't think it is a good idea to sell the board with pin headers soldered is that the pin headers take up a lot of space, especially when they are used. that is, wires with connectors are plugged in. many users would buy the board because is is very compact. but the connectors would really make it difficult to fit the board into a small space, compared to if you just solder the wires into holes. and soldered connections are a lot more reliable than pin headers and matching connectors. so I would definitely sell the board with pin headers but not soldered. it can be difficult to remove pin headers that are soldered.
I think I really just have to give people the option... While I think pretty much everyone is capable of soldering the connectors, it still puts a lot of people off getting started - especially if they haven't done anything like it before.
I'd prefer to just supply a bare board too - but given Espruino is all about how easy it is to get started, I think it makes a lot of sense to have one version with pins.
first of all, I'd like to commend you - as simple as that. You stepped into this endeavor with the right motives, and you show an incredible spirit, creativity, dedication, perseverance - and last but not least - awesome productivity.
With most products the question is how to balance engineering and marketing. Both cost, latter opens the wallet, and - or but - first one keeps it open (after discovering that it was not just a marketing bluff and a good sales pitch). Too much engineering (time) upfront makes the money (ROI) come (back) in too late... or too little or never at all, because by the time the product hits the market, the requirements/demands have already changed (...that's why 'agile methodology' came to be to help with this dilemma - especially in the domain of software development - it helps to be shippable at any time, ...on and with every increment in business value.)
It is important to have a clear understanding of prototypical inheritance. When a property is read from an object instance, the instance itself is first inspected to see if the property is defined on it. If not, the prototype chain is traversed and the value from the first object in the chain that has the property defined is returned. When a value is assigned to a property it is always on the object instance, never the prototype. The result of this is that all objects that share a common prototype will return the same value for a property defined on the prototype, unless the value has been set on the instance. This makes it easy to define default values for primitive data types (number, string, boolean) in your class declaration and update them on instance objects as needed. However, if you assign object values (Object, Array) to a property on the prototype, every instance will manipulate the same shared value. (from: Classy dojo, dojotoolkit.org)
Have a great Espruino time! - until next time - allObjects
tage, I agree that they should be included, but the rest is just egotistical. I've plenty of friends who can't solder but write awesome software and want to play with this stuff (and have made some really cool projects without soldering).