Aurora clones are copy-on-write at the storage layer, which solves part of the problem, but RDS still provisions you a new cluster with its own endpoints, etc, which is slow ~10 mins, so not really practical for the integration testing use case.
piggybacking on this, the performance of Firefox on a Mac with a 4k external screen is abysmal. any action at all takes an extra second or two to perform. not to mention that if i start watching a youtube video it makes the fans go crazy.
i changed back to chrome because of this and it's so much smoother.
i have exactly the same issue. so many websites nowadays choose to have dark themes which are essentially black backgrounds with white text and it is physically painful to read. if i'm invested enough in the article, i always try to change the user styles a bit to make it more bearable.
It seems much too close to the original Show HN to have a second one two days later. The rules (https://news.ycombinator.com/showhn.html) say: "New features and upgrades ("Foo 1.3.1 is out") generally aren't substantive enough to be Show HNs. A major overhaul is probably ok."
This may not technically be a new feature but slight variations on the same thing are very much in the bucket that that rule is meant to address.
This is a special case of a more general issue: follow-up posts [1] are not great for HN because they are repetitive, and curiosity withers under repetition. The test we apply is whether a post contains significant new information [2].
can you tell me a bit more about this? i wanted something like this for a small api i have but ended up using marshmallow to validate jsons against defined schemas which i think is a bit overkill.
second this. I haven't needed cap in a while for the work I'm doing, and I don't often see it mentioned (perhaps because I'm not looking) but it's a fantastic tool for managing atomic deployment.