Oh my sweet summer child. Even software being written TODAY isn’t being tested in HiDPI. Win32 still makes it difficult.

I’m not your child, and that’s false, it’s literally one key to change in the settings. That allows you to select the exact scaling factor, not macos’s “more text”/“less text”.

> By the end of the project, we wrote nearly four times as many lines of test code as we wrote for the Swift interpreter itself.

The UI got a massive overhaul in the new Xcode beta. It’s no longer confined to the sidebar.

Devs continue to be tricked by incremental updates to it. It's still deficient

There are fonts that rely on hinting for correct shaping at all sizes: https://xoxo.zone/@numist/116716601962175503

You’re thinking of the Bonjour sleep proxy. Normally if you tried to ssh to `mymac.local`, but your Mac was asleep, nothing would respond to the mDNS broadcast for `mymac.local`. If it had been long enough that your local mDNSResponder cache had expired, you’re out of luck.

The AirPort would take over for your Mac and respond to mDNS queries on behalf of its hostname. (I believe it would also repeat the service records.) So your lookup of `mymac.local` would resolve to your Mac’s last IP address, and the AirPort would send the WoL packet to your Mac’s MAC, hopefully in time for your TCP connection to succeed.

This isn’t quite lights-out, and Xserve ran the same version of Mac OS X Server you could install on any other Mac.

How is it not lights-out? You could remotely power on/off the servers (XServe only). Other Macs could not do this, as they did not have the separate LOM network interfaces, etc.

I managed a bunch of XServes for a while, they were incredibly good hardware. The Mac Server software kinda sucked (not the LOM stuff, it was as good as any of the LOM from Dell, which is to say, not amazing, but workable).

Sorry, I was referring to the automatic power-on feature described in the linked article.

Only on the Xeon models. The G4 and G5 didn't have any kind of LOM :(

My original comment was to add context to the article's first line:

  Apple FINALLY lets you turn on your Mac remotely, without having to press the power button.

To you and me, that sentence needs the word "again" appended to it.

To be fair, the number of users who ever touched an Intel Xserve is infinitesimally small in comparison to other Macs.

Any implication that OS X Server could only run on Xserve was inadvertent. I mentioned the special OS to preempt discussion of whether Xserve was, strictly speaking, part of the Mac product line.

Xserve is a Mac. In fact the original one’s product code was RackMac1,1.

What do you mean by “this succeeded?” Someone salted their PRs with nuclear secrets so that people were afraid to code-review them?

No. The intention is most likely to get automated LLM based code review mechanisms to stall out.

Normally you’d want that to result in a fail and a subsequent rejection.

But because the team who made the review agent and pipeline in my example had many false positives at first they resorted to a fail-open and report setup (not uncommon).

So when the LLM hit this bit and then stalled out the pipeline pushed the code to their Artifactory repo anyway resulting in it being used internally -> exfil of secrets and repos etc.

It’s more about bad design but bad design is pretty common unfortunately.

This sounds absolutely horrible, in all aspects. Sounds like there is no engineering culture at all.

Title buries the lede: the owner of the account under which the agent operates claimed to have likely had his account compromised, and the maintainer investigating actually seems to agree this is likely.

In my experience, it’s usually but not always enough for the hills in SF. But more importantly, regen can’t handle emergency braking (it would generate too much current and heat), and you can’t regen at all if the motor loses its path to the battery.

I assumed it was to target the most motivated, price-insensitive buyers while recouping fixed costs.