News for hackers. Stuff that matters.
Re:macOS 26 breaks custom DNS settings including .internal by brookst on Thursday March 19, 2026 @02:20PM (#47443631)
Classic perfect/good.

The choice is not usually “have humans write amazing top notch documentation, or use an LLM”.

The choice is usually “have sparse, incomplete, out-of-date documentation… or use an LLM”.

Re:macOS 26 breaks custom DNS settings including .internal by mort96 on Thursday March 19, 2026 @02:58PM (#47444179)
And my claim is that the latter is better.
Re:macOS 26 breaks custom DNS settings including .internal by brookst on Thursday March 19, 2026 @03:17PM (#47444450)
Cool, so just ignore documentation then. Problem solved for everyone.
Re:macOS 26 breaks custom DNS settings including .internal by mort96 on Thursday March 19, 2026 @06:13PM (#47447052)
I dont see how that solves anything.
Re:macOS 26 breaks custom DNS settings including .internal by dare944 on Thursday March 19, 2026 @10:40PM (#47449787)
We wouldn't have these silly arguments?
Re:macOS 26 breaks custom DNS settings including .internal by brookst on Tuesday March 24, 2026 @03:49PM (#47508081)
* Projects can focus on code first, and do best-effort on docs for low cost * Most of us get reasonable quality documentation, much better than what some poor developer would turn out in spare moments * You are spared from the outrage of imperfect documentation
Re:macOS 26 breaks custom DNS settings including .internal by mort96 on Friday March 20, 2026 @08:00AM (#47453385)
Gah hopefully the meaning was clear from context, but I just realized I said "latter" when I meant "former". Inconsistent human documentation is better than miles upon miles of AI-slop documentation.
Re:macOS 26 breaks custom DNS settings including .internal by systoll on Thursday March 19, 2026 @08:09PM (#47448403)
Given that people have access to LLMs themselves, publishing their output in lieu of good documentation (no matter how sparse) seems like it’s mostly downside.