Archive for January 12, 2026

Monday, January 12, 2026

Apple Picks Gemini

Google (CNBC, MacRumors, AppleInsider, Hacker News):

Apple and Google have entered into a multi-year collaboration under which the next generation of Apple Foundation Models will be based on Google’s Gemini models and cloud technology. These models will help power future Apple Intelligence features, including a more personalized Siri coming this year.

After careful evaluation, Apple determined that Google’s Al technology provides the most capable foundation for Apple Foundation Models and is excited about the innovative new experiences it will unlock for Apple users. Apple Intelligence will continue to run on Apple devices and Private Cloud Compute, while maintaining Apple’s industry-leading privacy standards.

Jeff Johnson:

How much did Apple have to pay to get Google to say, “Apple’s industry-leading privacy standards”?

Dan Moren:

Gurman has also previously reported that those delayed Apple Intelligence features are likely to make their debut in iOS 26.4 this spring.

It’s unclear exactly where in the timeframe we are. Given that 26.3 is already in beta, and 26.4 is expected in a few months, it’s possible that work has long since started on this, even if it’s only being officially announced now. Even with the leg-up provided by Google’s models, it seems unlikely the company could simply roll in that tech for a feature due out in short order.

M.G. Siegler:

Sort of weird that they would announce such a big deal this way rather than official releases/interviews/etc, then again, the talk has been – at least on Apple’s side – to downplay the partnership. We get it, it’s sort of embarrassing to have to outsource your work in such a key aspect of technology, let alone one you believed you were at the forefront of not that long ago, at least with regard to Siri.

Kyle Hughes:

The Google deal is now necessary because of past mistakes but it is far from ideal—Apple needed this all in-house for years. It will be very difficult to compete with Google on integrated, optimized software products, and they will be paying Google for the opportunity to compete with them at all. Knowledge work is going to look fundamentally different once Google does Claude Code for Google Workspaces.

Previously:

The Struggle of Resizing Windows on Tahoe

Norbert Heger (Mastodon, Hacker News):

Since upgrading to macOS Tahoe, I’ve noticed that quite often my attempts to resize a window are failing.

This never happened to me before in almost 40 years of using computers. So why all of a sudden?

It turns out that my initial click in the window corner instinctively happens in an area where the window doesn’t respond to it. The window expects this click to happen in an area of 19 × 19 pixels, located near the window corner.

[…]

But due to the huge corner radius in Tahoe, most of it – about 75% – now lies outside the window[…]

Jason Snell:

That’s right, folks, the solution to resizing the corner of a window in Tahoe is to click outside the edge of the window. I can’t even.

Jason Anthony Guy:

The accompanying gif of him grabbing a plate captures the experience perfectly.

Rui Carmo:

The annotated images (green “expected” area, blue dot, and the “accepted target area” sitting in empty space) make the point better than any amount of hand-waving, and we need more of this to make it obvious that Apple needs to reverse course on the whole thing.

Gui Rambo:

Yes! All the time. The opposite also occurs: trying to click something behind a window and accidentally resizing the front most window instead.

Tony Arnold:

I’ve noticed that resizing windows on macOS Tahoe seems to fail 2-3 times each time I perform the action. How did Apple break so many interactions in a single release?

Garrett Murray (Mastodon):

I have struggled with this every single day since Tahoe was released. I fail on nearly every first attempt at resizing a window.

[…]

Imagine taking one of the most core, we-take-this-for-granted features of a windowing system and throwing it away. And why? Oh, because iPhones have rounded corners and therefore so should all windows on every Apple platform.

Joachim Kurz:

Things like this make me want to switch to Linux and build my own Desktop environment and window manager.

Like, gather all the macOS devs who still understand how desktop UX is supposed to work, take an Apple HIG from the 90s or and let’s build ourselves a new home.

And when we are done with that (shouldn’t take longer than a couple decades, right?), we fork the open source component from Android and do the same for mobile UX.

Mario Guzmán:

ugh this is one of the things that drives me most insane in #macOSTahoe. Basic desktop-isms are just so broken. I fear that more and more folks who don’t understand the history of the desktop are running the show at Apple. I hope I am wrong but then what explains this mess?

John Gruber (Mastodon):

One can argue with the logic behind these changes, 15 years ago. I’ll repeat that I think it was a grave error to make scrollbars invisible by default. I would argue that while the visible grippy-strip isn’t necessary, it’s nice to have. (As noted above, its presence showed you whether a window could be resized.) But there was, clearly, logic behind the decisions Apple made in 2011. They were carefully considered. The new logic was that you no longer look for a grippy-strip to click on to resize a window. You simply click inside the edge of a window. And of course Apple added a small affordance to the hit target for those edges, such that if you clicked just outside the window, that would count as “close enough” to assume you intended to click on the edge. Most users surely never noticed that. A lot of nice little touches in UI design go unnoticed because they’re nice little touches.

Until MacOS 26, most of the hit target for initiate the resizing of a window was inside the window. Because, of course, right? Even though MacOS (well, Mac OS X) stopped rendering a visible resize grippy-strip 15 years ago, the user could simply imagine that there was still a grippy area inside the lower right corner of every resizable window. It would make no sense whatsoever for the click target to resize a window to be outside the window. Why would anyone expect that? It would work against what our own eyes, and years of experience, are telling us. You pick up a thing to move it or stretch it by grabbing the thing. Not by grabbing next to the thing.

diskzero:

I worked on Finder/TimeMachine/Spotlight/iOS at Apple from 2000-2007. I worked closely with Bas Ording, Stephen Lemay, Marcel van Os, Imran Chaudry, Don Lindsey and Greg Christie. I have no experience with any of the designers who arrived in the post-Steve era. During my time, Jony Ive didn’t figure prominently in the UI design, although echoes of his industrial design appeared in various ways in the graphic design of the widgets. Kevin Tiene and Scott Forstall had more influence for better or worse, extreme skeumorphism for example.

[…]

Here is my snapshot of Stephen from the time. He presented the UI ideas for the intial tabbed window interface in Safari. He had multiple design ideas and Steve dismissed them quickly and harshly. Me recollection was that Steve said something like No, next, worse, next, even worse, next, no. Why don’t you come back next week with something better. Stephen didn’t push back, say much, just went ok and that was that. I think Greg was the team manager at the time and pushed Steve for more input and maybe got some. This was my general observation of how Stephen was over 20 years ago.

I am skeptical and doubtful about Stephen’s ability to make a change unless he is facilitated greatly by someone else or has somehow changed drastically. The fact that he has been on the team while the general opinion of Apple UX quality has degraded to the current point of the Tahoe disaster is telling. Several team members paid dearly in emotional abuse under Steve and decided to leave rather than deal with the environment post Steve’s death. Stephen is a SJ-era original and should have been able to push hard against what many of us perceive as very poor decisons. He either agreed with those decisions, or did not, and choose to go with the flow and enjoy the benefits of working at Apple.

Previously:

Mac Screenshot Utilities

Adam Engst:

Here are the unique features that keep me using multiple apps for my screenshots.

[…]

Most of the time, I dismiss floating shot windows immediately, but they can be useful for referring to a screenshot—such as the contents of a menu that I can’t keep open—while writing. Floating shots are also handy for making simple edits and annotations without opening the file in Preview. The feature I value most, though, is one that ScreenFloat developer Matthias Gansrigler added last year—the option to export an image with an added border.

[…]

CleanShot X is a thoroughly capable screenshot utility with editing and annotation features, but it also offers a feature I haven’t seen elsewhere: the ability to combine screenshots.

[…]

I still occasionally press Command-Shift-5 and use the built-in macOS screenshot utility to create a screenshot of a window with an open menu. In these screenshots, I don’t want shadows around the window, but I do want them around the menu, which otherwise looks weird. This requires a multi-step process that involves capturing two separate screenshots and compositing them in Preview[…]

Previously:

Cloudflare Defies Italy’s Piracy Shield

Jon Brodkin:

Italy fined Cloudflare 14.2 million euros for refusing to block access to pirate sites on its 1.1.1.1 DNS service, the country’s communications regulatory agency, AGCOM, announced yesterday. Cloudflare said it will fight the penalty and threatened to remove all of its servers from Italian cities.

AGCOM issued the fine under Italy’s controversial Piracy Shield law, saying that Cloudflare was required to disable DNS resolution of domain names and routing of traffic to IP addresses reported by copyright holders. The law provides for fines up to 2 percent of a company’s annual turnover, and the agency said it applied a fine equal to 1 percent.

The fine relates to a blocking order issued to Cloudflare in February 2025. Cloudflare argued that installing a filter applying to the roughly 200 billion daily requests to its DNS system would significantly increase latency and negatively affect DNS resolution for sites that aren’t subject to the dispute over piracy.

Matthew Prince (Hacker News):

Yesterday a quasi-judicial body in Italy fined @Cloudflare $17 million for failing to go along with their scheme to censor the Internet. The scheme, which even the EU has called concerning, required us within a mere 30 minutes of notification to fully censor from the Internet any sites a shadowy cabal of European media elites deemed against their interests. No judicial oversight. No due process. No appeal. No transparency. It required us to not just remove customers, but also censor our 1.1.1.1 DNS resolver meaning it risked blacking out any site on the Internet. And it required us not just to censor the content in Italy but globally. In other words, Italy insists a shadowy, European media cabal should be able to dictate what is and is not allowed online.

[…]

In addition, we are considering the following actions: 1) discontinuing the millions of dollars in pro bono cyber security services we are providing the upcoming Milano-Cortina Olympics; 2) discontinuing Cloudflare’s Free cyber security services for any Italy-based users; 3) removing all servers from Italian cities; and 4) terminating all plans to build an Italian Cloudflare office or make any investments in the country.

Ernesto Van der Sar (Slashdot):

Launched in 2024, Italy’s elaborate ‘Piracy Shield’ blocking scheme was billed as the future of anti-piracy efforts.

To effectively tackle live sports piracy, its broad blocking powers aim to block piracy-related domain names and IP addresses within 30 minutes.

While many pirate sources have indeed been blocked, the Piracy Shield is not without controversy. There have been multiple reports of overblocking, where the anti-piracy system blocked access to legitimate sites and services.

Previously: