4 ms·

There is a big need for open API for internet of things. Currently, each company has proprietary protocol for talking to their gateways or service. Which means

There is a big need for open API for internet of things. Currently, each company has proprietary protocol for talking to their gateways or service. Which means need to have separate app. Can integrate with IFTTT, Google Home, or Alexa, but those need integrations for each service. Open API would allow the open source home automation systems like Home Assistant to have integrate with the services. Or make easier for Google Home and Alexa to control the open source systems. Or apps that control devices and gateways from different companies.

EGreg 9y ago
How do you prevent this phenomenon though: https://www.xkcd.com/927/ https://www.xkcd.com/927/
- yeukhon 9y ago
  Now we are back to regulations. /s It takes more than two decades for browser implementers to recognize the need to follow specs as much as possible. The only way to replicate that without the two-decade mistake again would be a compelling toolsets available. Docker got people interested in containers, so Docker has the influence in driving the standard, although I am not really sure how many implementers will participate and willing to bend. In general, the dominant one has to be willing to let go of its "pride" so others will "follow" to beat the dominant one. Otherwise everyone will be busy beating everyone and forget about consumers (which includes developers).
  - pjmlp 9y ago
    Given how things are going with Chrome taking IE's place, I doubt it.
  - imtringued 9y ago
    There are a lot of alternative container runtimes to docker. The problem is that you still need to use docker to build your container images.
- samstave 9y ago
  I knew it would be that one!
- crdoconnor 9y ago
  Make the standard open, make it work, build a high quality reference implementation and market the hell out of it. As far as I can tell Mozilla is one of the only institutions with the resources and incentive to do all of this. I'm not altogether convinced they won't fuck it up though - the way they handled firefox OS was not encouraging. They might spend all of their time stroking their beards and deliberating over where to put the comma in their specs rather than getting their hands dirty with no-brand Chinese hardware manufacturers and figuring out all of the subtle problems that can arise building a network of devices and the not so obvious use cases. If I were running mozilla I'd put the office for this venture in Shenzhen and make sure that the employees visit often and work closely with OEMs because if you keep these people away from actual manufacturers then the result is going to be pretty poor.

EGreg 9y ago

How do you prevent this phenomenon though: https://www.xkcd.com/927/ https://www.xkcd.com/927/

yeukhon 9y ago
Now we are back to regulations. /s It takes more than two decades for browser implementers to recognize the need to follow specs as much as possible. The only way to replicate that without the two-decade mistake again would be a compelling toolsets available. Docker got people interested in containers, so Docker has the influence in driving the standard, although I am not really sure how many implementers will participate and willing to bend. In general, the dominant one has to be willing to let go of its "pride" so others will "follow" to beat the dominant one. Otherwise everyone will be busy beating everyone and forget about consumers (which includes developers).
- pjmlp 9y ago
  Given how things are going with Chrome taking IE's place, I doubt it.
- imtringued 9y ago
  There are a lot of alternative container runtimes to docker. The problem is that you still need to use docker to build your container images.
samstave 9y ago
I knew it would be that one!
crdoconnor 9y ago
Make the standard open, make it work, build a high quality reference implementation and market the hell out of it. As far as I can tell Mozilla is one of the only institutions with the resources and incentive to do all of this. I'm not altogether convinced they won't fuck it up though - the way they handled firefox OS was not encouraging. They might spend all of their time stroking their beards and deliberating over where to put the comma in their specs rather than getting their hands dirty with no-brand Chinese hardware manufacturers and figuring out all of the subtle problems that can arise building a network of devices and the not so obvious use cases. If I were running mozilla I'd put the office for this venture in Shenzhen and make sure that the employees visit often and work closely with OEMs because if you keep these people away from actual manufacturers then the result is going to be pretty poor.