Alexander

In Siberia land use rules are quite harsh, they are just enforced by criminals, not government (which is criminal too pretty much). Do not recommend.

Well, in Finland, this kind of setup is deeply default. It becomes the main power consumer in November though.

Was thinking about this very topic, although I plan to catch wind.

So far the best ideas I’ve got are:

1. Scavenge old Toyota hybrid Ni batteries - those are surprisingly reliable long after they are not giving enough power for a car, and have quite good charge-discharge capacity
2. Build Fe-Ni base batteries - messy but cheap
3. Switch part of equipment to compressed air, run compressor for storage, spin generator with air on demand, possibly bubble air through some kind of bioreactor (kelp, mushrooms, etc.). Maybe same thing with vacuum line.
4. Electrochemical synthesis on spare power (pretty much open battery loop; just a little bit - by making materials to be used in non-rechargeable batteries - or completely - make something useful elsewhere like metal coatings; I could extract stuff from local minerals, or barrety broth, or some kind of local goblinite). Anyway, something that wouldn’t care about random schedule, as opposed to, for example, greenhouse lighting or heating.

Home power storage is very hard to design. Ballpark-wise, I found that energy storage could be as profitable as renting space for living, normalized by square meter; thus it’s bound to be at least about as expensive to run. If possible, you should consider making smart grid with neighbours.

This is so true! Tried “nice crossplatform WASM” multiple times - every time you need a system call, drawing single pixel, networking, or catching input - you just start debugging JS. If the logic is simple, whole code ends up being JS mess with small inclusions of Rust. Very unpleasant experience, even with all the modern frontend code generator tools.

I ended up deciding that making custom bindings instead (edit: mention uniffi here) and building frontend in native (Qt/Kotlin/Swift) ends up being simpler, more pleasant, and the end result is faster and prettier (and no wasm limitations). The downside is having to actually use XCode if you do want iOS app to work (which is quite simple but unpleasant and requires you to have Apple hardware or suffer a lot), but if not and you don’t care for Apple worshipers - it’s pure win.

Even 2 years ago, yew was way way worse than actually writing js by hand.