Dan is correct (naturally); depending on complexity and scope redux can be a drag. For a small project I will use an event emitter to communicate state change requests to my top level component. These sort of things tend to only have a handful of components anyhow.
I was attempting to confirm that these are all points are important. Being too arrogant to learn and being in incompetent are two entirely different things.
So long as you don't use JSX you certainly never need to transpire. I believe there is also a shim to do client side jsx parsing but is not encouraged for use with prod code
Despite all the hand waiving about accuracy of the claims or the efficacy of CDN fronted caching, etc etc, it is good to see more initiatives around saving (especially mobile) bandwidth use. After moving from EE into full stack js I've been blown away as the duplication present
A directional antenna at the active wifi radio would enable longer range. One interesting application would be the ability to dogleg a wireless connection between points A and B where there is no LoS to each other, but both have LoS with point C. It would be a low throughput link, but it would allow for an awesome implementation of a private two way communications system. I.e. Several miles without direct LoS between the two end points.
It'd be enough to achieve significant power reduction for the <100ft region though; pretty sure wifi modules would be able to support both passive and active modes depending on availability.
Idk, I just try to be reasonably fluent in the language...frameworks tend to play to one ideology or another and it seems just as important to pick one you understand as it is to pick one that purports to solve your problems better/faster/etc.