Ngl the weird UI bugs made me think it must be made by AI, either that or the developer has very skewed frontend skills where gradients are fancy but sliders & interactions are broken.
Because if you go down the callstack eventually you won't get the await keyword anymore; you'll get the actual 'waiters' and 'wakers' which define your scheduling
A UPS-style grid connected inverter (with phase balancing) would be significantly more complicated by also significantly more useful. More in the critical/specialized part category, rather than near-commodity (like MPPT/BMS)
There is no "who", once stabilizing institutions 'fall' the only remaining option is social pressure (which can come in various forms) but that does require a critical mass as it's very much reliant on network effects.
Having worked on compression algos, any NN is just way to slow for (de-)compression. A potential usage of them is for coarse prior estimation in something like rANS, but even then the overhead cost would need to carefully weighted against something like Markov chains since the relative cost is just so large.
> I have no idea why I should be against using LLM
It highly depends on your own perspective and goals, but one of the arguments I agree with is that habitually using it will effectively prevent you building any skill or insight into the code you've produced. That in turn leads to unintended consequences as implementation details become opaque and layers of abstraction build up. It's like hyper-accelerating tech-debt for an immediate result, if it's a simple project with no security requirements there would be little reason to not use the tool.
I have the same with journals, but the video archiving has actually come up a few times, still fairly rare though. I think the difference is that you control the journal (and so rarely feel like you need it's content) while the videos you're archiving are by default outside of your control and can be more easily lost.