If I understand you correctly, you do a sort of blue green deploy? Load balancing between two versions while deploying but only one most of the time?

How do you orchestrate the spinning up and down? Just a script to start service B, wait until service B is healthy, wait 10 seconds, stop service A, and caddy just smooths out the deployment?

Business idea free for the taking:

Build home or industrial heating furnaces out of slightly out of date computer hardware. Give them away for next to nothing and make the money back by renting the cpu time out.

Electrical home heating is such a waste of energy when you think about it.

Electrical resistance heating is considered one of the most wasteful and least efficient forms of heating.

Heat pumps are four times as efficient and that’s why they’re used…

Isn't this just less efficient electrical heating? Or am I missing something.

At least out of the box, I'm pretty sure FAISS doesn't support sparse matrices.

I agree, I think this is very unpythonic behavior

Tough because of the subject matter or the writing? Would you recommend it?

$3.4B according to the article

I really want to use xonsh as my daily but everytime I try to do a git rebase it doesn't handle the inputs properly for my editor.

I agree, VimCal has the same business model as Superhuman but doesn't require an onboarding call. So I'm only using Vimcal

Probably excluded because they're deemed unintentional. Of course the mosquitoes don't kill us intentionally either.

I've been calling this "The Sunk Cost Fallacy Fallacy", people don't understand it but still quote it liberally.