You can either choose truthfulness or empathy.
You can either choose truthfulness or empathy.
Which is my point.
Perhaps I've been lucky or I haven't been observant enough, but I've never seen a company suffer financially because of inefficient code. Don't get me wrong, I still value good code for its own sake, but in my experience there is no correlation between that and profits.
The worst is when the performance is so bad it starts to prevent onboarding new features or customers.
- How much alcohol can a pregnant person drink? (Not too much, obviously, but is a glass of wine a couple of different days in the third trimester okay? Probably, but it varies a lot deoending on which country you're in.)
- When can children start eating green leaves? (I don't know, but even different counties in Sweden have different guidelines on that one.)
- Should infants sleep on their tummy or back? (Definitely on their back. There is no argument there. But when I was an infant -- which is not that long ago, parents were advised otherwise.)
At first I thought this sounded like a blend of the virtualisation framework with a firecracker style lightweight kernel.
This project had its own kernel, but it also seems to be able to use the firecracker one. I wonder what the advantages are. Even smaller? Making use of some apple silicon properties?
Has anyone tried it already and is it fast? Compared to podman on Linux or Docker Desktop for Mac?
This project had its own kernel, but it also seems to be able to use the firecracker one. I wonder what the advantages are. Even smaller? Making use of some apple silicon properties?
Has anyone tried it already and is it fast? Compared to podman on Linux or Docker Desktop for Mac?
And like I'm not all anti-GUI, it's just that docker is one of those things I've never even imagined using a GUI for
It’s just that Docker Desktop makes it easy and also provides other integrations like file system sharing etc.
I have often wondered if it would be worth designing an EV battery that can permanently short out a bad cell in a string, perhaps by deliberately disabling balancing, letting the bad cells voltage fall to zero, and then perhaps having a single use 'bypass' that latches on.
It wouldn't be a seamless user experience, because if you discharge the cell to say 0.5 volts but then the user tries to charge their car, you can't let them, since you cannot safely charge a lithium cell which has fallen below the minimum voltage, but you also cannot bypass it till the voltage falls to zero. Could be done automatically at 3am though like system updates.
Either way you need some form of overbooking / compensating capacity.