> I assume that datacenters UPSes are better [...]
I don't know about specific datacenter models, but in our colocation there are humans available 24/7. So the UPS might not start after failure, but there's a human to figure it out.
Most (all?) decent datacenters also have generators on site, and the intent is that the UPS will never run out of charge. So the fully-discharged case is an error and it might be intentional to require intervention to recover.
Yeah, some people treat UPSes as "backup power" but that's not really what they're intended for. Their intended purpose is to bridge the gap during interruptions... either to an alternative power source, or to a powered-off state.
Sure, but when you stick a UPS in the closet to power your network or security cameras or whatever for a little while if there is a power interruption, you expect:
a) If the power is out too long for your UPS (or you have solar and batteries and they discharge overnight or whatever) that the system will turn back on when the power recovers, and
b) You will not have extra bonus outages just because the UPS is in a bad mood.
I completely agree with B. But alas, people love buying shitty cheap UPSes.
But A is along the lines of the misconception that I'm referring to... There should be no such thing as "the power being out too long for your UPS". A UPS isn't there to give you a little while to ignore the problem, it's there to give you time to address it. Either by switching to another source of power, or to power off the equipment.
Now, the reason that every UPS that supports auto-restart has it as a configurable option, is because you often don't want to do this for many reasons, e.g.:
* a low SOC battery could not guarantee a minimum runtime for safe shutdown during a repeated outage
* a catastrophic failure (because the battery shouldn't be dead) could be an indication of other issues that need to be addressed before power on
* powering on the equipment may require staggering to prevent inrush current overload
The whole use case of "I'm using the UPS to run my equipment during an outage" is kind of an abuse of their purpose. It's commonly done, and I've done it myself. But it's not what they're for.
But also, if you want a UPS that auto-restarts -- they exist -- but you get what you pay for.
> a low SOC battery could not guarantee a minimum runtime for safe shutdown during a repeated outage
A lot of devices are unconditionally safe to shut down. Think network equipment, signs, exit lights, and well designed computers.
> a catastrophic failure (because the battery shouldn't be dead) could be an indication of other issues that need to be addressed before power on
This is such a weird presumption. Power outages happen. Long power outages happen. Fancy management software that triggers a controlled shutdown when the SOC is low might still leave nonzero remaining load. In fact, if you have a load that uses a UPS to trigger a controlled shutdown, it’s almost definitional that a controlled shutdown is not a catastrophe and that the system should turn back on eventually.
All of your points are valid for serious datacenter gear and even for large server closets, but for small systems I think they don’t apply to most users, and I’m talking about smaller UPSes.
> > a low SOC battery could not guarantee a minimum runtime for safe shutdown during a repeated outage
> A lot of devices are unconditionally safe to shut down.
Yeah, but that doesn't mean you want to expose them to brownout conditions when your UPS is depleted. If the power is continuing to flip on and off, it's better to just leave it off if you don't have the battery to prevent even short interruptions. A good UPS can do this automatically for you. A cheap one will just stay off and let you respond to the outage.
> This is such a weird presumption.
It wasn't a presumption I was making for all users -- but an example of why some users might not want auto-restart as a feature. Of course, if you want auto-restart as a feature, you can buy a UPS that has it as a feature and turn it on.
> they don’t apply to most users, and I’m talking about smaller UPSes.
Yeah, I know the situation: Someone has a network closet on a budget with a UPS they've sized to get them a few minutes of runtime. They put a UPS on the BOM because it checks a box. So they buy a low-end UPS that either doesn't have the feature, or it doesn't work right.
The solution is just to buy the right UPS for the thing they were trying to do... and test it.
Out of curiosity: What is your USP? Why should I prefer your product over draw.io?
IMHO (this may not apply to you!) a lot of people launch a "competitor" of a product which seems to be a clone of the product without improving something that the other product misses/is very bad at.
Maybe - but that's also a style of life definition, isn't it. I did not care at all about Bitcoin, and I'm still pretty fine. I even think, sitting Bitcoin out was better for me, because who (vrosdly speaking) cares about it today (besides speculating with it)?
That's fine for me - as long as the new subscription (Pro+AI) is the same price as it is now.
If they increase the prices, well then my Kagi subscription is gone and I will move on. I'm a happy user for noe but I think search wuality has gotten worse lately and I'm more often using the AI instead of search because search just does not bring any good results anymore.
I think the day I _must_ walk go a desk to vote is the day I'll give up. Voting by mail is one of the best things occuring here (in Switzerland). You get the voting stuff by mail, make your crosses, put it back into the postal box and it's delivered for free (as in beer) to the government.
> it's delivered for free (as in beer) to the government
Not everywhere though; it's up to the canton or municipality to implement this. It's literally the only reason I still buy stamps.
Should be made a thing at the federal level imho.
It's completely normal here. People get federally mandated time off to go vote; 3 hours IIRC, which is way more than would ever ordinarily be necessary (and polling stations are open well past typical work hours). I typically walk a few minutes from home, and never experience a significant lineup.
Relying on the postal service here would make it much worse, honestly.
> [...] I decide to take the time to explain [...]
Do you just explain or do you start by asking a question?
What I usually go with is _asking_ what they want to achieve. Because usually, the user describes features/functions/forms instead of explaining the business case. And while the user describes a business case (a thing that generates him money/...) it becomes obvious how/why to implement the request.
No, it was a perfectly fine question IMHO. it is a broken incentive - it is expected that you design complex systems regardless whether they are useful or not. Try to interview for the role you have to fill, nor for a role you a dreaming you would love to have whenever you're Google2.
If the interview wants you to think about stuff that never happens in your role, I think it is a sign that in your role, you're expected to solve the problems like in the interview.
I don't know about specific datacenter models, but in our colocation there are humans available 24/7. So the UPS might not start after failure, but there's a human to figure it out.
reply