Live data from Hacker News

macOS 26 breaks custom DNS settings including .internal

gist.github.com

81–90 of 240 posts

Re: macOS 26 breaks custom DNS settings including .internal

#82
post #38

Earlier quoted context omitted.

at this point I really think its better to read broken english than have to read some clanker slop. it immediately makes me want to just ignore whatever text i'm reading, its just a waste of time

I do wonder, we had pretty good (by some measure of good) machine translations before LLMs. Even better, the artifacts in the old models were easily recognized as machine translation errors, and what was better, the mistranslation artifacts broke spectacularly, sometimes you could even see the source in the translation and your brain could guess the intended meaning through the error. With LLMs this is less clear, yo…

and not just artifacts/hallucinations, the worst thing about is the fact that its basically "perfect" English, perfect formatting, which makes it just look like grey slop, since it all sounds the same and its hard to distinguish between the slop articles/comments/PRs/whatever.

and it will also "clean up" the text to the point where important nuances and tangents get removed/transformed into some perfect literature where it loses its meaning and/or significance

Re: macOS 26 breaks custom DNS settings including .internal

#83

Ah great another reason to add to the many reasons not to use this OS. Semi serious question, is Apple looking to dump its existing customer base for a new, perhaps consumer not pro-sumer one?

Wait... someone is under the impression that Apple was ever good to its customers?

I thought we all just dealt with the overpriced hardware, the prisons, the control, that they are a US company that gives away data to the government(PRISM), has weak security(Pegasus), lies about hardware issues(butterfly keyboard and holding your phone wrong), deceptive marketing...

All so we can compile iOS apps.

If you arent compiling iOS apps... Do you not know about Fedora? Ofc Windows sucks, but we have Fedora.

Re: macOS 26 breaks custom DNS settings including .internal

#84

Earlier quoted context omitted.

(arguably terrible) operating system macOS has made some arguably poor design choices, but it makes it hard to take someone seriously when they state the whole OS is terrible.

It could be just me, but every time I tried to do something I sat thinking that I am not the target audience for this thing. I don't like the UI, I hate not being able to talk to the hardware the way I can on linux (uart took me way too long to get working), I am angry that I am not able to run kvm, I hate not being able to replace the desktop and fix bugs myself. That's what makes it terrible for me.

MacOS IMHO is no longer a viable OS for people like us(who know what this website even is). MacOS26 along with Windows11 are enshittifying and in some ways it's glorious to see. I do feel bad for non-IT people though, Linux is daunting to them...I get it.

Re: macOS 26 breaks custom DNS settings including .internal

#85
post #69

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…

It’s good-faith arbitrage. Until everyone automatically suspects everything to be LLM generated and there is zero trust, anyone doing this is eroding the good faith that lets them get away with it in the first place.

Re: macOS 26 breaks custom DNS settings including .internal

#86

Honest question: How would this affect me and the vast majority of macOS users who use the device for media consumption and productivity applications? Next question: what reason would Apple have to make a change that would interfere with developers using their operating system?

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?

Re: macOS 26 breaks custom DNS settings including .internal

#87
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]

Re: macOS 26 breaks custom DNS settings including .internal

#88
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

Re: macOS 26 breaks custom DNS settings including .internal

#90
post #61
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.

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

I disagree, because those aren't their words.
Post reply on HN