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

101–110 of 240 posts

Re: macOS 26 breaks custom DNS settings including .internal

#101

Post by mikestew »

intrasight wrote: post #86
mikestew wrote: post #65

Earlier quoted context omitted.

Your “next question” seems very leading. Can you make your point more clear? What’s your answer to that question?

I don't understand your question since my question was honestly posed. What might lead Apple to make a change that would reduce the audience of their devices. I don't develop on macOS but I know developers who do. Did they just make a mistake and they're gonna fix it?

I doubt it was an intentional change. A lot of bugs result from, "hmm, didn't think about that use case. Ooops." There's just the question of how long it'll be before they ship a fix. It seems like there ought to be an automated test for something like this, but Apple seems to be shedding QA as fast as Microsoft is.

(And apologies if it seemed that I was insinuating ill intent on your part.)

Re: macOS 26 breaks custom DNS settings including .internal

#102

Post by [deleted] »

whalesalad wrote: post #25
himata4113 wrote: post #10

Still wishing for the day apple is split into the hardware and the software company. I want their silicon, but I will never use their (arguably terrible) operating system. If I can't run my own kernel and kernel modules then it's a device that I don't own. Firmware is alright in some cases, but my laptop next to me is running core boot just to prove a point.

macOS is not perfect but I don't think anyone could seriously argue that it is terrible.

[deleted]

Re: macOS 26 breaks custom DNS settings including .internal

#104

Post by oasisbob »

dec0dedab0de wrote: post #30
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.

There is a huge difference between using an llm and just blindly dumping it's output on someone verbatim. I think it's fine to have an llm write a first or second draft of something, then go through and reword most of it to be in your own voice.

If one is trying to avoid plagiarism, starting with an AI draft and polishing it to avoid signs of its true origins is not a good method.

Re: macOS 26 breaks custom DNS settings including .internal

#105

Post by hrmtst93837 »

binaryturtle wrote: post #9

I run a setup like that on my (outdated) Yosemite machine to provide multiple private TLDs for local deployment/development needs. I set that up in like 2014? Even back then it was known already that the quick /etc/resolver way was the deprecated way to do things. So I guess they finally killed that feature off? The proper (more awkward) way is to use scutil directly (which then stores the settings in some binary pli…

[flagged]

Re: macOS 26 breaks custom DNS settings including .internal

#106

Post by alin23 »

reaperducer wrote: post #87
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…

[flagged]

Does everything need to be snark on HN now? What is happening with this place?

Those are valid problems affecting real people. For some are just missing conveniences, for others they are full on accessibility issues.

Re: macOS 26 breaks custom DNS settings including .internal

#107

Post by alin23 »

nowahe wrote: post #88
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…

Ah I was wondering why I couldn't get past 600 nits on my M5 why it worked great on my M1. Guess I'll just have to live without it for now

It's still possible with the older forced HDR + Gamma tone-mapping logic, but it has its limitations. The native unlocking was miles better.

Re: macOS 26 breaks custom DNS settings including .internal

#108

Post by bdcravens »

torben-friis wrote: post #32
ramon156 wrote: post #26

Bit off-topic. I mostly use Linux and I'm of the opinion that it's miles better than Windows, but I don't fully understand why people say MacOS looks bad? Ignoring the current Tahoe mess, MacOS felt relatively polished. I'm purely talking about UX here, as the OS is evidently buggy. The most popular Gnome themes are a re-impl of MacOS, so I can't be the only one.

I'm with you, pre Tahoe I've never had an issue with iOS aesthetically, other than lack of customisation. Then again I never understood the trend to remember fondly windows 98 and those kind of interfaces, maybe it's generational.

> Then again I never understood the trend to remember fondly windows 98 and those kind of interfaces, maybe it's generational.

I may have a generational bias (I am almost 49), but I think the fondness is due to lack of UI surprise. A button was a button, a menu was a menu with clear shortcuts, etc. There were no mystery scrollbars that required specific interactions to appear or expand. Don't get me wrong, I'm a happy-ish MacOS user and love screen size, clear fonts, etc that we get in the modern world, but I think we've all had moments of frustration when we had to go on a scavenger hunt in an app and cursed those who didn't leave well enough alone.

Re: macOS 26 breaks custom DNS settings including .internal

#109

Post by brookst »

827a wrote: post #69
mrbuttons454 wrote: post #13

Papercuts like this are why I moved away from macOS. I will say, I don't love the use of LLMs to write these bug reports. It's probably fine if reviewed, but at least review for things like "worked on macOS 25", which obviously didn't exist. If that wasn't caught, how sure are you that the rest of the report is accurate? We all want the bugs fixed, but people are going to start throwing out the obviously LLM written…

Its my strong belief that using AI in any capacity which does not upfront state "the following content was generated by artificial intelligence" is never acceptable. In most situations, allowing an AI to wield your name gives off the scent of "My time is more valuable than yours, so I've automated writing to you." It is quite disgraceful. If your use-case would be materially harmed by an upfront disclosure of AI gene…

[flagged]

Re: macOS 26 breaks custom DNS settings including .internal

#110

Post by brookst »

bigyabai wrote: post #91
wyufro wrote: post #61

Earlier quoted context omitted.

That's very elitist and unfair to people who previously struggled to form their words but now have a better chance at doing so.

An elitist attitude towards plagiarists is common.

Also elitist attitudes towards people for whom English isn’t a native language, elitist attitudes towards people with dyslexia and other conditions that make writing difficult, and elitist attitudes towards people with lower education levels.
Post reply on HN