IMO live demo is better in some cases, but if there are complicated or time-consuming steps where the prerequisite can not be met quickly, a recording would be better
This is horrible news. Zigbee has been trouble-free and Thread has been nothing but Trouble to the point I had to throw out everything based on Thread…
some of the tests and standard answers are strange such as the one with debounced function not considering whether there should only be 1 arg / the dev could use the arguments keyword and call, the filter numbers question insisting on === instead of == etc etc.
Agreed. There is no alternative to thinking. However a good collection of conventions, primitives & building blocks, can assist greatly in architecting a robust system.
We do test systems to the point of breakage. It is not something we skip just because the language is good.
As to existential risk:
I will try to be succinct. If there has been no exposure then there is no need to hedge.
Further, there are commercial firms which will maintain your critical systems. In other words, a long term maintenance contract for Elixir systems can be procured from more than one source.
Regarding numeric stuff. I discussed this matter with some folks and it was quite interesting because just like Erlang/OTP was used at control plane for phone switches while the data plane was implemented in something else, one could theoretically leverage it to oversee ML processes (perhaps Python programs written with PyTorch or something else)
The topology is exactly the same
In fact, porting your vetted numeric code to Elixir is probably going to make the risk go sky high, but running the same code with supervision structure in Elixir would in fact reduce risk so is a no-brainer