> The real question is whether fusion will ever be economically competitive with renewables+storage.
Could you elaborate on what storage you have in mind? The only effective way we have to store large amounts of electricity right now is [pumped-storage hydroelectricity](https://en.wikipedia.org/wiki/Pumped-storage_hydroelectricit...), which is interesting but also very sensitive to the geography.
I'm by no means an expert, but as far as I know a combination of batteries for fluctuations in the dozens-of-hours range and Power-to-{Methane,Hydrogen,Ammonia} for seasonal variations is what experts think feasible.
Writing your own transducers is hard and error prone, but I think using and composing the ones given you by clojure.core is actually rather easy (Especially using the 3 arity of `into`).
I dunno. Except for one very specific project, I've yet to see a "Wow!" use case for transducers. The only place where they really shine is working with channels, but I think channels are a big design mistake (after extensive work trying to tame them).
Interesting! Why do you think they are a big design mistake? I can understand how they can be misused, but I find myself missing them in every language I used that doesn't have them...
So either I'd rather talk about the COMPUTATION and resource safety rather than the channel, as in Pipes/Conduit/Streaming from haskell.
OR, I'd rather deal with a direct actor model a la Erlang, Pony and Cloud Haskell.
Go's experience is so goddamn miserable it should just put the entire notion of async channels as a higher level programming library to bed. As a low-level primitive, it's okay but not fundamental.
Like another reply to your comment, I thought about having a very small js script in the header puting `Date.now()` in a global, then on page load, having another script checking the amount of time that had passed to see if it was worth downloading the "extra" at all. But then again where do you put the threshold? Has anyone tried this with some degree of success?
For your concern number 3, the creator of spacemacs has created a package to help you author lisps in normal mode (https://github.com/syl20bnr/evil-lisp-state). It is included by default in spacemacs (all the bindings begining with `SPC k`).
It offers you all the cool features of paredit (barf, slurp, splice, transpose, convolute etc...), but it is easier to use in evil-mode. Check it out!
That would have to be an INSANE worldwide propaganda effort to pull this off. Or maybe, the propaganda is not where you think it is.