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.
macOS 26 breaks custom DNS settings including .internal
31–40 of 240 posts
Re: macOS 26 breaks custom DNS settings including .internal
#32Bit 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.
Then again I never understood the trend to remember fondly windows 98 and those kind of interfaces, maybe it's generational.
Re: macOS 26 breaks custom DNS settings including .internal
#33Still 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.
But you can run your own kernel on Macs, no? Isn‘t driver support the issue?
Re: macOS 26 breaks custom DNS settings including .internal
#34Re: macOS 26 breaks custom DNS settings including .internal
#35Papercuts 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…
Re: macOS 26 breaks custom DNS settings including .internal
#36Programs like LittleSnitch never really seem like "enough" for me, because the computer has to boot before DNS filtering comes online. It also has the design error (IMHO) of pre-resolving IP addresses before clicking Accept/Deny(all).
A great blockrule for your personal firewalls would be to ban (at top level) icloud.com, apple.com, &c; system updates can then be performed manually using guides like http://www.mrmacintosh.com>. Of course: this breaks everything (in exactly the way I prefer to compute).
Re: macOS 26 breaks custom DNS settings including .internal
#37It also seemingly broke removing Safari cookies on a per website basis, something I often used to stop Google's scummy tracking across all their services if you just want to sign into YouTube.
Why use Apple's browser when they don't actually care about your privacy?
Re: macOS 26 breaks custom DNS settings including .internal
#38Earlier 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.
Re: macOS 26 breaks custom DNS settings including .internal
#39Re: macOS 26 breaks custom DNS settings including .internal
#40Bit 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.
There’s no “Tahoe mess”. I’ve used it since 26.0 and it’s good. Different indeed, but good. People love complaining.