# Why Open Source May Not Always Work For IoT

DevFeed: [Why Open Source May Not Always Work For IoT](<https://devfeed.tech/articles/why-open-source-may-not-always-work-for-iot-33406.md>)

Original publisher: [Read original article](<https://timkellogg.me/blog/2014/10/20/open-source-iot>)

Published: 2014-10-20T00:00:00Z

Content type: opinion

Language: en

Sources: [Tim Kellogg](<https://devfeed.tech/sources/tim-kellogg.md>)

Topics: [Internet of things](<https://devfeed.tech/topics/iot.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Internet](<https://devfeed.tech/topics/internet.md>), [Software](<https://devfeed.tech/topics/software.md>)

Tags: [iot](<https://devfeed.tech/tags/iot.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [open-standards](<https://devfeed.tech/tags/open-standards.md>), [standards](<https://devfeed.tech/tags/standards.md>), [technology](<https://devfeed.tech/tags/technology.md>)

## AI overview

This opinion argues that Internet of Things systems should use small, componentized open standards while distinguishing open specifications from open source software. It maintains that both open-source and proprietary implementations can have a place in IoT, and uses HTTP and replaceable components as supporting examples.

## Source excerpt

On Friday, Matt Asay wrote an article on readwrite about why the Internet of Things has to be open sourced that triggered a lot positive responses in my Twitter feed. I generally agree with what Matt had to say, but I found it unsettling that he conflates open source software with open specification. This distinction is important! There is a place for both open source and proprietary in the IoT and I believe that ignoring these differences will cause more harm than good.