Earlier quoted context omitted.
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.
So you're upset an operating system that is called macOS is not in fact Linux. Gotcha.
macOS 26 breaks custom DNS settings including .internal
161–170 of 240 posts
Re: macOS 26 breaks custom DNS settings including .internal
#162Re: macOS 26 breaks custom DNS settings including .internal
#163Re: macOS 26 breaks custom DNS settings including .internal
#164Containers ran using docker are called containers, not dockers.
Re: macOS 26 breaks custom DNS settings including .internal
#165the resolver confs all contain this content:
# /etc/resolver/example-private
nameserver: 127.0.0.1
domain example-private
I noticed in the author's bug report they do not include `domain`, which is documented in `man 5 resolver` as: # The domain directive is only necessary, if your local
# router advertises something like localdomain and you have
# set up your hostnames via an external domain.
In the real world though, I've found the `domain` setting to be required nearly every time. I wonder if adding it will resolve the issue?Re: macOS 26 breaks custom DNS settings including .internal
#166Papercuts 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…
1. Am I allowed to ask an AI to proofread a draft for grammatical errors?
2. Am I allowed to ask an AI to proofread a draft for technical errors?
3. In both #1 and #2, am I allowed to ask the AI to suggest revisions, or is it only allowed to point out what's wrong and why?
4. If I write a sentence like "Lucy's laughter ___ her underlying anxiety" and I'm having trouble coming up with the right word to fill in the blank, can I give the sentence to an AI and ask it for a list of possible options?
5. While brainstorming, can I use an AI as a souped up rubber duck before I begin writing?
Re: macOS 26 breaks custom DNS settings including .internal
#167Earlier quoted context omitted.
So you're upset an operating system that is called macOS is not in fact Linux. Gotcha.
pretty much, it's unix and I want it to be unix, but I get the worst parts of linux and windows combined.
Apple really is leaving everyone else years behind in making hardware. Yet they’ve never done what I would consider obvious geek-friendly things to MacOS. I’m sad about it too, and I wish the OS were better.
Re: macOS 26 breaks custom DNS settings including .internal
#168These days I’m just using Caddy to do ..localhost for my web dev and it works like a charm.
This is exceptionally sloppy on Apple’s part.
Re: macOS 26 breaks custom DNS settings including .internal
#169Earlier quoted context omitted.
Source? [1] states 12% for macOS and 3% for Linux. [1]: https://gs.statcounter.com/os-market-share/desktop/worldwide...
That's desktop market share. I'm sure the comment you're replying to means overall usage including mobile and server, where Linux is far and away the leader.
Re: macOS 26 breaks custom DNS settings including .internal
#170Earlier quoted context omitted.
macOS is not perfect but I don't think anyone could seriously argue that it is terrible.
It’s pretty bad. IPC doesn’t work reliably any more. The window manager is unusable. Spotlight misses results and also pegs the cpu, killing battery. Finder is bad enough on its own, but the 1:N mapping from logical directories to filesystem directories (like photos, home, applications, etc) makes it essentially unusable without spotlight. Notifications are flaky as hell (missing phone calls and messages from contact…
Not OP, but accessibility tools on mac put other desktop OSes to shame.