31–40 of 56 posts
Earlier quoted context omitted.
"features"
The phrase is usually "batteries included" not "and batteries"
I would interpret "batteries included" to mean "you don't need to worry about shaving a yak to get this installed, it's all there and ready". Language is fun!
Should this be “an” in the page header?
What’s with “and batteries”? Doesn’t even get mentioned in the features list. Makes this feel AI generated and doesn’t clarify anything.
What’s with “and batteries”? Doesn’t even get mentioned in the features list. Makes this feel AI generated and doesn’t clarify anything.
Probably an attempt at "batteries included" as in it comes with everything you need to start using it. https://news.ycombinator.com/item?id=39101910
Isn't it easier to understand what is going on just by calculating the condition on the top and put the text on the markup based on that condition?
I feel like there are few places where in order to don't duplicate part of the text it's being made extremely difficult what the text is going to be by putting it far away
What’s with “and batteries”? Doesn’t even get mentioned in the features list. Makes this feel AI generated and doesn’t clarify anything.
For personal monitoring, I've been using Uptime Kuma (and been happy with it). Has anyone looked how these two compare?
A status page should not replace your internal monitoring, so including "batteries" is both not necessary and a bad idea - because of the next point.
A status page should not have dependencies, and if it does, they should have higher availability than your service. Otherwise, you need a status page for your status page. Node.js sounds like a liability in this case.