641–650 of 691 posts
Earlier quoted context omitted.
I wish they’d just get iOS, the iPhone, and macOS or whatever it is called now all the same. Today I should be running iOS 15 on an iPhone 15 talking to macOS 15.
Why? They're different operating systems with different backgrounds.
(It's already happened before where Windows jumps versions for various reasons, but one is to not sound too far behind other OSes.)
Earlier quoted context omitted.
Indeed, and I hope Ventura will get at least two years of security fixes. It's still my impression, that the 2017 Macs (sold by Apple well into 2018), should have made the cut for Sonoma. I don't even care about any of the new features. I'm more interested in bug and security fixes. So hopefully I have more time to hunt for the perfect display that can adequately replace the 5K 27" of my current setup. And I know the…
I too have been looking into what can replace the 5K 27" iMac display, because my 2017 5K iMac display has developed a column of bad pixels about 30% in from the right side. It's been that way for about a year and a half now and has not gotten any worse so I don't think I'm in any danger of suddenly needing a new Mac. The way my iMac happens to be on my desk I'm directly in front of a spot about 30% in from the left…
The Samsung display seems nice. But how long is Samsung going to support the devices OS? The price is also not competitive in my opinion. For 1600 I would prefer the Studio Display, even if it's not height adjusted.
I will probably wait for the next Mac mini model with the M3 SOC. Luckily I'm not in a hurry.
I hope it can do DisplayPort Multi Stream Transport. Currently I have to connect one screen through TB4, and the other one through HDMI despite the TB4 screen being able to daisy chain through DisplayPort. One screen is a 32 inch UHD 60Hz monitor and the other one is a 24 inch 2560x1440 90Hz screen which is rotated by 90 degrees.
My records indicate it is this: https://www.apple.com/shop/product/MMEL2AM/A/thunderbolt-3-u...
I drive two 34UM88 with it.
Earlier quoted context omitted.
> had to start his own company because FAANGs wouldn't hire him. LOL dude... "FAANG" is not the only place to work
But they are definitely at the top end of the compensation and job-security scale, which someone responsible for such a popular piece of infrastructure surely deserves.
Earlier quoted context omitted.
> I wish Apple would separate the updates of their bundleware from their OS. In a way it's a bit of a philosophical standpoint: macOS is the whole indivisible thing developed, built, and released in lockstep, kinda like FreeBSB base is the whole indivisible thing developed, built, and released in lockstep (and the rest is ports). In a way, removing tcsh from a FreeBSD install because you only ever use bash from ports…
Yeah, I get that, but I think there could be a middleground. They could ship all their apps as a bundle, and their raw base OS separately.
I am sure this can be managed, but someone else may say they do not want to do it.
Earlier quoted context omitted.
Yeah, I get that, but I think there could be a middleground. They could ship all their apps as a bundle, and their raw base OS separately.
So what do you do when - previous bundle exists, you upgrade raw OS, but the previous bundle is not compatible - you try to install new bundle, but did not install new raw OS I am sure this can be managed, but someone else may say they do not want to do it.
Earlier quoted context omitted.
Of course the devs dont need to support everyone and answer every feature request. Its more nuanced than that. As a dev, i like a stable environment and i dont like to do big updates all the time, since that means i have to spend hours updating my setup again. Everytime i run brew im scared it will hose my PHP versions, etc, since it auto updates everything. To install old PHP versions one needs to hack the install f…
I'm glad we have both Homebrew as well as MacPorts. It's like having options to choose a bleeding-edge or stable distro. I prefer the former (as a dev, who often wants to use reasonably new features and libraries - and honestly despite keeping up in versions I can count the breakage to my workflow in the past decade on one hand, at least I'm not a JavaScript developer) but I totally respect the latter as well, so I'm…
Earlier quoted context omitted.
Oh oh, it's getting closer. Currently on MacOS 12 with my trusted 2015 Macbook Pro. It still goes strong, but looks like the next major release may see the end of homebrew for this one. There's really no issue with this computer other than 16gb of RAM being a bit tight when every modern app is using Electron. Oh well, see how we go.
(Message also for your parent) Last week, I saw the writing on the wall. I installed OpenCore-Legacy-Patcher on two MBPs from 2015, updating 12.7 to 13.6. It is a MBP 13" 2015 (early 2016 variant) and a MBP 15" 2015 (late 2015?). Works very well but you need to follow the guide. Both machines are still working well, 'cept for the battery (already replaced on the 13"). Esp the 15" is still in good condition, my wife h…
Earlier quoted context omitted.
That's great until homebrew breaks in some fucked up way (which a few years ago it used to do often), or they break a package (ditto) and you try to report that to them, and they act like insufferable little shits back (and don't fix the problem.) It reminds me of my boss emailing gnu.org to tell them one of their mirrors was down and got a nastygram back that said "It's spelled GNU/Linux" and the mirror went unfixed…
> and the mirror went unfixed. They don't maintain the mirrors themselves. These are maintained by third party who decide to hosts the mirrors so there is that.
Earlier quoted context omitted.
Once again a good time to remember that there were multiple perfectly good package managers available when Homebrew was invented, they were more future-proof (by eg not putting files in /usr/local), and everyone only switched to it because for some reason Ruby programmers wanted all of their tools to be written in Ruby (and possibly by people with waxed mustaches.)
I don't care what language Homebrew uses, it just works. When I got my M1 MacBook in 2021 I saw some of this negativity about Homebrew, and since I was doing a clean install anyway I decided to try out MacPorts. I quickly ran into problems and switched back to Homebrew and it's been smooth sailing.