lowercase1

Trucks have a higher duty cycle than cars so a battery pays for itself quicker.

Truckers have legally mandated breaks that largely mitigates charging time.

Charging infrastructure is cheaper than hydrogen infrastructure.

>And it's with this decision that every reasonably happy, veteran developer I know distinguishes themselves. They all choose Extra.

Selection without causality can explain this. Turns out people who survive either have personality or environment that enable them to feel the Extra work is worth it. Where I'm at, it certainly doesn't.

Yeah the tech seems feasible but I'm skeptical of controlling capital costs when you need carbon nanotubes membranes as a core piece.

Air capture is also quite expensive and I'm not sure how much the "only need small concentrations of CO2" trick does.

Many of those shareholders are diversified and may benefit more from a freer Russia than they lose in short term google profits

This seems good but falls apart with.long approval chains (which are maybe the core issue).

If I need library PR approved so I can make a service 1 PR so I can make a production release request so that I can deploy a one line change then it's hard to get things done with 4 hour ping time.

Anyone can take a battery and just decrease the discharge rate and claim "long duration storage".

The hard part is making it cheaper per kWh.

If they made it cheaper per kWh then they should say that

Them: Please randomize a list in O(n) time.

Me: so you just want me to generate O(n lg n) bits of entropy in O(n) time? That's not possible.

My username is "fucky" after I used an name to describe my feelings of having to create/use a Microsoft account. Exercise to the reader to guess the unshortened name

That's what qualifies as "compact" these days?

Yeah. I have a poor view of terraform since my first interaction was trying to a few one line changes to avoid repetition but couldn't find why it didn't work without setting up connection to the AWS S3 bucket.

Thanks for the answers.

How is session state kept? Is /event required (as data would be sent in /next?).

Also as I understand, Processors won't be involved until they are needed. E.g. if we have 2 panes but only the result of the first was required to be processed, would the processor be invoked after just the first pane was complete?

Would be interested in:

1. How you implemented this on the backend? Did you consider using something like Temporal, AWS Simple Workflow, or AWS Step Functions?

2. Interested in how you're avoiding (waiting) on network calls on each action. You mentioned it was coming in next post.

3. How are you managing multiple workflows? Does a common child graph make sense for a common workflow?