3 ms·
Given that this stack costs $6/year, running on a $2 controller, it seems somewhat expensive, unless it is providing some sort of advantage/benefit. However, th
by laydn 5y ago
Given that this stack costs $6/year, running on a $2 controller, it seems somewhat expensive, unless it is providing some sort of advantage/benefit. However, the examples on Github aren't complex enough to show what is the advantage of this ecosystem.
Perhaps a much more detailed blog post going over an example would help us understand why this stack is useful? Since you appear to have paying customers, clearly, there is an advantage, but it is not immediately obvious.
- the__alchemist 5y agoWhat happens if the devs making a device stop paying? Do the customers' devices stop working? Also, that seems like an unacceptably steep BOM item for a consumer device. The MCU itself costs less in many cases over reasonable device lifetimes.
- matharmin 5y agoI'd assume offline features would keep functioning, but online features would stop working. The online features seem to be device provisioning (so may not be able to change WiFi access points?), OTA updates, and cloud PubSub.
- kasperl 5y agoIt is worth noticing that you enable and disable the serviceability for individual devices when you want to. Your unserviced devices are free and keep running your code. https://toit.io/pricing https://toit.io/pricing
- detaro 5y agoThe submission is about the language, which they just open-sourced and thus doesn't cost anything.
- meltedcapacitor 5y agoYes but may not be worth learning if it gets orphaned once the sugar daddies realize selling cloud service subscriptions to $2 sensors is a naff idea. A community could pick it up, but doesn't work every time with open but abandoned VC-ware.
- owenfi 5y agoThe advantage from using it a bit (not for anything real yet) is that it supports remote code/deploy/logging/communication. So it’s for the server/maintenance aspect that you are paying a monthly fee.