401–410 of 691 posts
FINALLY we've come full circle and can have widgets on the desktop again! It's not like a revolutionary killer feature for me, but I just always preferred having information always in my "peripheral" instead of having to actively check a separate menu.
Next thing I'm waiting for: Apple removes the useless Stage Manager "feature" (it's not a feature, it's a bug).
So it goes... Warning: You are using macOS 11. We (and Apple) do not provide support for this old version. It is expected behaviour that some formulae will fail to build in this old version. It is expected behaviour that Homebrew will be buggy and slow. Do not create any issues about this on Homebrew's GitHub repositories. Do not create any issues even if you think this message is unrelated. Any opened issues will be…
These warnings keep getting longer every homebrew release. You may want to try macPorts, which goes out of their way to explicitly support releases all the way down to 10.5.
It’s better suited for a multiuser system (and I share my desktop with my wife who has a different login) and is more stable, too.
Is there any update to Music.app? 50% of my work on a computer is managing my local music library, and the app is extremely buggy since the rewrite in Big Sur. Want to make sure it doesn't become more buggy in this release.
Still hoping for the death of .DS_Store every macOS release.
Earlier quoted context omitted.
https://nixos.org/download.html#nix-install-macos The homebrew team seems incredibly burnt-out, to the point of hostility. I've really enjoyed the nixpkgs community so far and encourage others to check it out; it hasn't replaced homebrew entirely for me (yet), but it's getting closer every day.
Yes, the Homebrew message does seem unnecessarily hostile. Not everyone can afford to buy a brand new computer every year.
Maintainers get requests to do things they have no interest in, like maintaining software for OSes past a certain date. That doesn’t sound so bad, but there are a lot, and they can even be mean. The maintainer can block these users individually, but it’s different users all the time, so that doesn’t stop it.
So, the maintainer addresses the user base, the whole crowd all at once. The problem is most of these users haven’t seen these interactions, so the message seems hostile. Having someone say “I owe you nothing.” seems really weird when you’ve never asked them for anything. Or, if they list of all the ways and reasons for you to not contact them it looks hostile. The users don’t see the fan next to them throwing a beer can at the center fielder.
Earlier quoted context omitted.
I went to the wikipedia page, which is kinda the point. No other OS requires you too look it up. Even WatchOS and iOS directly use version numbers. Saying it's due to NextStep integration sounds like a strange defense of this naming strategy (if that was your intention). They have version numbers, but they decide to use the "code name" as a product name.
> No other OS requires you too look it up. Debian and Ubuntu frequently refer to releases by codename rather than number
Earlier quoted context omitted.
These warnings keep getting longer every homebrew release. You may want to try macPorts, which goes out of their way to explicitly support releases all the way down to 10.5.
One of the cooler experiences I've had with MacPorts was seeing some people go out of their way to ensure builds still worked on PPC Tiger and PPC Leopard. I remember seeing SBCL builds broken on Darwin/ppc for a long while, and eventually SBCL decided to drop support for Darwin/ppc altogether. Still, these ports maintainers did not give up and eventually found a way to fix SBCL builds on PPC: https://trac.macports.o…
I’ve also dabbled in this area http://leopard.sh/
I still don't understand why Apple is so bent on coupling application updates together with OS updates. I just want the new changes to Safari and Notes while I don't care about the other changes, why not have Safari be a normal application downloaded from the App Store, like the rest of us pleebs have to do when publishing apps?
macOS is a BSD; the whole point of BSDs is that the OS and "base system" are vertically integrated (and, usually, living in a monorepo together) so that a dev can one day decide to add a new API to replace one currently used by first-party apps, by just adding the code and then doing a big Search+Replace to fix all first-party apps to use it, all in a single commit.
it really isn't
I wish Apple would separate the updates of their bundleware from their OS. Some of the major updates have meaningful changes to the underlying OS (gatekeeper, SIP, etc.), but others - like this one - are primarily changes to frills like Messages, Notes, Safari and other Apple-native apps that I don't even use. I have no problem with Apple bundling these apps and making them work seamlessly together, and I don't even…
You know what would be even better? If you could reliably uninstall all this junk or not even install it at all. Every time I hit some button on my keyboard and the Music app opens asking me to create an account I am reminded how hostile all commercial operating systems are.
I mean, I'm using a GUI that is really primitive by comparison to Win/Mac (i3wm) but it's actually great. Extremely fast, efficient, and stays out of my way. There is literally no mechanism in the OS to pop up a notification or bounce an icon or blink anything at me. It couldn't interrupt me and piss me off even if some piece of software wanted to. It's amazing. Nothing updates on its own, and the OS runs very very few services or other background stuff -- basically only whatever I have explicitly configured and enabled. Again, awesome. I'm easily aware of every single process that runs on this machine, and if there's one I don't know about, there's comprehensive documentation about it, including how to configure it. That's honestly effectively impossible for someone using Mac or Windows.
Oh, I just installed a security patch in about 20 seconds. Open terminal (winkey->enter), "doas syspatch -c", type pass, see there's a patch, "doas syspatch" to apply it, done in 2 seconds. Once I reboot the newly-patched kernel is active. There is full documentation of the patch, including why it's needed, how the patch resolves the issue, and a diff of the patch is included.
Earlier quoted context omitted.
Yes, the Homebrew message does seem unnecessarily hostile. Not everyone can afford to buy a brand new computer every year.
One of the problems with OSS burnout is this many-to-one relationship with the users and maintainer. It’s sort of like the relationship between an outfielder and the bleacher crowd at a baseball game. Maintainers get requests to do things they have no interest in, like maintaining software for OSes past a certain date. That doesn’t sound so bad, but there are a lot, and they can even be mean. The maintainer can block…
Max Howell (founder of homebrew) went to interview at Google, shoved a coding exercise back in their faces, made a snotty comment about how all the engineers at Google using Macs use his code and how dare they blah blah greatest engineer in the world blah blah, and walked out the door.
That coding exercise was likely given to him precisely because all the google engineers had a lot of experience using brew, or they did it as ego check to see if he'd be insufferable to work with.
Howell failed to realize that and instead went and bragged about it on twitter, almost certainly confirming for the hiring committee that things had worked exactly as designed.
Whole lot of fucking sass from a man who either didn't care or didn't know about the security implications of making a directory in the default path user-writeable, thus making probably hundreds of thousands of developer's systems less secure:
https://infotoast.org/site/index.php/2021/05/30/homebrew-is-...