4 ms·
>I read this as "embedded devs don't know how to consume REST APIs", and I also found it unlikely. >the real-time/embedded devs wanted to use some crazy board
by whatshisface 6y ago
>I read this as "embedded devs don't know how to consume REST APIs", and I also found it unlikely.
>the real-time/embedded devs wanted to use some crazy board that couldn't run anything useful
You said it was unlikely, but then described how it happens. The reflex of many embedded devs is not to use big processors running standard software speaking standard protocols. IoT represents people realizing that there are many applications where it's a good idea to use a $20 board and standard software to do something that could technically be accomplished by a $0.02 chip and 100 different serial protocols.
- LeifCarrotson 6y agoThere was a great primer on embedded Linux boards by Jay Carlson a couple weeks ago that touched on the network limitations and various tradeoffs that devices in this class need to make: https://jaycarlson.net/embedded-linux/ https://jaycarlson.net/embedded-linux/ In summary, if you can't have your IoT device plugged into the wall, or connected by a "crazy" 802.15.4 low-power serial wireless network to a hub device that is, and especially if you have BOM cost constraints, battery life requirements, or processing needs that mean you can't use Linux or lwIP, you're going to have a bad time.
- sam0x17 6y agoI guess my followup question then is "why do embedded board manufacturers design boards that don't work with industry standard tools and languages"?