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

61–70 of 240 posts

Re: macOS 26 breaks custom DNS settings including .internal

#61

Post by wyufro »

duped wrote: post #16
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…

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.

Re: macOS 26 breaks custom DNS settings including .internal

#63

Post by andrewmcwatters »

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…

[dead]

Re: macOS 26 breaks custom DNS settings including .internal

#65

Post by mikestew »

intrasight wrote: post #56

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?

Re: macOS 26 breaks custom DNS settings including .internal

#67

Post by rebolek »

duped wrote: post #16
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…

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.

Using LLM is perfect for writing documentation which is something I always had problems with it.

Re: macOS 26 breaks custom DNS settings including .internal

#68

Post by seemaze »

mikestew wrote: post #43
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.

(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's the worst OS we have.. except for all the others.

Re: macOS 26 breaks custom DNS settings including .internal

#69

Post by 827a »

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 generated content, then you need to take a good, hard think on what that means for what you're doing (then again, maybe you're not interested in thinking anymore and that's how you got to this point in your life).

Re: macOS 26 breaks custom DNS settings including .internal

#70

Post by whalesalad »

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…

we have dev.our-root-domain.com in public DNS pointing to 127.0.0.1
Post reply on HN