Increasingly I am seeing people looking at other peoples implementations and reimplementing them with their own techniques and getting away with it. Thus I think it is better to be open, get first mover advantage and possibly a piece of the other guys pie than to keep your cards close to your chest and be beaten by someone else with more money or a cheaper workforce.
Max magnificently wrote: I can well see why someone who has designed something that is capraciously cunning would want to keep it (the design details) for themselves...
By doing so they miss the opportunity to make the design even better. Chris Taylor of SparkFun explains it very well in this EDN article:
In open source, a lot of that concern comes from wondering "What if someone steals my design?" Well, good, that's kind of the point. Let them steal it. If they can make it better, you can steal it right back and make yours better. That's what makes the product a quality product. Then you design the next cool thing. The information is free, but at SparkFun, the hardware is where we make the money.
Hi Javi -- in your blog you mention hardware, software, and gatewear. It's probably worth noting that -- in this context -- the term "gateware" refers to the data that describes the configuration of an FPGA or similar programmable logic device.
On the one hand I totally agree with the concepts of open source software and hardware... on the other hand I can well see why someone who has designed something that is capraciously cunning would want to keep it (the design details) for themselves...
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.