3 ms·
I hesitate to rain on a positive parade, but.. Keep in mind when enabling features ahead of widespread release in software, that obvious and/or non-obvious thi
by floatingatoll 7y ago
I hesitate to rain on a positive parade, but..
Keep in mind when enabling features ahead of widespread release in software, that obvious and/or non-obvious things are more likely to break when you do so than if you wait until it’s enabled for you.
This goes double for users on the Release channel of software rather than the Beta/Nightly/Canary/Whatever channel, since it takes weeks or months to fix problems.
I’m not saying “don’t”, but I am saying “be prepared to encounter self-inflicted issues”. The tendency is to blame the issues and the frustration of tracking down their cause on the software developer. Keep notes about what you enable, so you can try disabling it and see if that fixes it. Report bugs you find, and don’t panic if they’re known and/or unsolved.
- o-__-o 7y agosuch as expecting an application (not OS) based DNS resolver to react to /etc/hosts changes...
- floatingatoll 7y agoYes. But. That’s very specific and assumes they’ll only ever query one or the other, which might not necessarily be true for *.local and localhost (I haven’t researched or tested).