390 karma · joined January 23, 2017
For that to work, I'd like that cars that have features like this show you what they're seeing. Tesla does this a bit by showing all the cars it has detected in the dashboard. But it should go further and other car brands should do the same.
Without that, you're right, you can not be sure if the car is going to react to something on its own.
However, you can't really do that with a phone, since it eats battery and needs a stable wifi connection.
AirPlay 2 solves that by allowing the phone to buffer minutes of audio to one speaker, which then distributes that buffer to the rest of the speakers.
We're building a technology-agnostic IoT Platform with focus on LPWAN and SmartCity. Features include device management, metrics, communication history, rule engine and parsers.
Our software is built with Elixir in the backend and JavaScript (VueJS) in the frontend and makes use of the Phoenix Framework, PostgreSQL and RabbitMQ. We have a modern CI setup built on Docker and Gitlab.
If you're fluent in either VueJS or Elixir (preferably both), we'd love to talk.
https://gist.github.com/narrowtux/19220fc077ecbaeb274c56e849...
The latest entry blocks the smooth scroll on the site of this post. They've gotten smarter now and include this in bundles.
It will take you a few months to fix all those problems and even then it could be that some email provider decides to put new requirements in place.
I find this useful because it allows you to reuse a controller (action). In most applications you'll have at least 2 views on the system: UI and API. Sometimes, they're the same, but very often they're not.
That just doesn't work because of business decisions on google's end.
However, processes in Erlang/Elixir are used ubiquitously. Most of the time, they run forever like some sort of service and are restarted when they crash. Sometimes, you won't care about the result.
That's the reason why features such as tracking success/failure in a persistent data store is not a core feature. You could easily add those features to your processes though, the necessary API is already there.
The alternative is to use message queues that are durable. Only ack the message when you successfully handled it. If your application crashes before the task was completed, the task will be redelivered the next time the application starts.
Only mobile, the web version is shitty because it hosts a web server on your phone which is unreliable. And even with that you can only access the web version from one computer and it does not work well on tablets.
1. They already have a lot of accessories for lightning and they would kinda lose that sweet 30 % MFi for 3rd party lightning accessories
2. A lot of people who don't know why USB C is great will probably bitch about how Apple is changing the port on the iPhone _again_, like they did when they switched from 30 pin to lightning. Could be a PR nightmare