Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

macOS 26 breaks custom DNS settings including .internal

gist.github.com

Post reply on HN
Print view View original

131–140 of 240 posts

Re: macOS 26 breaks custom DNS settings including .internal

#132

Post by brookst »

mort96 wrote: post #126
brookst wrote: post #115

Earlier quoted context omitted.

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”.

And my claim is that the latter is better.

Cool, so just ignore documentation then. Problem solved for everyone.

Re: macOS 26 breaks custom DNS settings including .internal

#135

Post by pier25 »

alin23 wrote: post #79

macOS 26 has to be the most breaking version so far, its problems and intended breaking changes making my app dev life so hard this year. Just to name a few: - Reference Presets no longer allow setting arbitrary SDR nits, making it impossible to natively unlock 1600nits of brightness on MacBook Pros or 2000nits on Studio Display XDR which breaks my Lunar app [0] (this seems to be intended, no idea what hurt Apple tha…

There are rumors iOS 27 will be a sort of Snow Leopard update with no new features [1]. Just bug fixes and performance improvements.

Hopefully Apple will do the same for macOS 27.

[1] https://www.macrumors.com/2026/03/15/ios-27-will-reportedly-...

Re: macOS 26 breaks custom DNS settings including .internal

#136

Post by doctoboggan »

philo23 wrote: post #55

It's not quite the same, but I've moved to using *.localhost for all my local web dev work. All modern browsers will resolve *.localhost to 127.0.0.1 internally. No need to setup any DNS resolvers or edit your hosts file. But that only really helps you when you're dealing with websites in a browser, and when you want the address to resolve back to your local machine. So it wont help you with other programs like pytho…

Yeah I've been doing this as well. I know it's a minor nit, but I wish that TLD was shorter. I've used *.local in the past but that has bitten me too many times.

Re: macOS 26 breaks custom DNS settings including .internal

#138

Post by hedora »

x3ro wrote: post #119
bigyabai wrote: post #94

Earlier quoted context omitted.

There's a reason macOS is the least-used OS behind Linux and Windows. If it was any less terrible, we would know.

Source? [1] states 12% for macOS and 3% for Linux. [1]: https://gs.statcounter.com/os-market-share/desktop/worldwide...

Steam reports 3.4% for linux and 2% for macos (last montg. This month numbers are probably hit by systematic measurement errors).

https://store.steampowered.com/hwsurvey/

Also, the 16% “unknown” in the graph you linked to implies huge error bars on macos vs linux!

Re: macOS 26 breaks custom DNS settings including .internal

#140

Post by lurking_swe »

zer00eyz wrote: post #41
duped wrote: post #16

Earlier quoted context omitted.

Using LLMs for any kind of writing is unethical, with the narrow exception of translation. If you didn't take the time to compose your words thoughtfully then you aren't owed the time to read them.

> If you didn't take the time to compose your words thoughtfully then you aren't owed the time to read them. Apply this argument to code, to art, to law, to medicine. It fails spectacularly. Blaming the tool for the failure of the person is how you get outrageous arguments that photography cant be art, that use of photoshop makes it not art... Do you blame the hammer or the nail gun when the house falls down, or is i…

“compose thoughtfully” != layman terminology

Lawyers thoughtfully write laws that other lawyers understand. I’m not sure why that’s confusing.

Post reply on HN