Not GP, but: not confident. How confident would I be to avoid a (slightly lower entropy) UUID collision while also avoiding a clock desync landing on the exact same logged millisecond? Very, which is how confident I was about not encountering an UUID collision before this thread, so very++ I guess.
I just read UUIDv7, something I wasn't familiar with until now. That does address everything I had in mind yes. I assumed timestamp-uuid meant purely based on the timestamp precision, in which case you can get conflicts if you don't have a reliable clock across your system.
At temperate latitudes, summer/winter is a bigger deal than day/night. To the point where it makes sense to orient fixed panels tilted south and you still get a 2-3x difference in daily capacity between the seasons.
Related is the other comments here that mention air-conditioning is largely a non-issue if you spec for year-round solar. If you are generating 3x as much energy in July compared to January, and January can power your house, then the A/C is basically free.
You can buy a full day's worth of energy storage with an array of LiFePO4 batteries for less than the typical 3% estimate of annual home improvement and maintenance costs you should be budgeting for as a homeowner. The cost problem usually comes from the labor and every solar installation company seemingly being ran by scam artists.
Thats whats driving the buildout in places like spain.
Solar power is in curltailment most days, so to make money solar operators need to add batteries to take free energy and shift it to the ultra expensive parts of the day.
Because solar energy production doesn't just vary by time-of-day, it also varies seasonally. Where I live, winter solar production collapses due to decreased daylight hours and cloud cover. At the same time, energy use skyrockets due to heating demand.
We would need a lot of batteries to be able to charge during the summer and drain during the winter!
I started writing in a Dioxus (rust framework) style. max 1KB of js code. Sending the diff via WebSocket from the rust server, and , what is more important, all code is now on a server, and because of websocket and rust it executes almost same speed as on the client. Back to normal pages sizes. And, of course, virtual scrolling everywhere.
Hard feelings here. I like react and have to work with it, still it is all insanely wrong.
The best approach I've found so far is egui , and I hope people are moving that direction. Draw whole frame, collect events, process, update internal state.
reply