Nix is sort of that third option, though I really wish there was a well-documented way to use it on macOS as purely a binary/source package manager. A lot of stuff I read online goes into setting up nix-darwin to manage desktop settings and etc. and I just don't need or want that.
That being said, if you haven't used MacPorts in years, I'd say it's worth the jump. I recall moving from MacPorts in the first place because Homebrew was faster and allowed for customising packages.
When I switched back to MacPorts again, it was because Homebrew had become slow and no longer allowed package customisation. Now, MacPorts is much faster and has the variants system for package customisation.
Thank you for this helpful information. It might be worth a try. I initially moved to brew because it was "new", because I liked the command line interface, and because it seemed more "segregated" from the rest of the OS's files (/usr/local/Cellar and so on). But it's increasingly aggressive messages reminding me I am a second-class (or third-class) citizen due to the age of my OS is really off-putting.
If it's a mechanical one, there's a possibility that it's been repaired or replaced. The mechanism after all these years will likely wear out. At the same time, I know someone with a car whose odometer has been at 249,999km for a few years now.
As for (early) digital odometers, does the soul more specifically exist in the EEPROM chip in the instrument cluster* that stores the odometer data?
*at least on my late-90s car, this is how the odometer/trip meter works.
My 2007 Corolla odometer has been at 299999 since 2019. I've replaced the transmission once, but the rest is original, aside from expected maintenance - tires, brakes, fans, etc. - and an added stereo.
An aside on your last point: In the D gear, a lot of auto transmissions will be set up to allow for the wheels to spin somewhat independently of the engine (in any gear) when you aren't accelerating, which accounts a lot for how well an automatic will coast when you release the throttle, even if you're not going fast enough for top gear (especially apparent with older four speed boxes).
Using the numbered gear options will enable clutches/bands that provide more engine braking.
Huh, interesting. I had thought it was just from the higher gears being used. Vast majority of my driving is with manual, I've only really driven modern autos with 5+ gears (and a Toyota hybrid, which don't really have gears at all).
I’ll absolutely admit knowing very little about the nuances of payment networks in the US, particularly with contactless —- but my experience (in Australia) is that payment terminals that support contactless inherently support Apple/Google/etc Pay, even if the payment terminal is unaware of those things, in which case the transaction will work the same as a contactless card transaction (e.g. transactions >$100 require PIN).
It's been in macOS for quite some time. Mostly dormant now but at one point it was what powered the Web Sharing option in the Sharing prefpane. It was also used in OS X Server (both the OS X versions designed for Xserve and the later "app" version) before that was largely whittled away.
I can't exactly find if it came with OS X since the beginning (which would predate nginx and friends), but it probably was a much more likely choice back in the day, and I guess that's why it's still included. Wouldn't be surprised to see it quietly disappear from later macOS releases, though.
"quite some time", is an understatement. The Apache HTTP Server was included as part of Mac OS X starting with version 10.0 (Cheetah), which was released on March 24, 2001. Prior to that, users of Mac OS X would have to manually install and configure Apache HTTP Server, if they desired to run a web server on their Mac.
I feel like it dates from earlier internet, before the age of walled garden takeover, when it still seemed like a decentralized internet would be the thing, and everyone would be, like, using a desktop GUI to create html or something. Of course everyone should have a webserver on their machine, right?
Apple was ahead of the curve on something that never arrived and many of us still miss.
The web sharing was more about sharing on local networks. It was the same concept as the Public folder for file sharing which dates back to NeXT. When Bonjour née Rendezvous was released Apple build an Apache module for it. When web sharing was enabled it would advertise the server over Bonjour. Safari still supports Bonjour server discovery IIRC.
The Apache install would obviously work over the Internet but sharing over the local network was its main purpose.
What kind of content do you think they imagined as use cases for local network http server over bonjour? Like for a small business? Or household? Or giving strangers access to something when you happened to be physically adjacent and on the same network?
It still seems like kind of evidence of a decentralized networking environment that never really came to be... bonjour in general kind of is, although it's still there and gets used for some specific things. But we have ended up doing a lot more connections "cloud-mediated" instead of peer-to-peer.
MacOS 9 had a personal web sharing feature. The Apache server with Rendezvous/Bonjour was basically the MacOS X implementation of the same. For OSX it was literally a free mechanism to add web sharing.
As for the use case, in the classic MacOS days and even early days of OSX the system didn't ship with support for Windows file sharing. It wasn't until IIRC Jaguar (10.2) that Samba shipped default with the system. Web sharing made for a workable lowest common denominator for getting content off a Mac to Windows. With Bonjour (in Safari) you'll see all the shares on the local network segment.
Additionally since web sharing was just Apache it shipped with a bunch of the extension modules. I believe PHP was enabled by default so you could just drop a PHP script in your Sites folder for a dynamic page. CGI was also simple to enable because thanks to all the shipped modules.
Bonjour is decidedly a local peer-to-peer discovery mechanism. Even the packets have a short TTL so they don't route beyond local segments. It's far too chatty to be a WAN discovery system.
We ended up with cloud mediated connections because of NAT and UPnP hole poking sucks. Residential routers are really shitty in general. They also don't make port forwarding easy (or possible). So a host behind a NAT router doesn't usually have good options for receiving incoming connections. That's why we've got a bunch of NAT traversal protocols and need public hosts to mediate those connections.
>It seamlessly detects when the peer is local so it doesn't route out to the internet and back
One of my use cases for Tailscale was connectivity between my primary NAS and an off-site NAS I use for backups. Being able to bring my NAS to the same site/network I had set-up the off-site NAS and just have things work over the LAN without reconfiguring anything was a wonderful surprise.
(Yes, I’m aware I could save some overhead by reconfiguring but looking at the network traffic monitor I was happy enough with the throughput I got though Tailscale’s LAN routing)
It's what happens when a country dismisses a proper national ID number/card -- the nearest available substitute gets used, sometimes regardless of how well the substitute works as an ID. The United States Social Security card/number comes to mind as a particularly egregious example, though I'd also consider drivers' licences (as is common in Australia) to also be a bad substitute.
Anecdata, but I think for pre-paid services Optus never stored that information, and only used it for the required identification.
I had activated a pre-paid Optus service (in a store, using my drivers' licence as ID) but let it lapse a year ago, and allegedly my licence number was not in the breach.
I had a prepaid Optus number too. I let it lapse years ago but I got the same email about name, number address being leaked, but not license or passport numbers.
I never used the Optus number and I have moved since then. So maybe impact is minimal. But I'm still angry.
That being said, if you haven't used MacPorts in years, I'd say it's worth the jump. I recall moving from MacPorts in the first place because Homebrew was faster and allowed for customising packages.
When I switched back to MacPorts again, it was because Homebrew had become slow and no longer allowed package customisation. Now, MacPorts is much faster and has the variants system for package customisation.
reply