This is a weak argument as pi-hole needs to go to a resolver or perform recursion itself which will give you the same latency or worse. The 1ms latency will only apply to already cached entries that are also cached by you OS anyways, whichever solution you are using.
If you configure NextDNS on a router, your router will perform the exact same caching pi-hole is doing, so it will make no difference performance-wise.
NextDNS will soon have a solution to auto-follow tracking links and allow some blocked domains temporarily from the blockpage. Just make sure you install the root CA on all devices.
It's convenient to have stdout only returning the body so you can work with it without having to remove the header. With curl, if you pass the -v, you get headers on stderr too.
When headers are specifically requests with -i for instance, I agree curlie should print them on stdout. PR accepted ;)
Author here: the main driver for writing curlie was not about the slowness of httpie but about all the features I was missing from curl. As curlie is just a wrapper on top of curl, you get all the great options of curl like http/2, http/3 support, advanced TLS options etc.
That's like a tiny bandaid; in the next iteration they'll copy the A/AAAA records instead of CNAMEing them; that would make CNAME uncloaking useless _and_ save one DNS roundtrip reducing browser latency.
If it is true it would buy ad servers greater obfuscation since blockers were relying on CNAME metadata to differentiate between safe and unsafe targets. If more reverse lookup and secondary metadata and vhost dereferencing is required it will complicate performant ad stripping at a minimum.
If you configure NextDNS on a router, your router will perform the exact same caching pi-hole is doing, so it will make no difference performance-wise.