This reevaluation postulates that the participants didn't deviate by mistake, but deliberately. The participant could have waited for the respondent to be in a state in which they could answer. (Reminder: the exercise was officially about answering questions, not enduring shocks).
Instead, most participants rushed through, most likely to end their own negative experience. Which is much more nuanced that "gosh, they told me to do it."
It just feels ancient and weird now that I can tap every screen I own, except my Mac. I don't want to replace the Mac's keyboard & mouse with a touchscreen, I would simply like it to support touch.
(This also made me realize the impending obsolescence of the Studio Monitor XDR: no touch support.)
My iPad is mounted next to my Macs. I use it as a media player, checking deliveries, personal messages when I'm on my work laptop, and such. All of that is done via touch. When I need to flip over to my Mac to do the same thing, I have to use a 40 year old interface (a mouse).
It's not hard. I don't think we need to make everything touch-size on Mac. Small icons & buttons are perfectly fine in a production environment, and they're considered to be accessible. Just let us touch the screen.
I've never worried about AppleCare for my Apple products, until this year when I signed up for AppleCare One. I bought a few new devices, including the Studio Monitor XDR. For the XDR alone it's worth it, since replacing the screen is a multi-$1k repair.
> If you want a repairable machine, buy one. They exist. Others have already mentioned Framework
But that means Windows or Linux, not macOS. There's serious trade-offs that you're dismissing because you personally don't need macOS, but that's not the case for everyone.
I run into bugs every day. It wakes, and has a black screen not wallpaper. Change spaces and the focus is wrong for half a second. Login screen is a pain because it collapses all users together. Notifications don’t scroll if they stop scrolling when the cursor is over a gap between them. Something on the system constantly eats disk space, and I think it’s the system updates. If I dock two apps in one space, sometimes one is black. If I zoom out to the Spaces overview it shows fine in the preview though. In the Terminal if I close a tab it can focus an entirely different window.
I could go on for hours. It’s a buggy mess these days and I miss Lion and Snow Leopard desperately.
Yes, these got a lot worse after Tahoe. The past few versions have all had issues on multiple machines.
None of this sounds like a hardware error. Something like notification scrolling is simple bad programming and bad QA. You scroll the list of them, but when the mouse cursor ends up on a gap between them, the new scroll event doesn't apply. They're all individual even though shown together.
Or a black screen on wake - that has the mouse cursor and login prompt, it just sometimes doesn't load the wallpaper or does it slowly. Not hardware - just something buggy. It's unbelievable when I compare to Leopard or whichever version it was introduced the rotating 'cube' of login screens, which always had wallpaper and loaded fast. Here we are fifteen years later with incredibly better hardware and the thing lags.
Nothing mentioned in the previous comment is indicative of a hardware problem. If you think I'm wrong, please describe a plausible mechanism to cause any of the problems described above. They all are plausibly software bugs. I mean, Apple hardware is not really any better than any other piece of fallible hardware, and their OS has been a buggy mess since Apple DOS. Most pieces of software as large as an OS are buggy in many ways, and Apple has not been proven to be the exception.
Oh, I completely agree. But they can get away with it because we depend on the platform more than the individual apps.
And yes, Tahoe is shiny hot garbage piled on top of so much broken software, just to push an effect trick. I'm not sure how I feel developing with SwiftUI when Apple clearly can't make it work for their own apps.
That only reinforces Apple being assholes. They are perfectly capable of delivering security updates to ios 18, they just choose to not do that for phones that can run 26.
By the way does that mean you can root a phone that's on iOS 18.6? :)
> The problem that fucks us over is that Mac OS only has to be better than the competition.
I'm with you here, but I'm having a _much_ better time on my Linux machines (KDE and Cinnamon Mint) than on my (unbelievably-powerful-but-for-what) M4 Max MBP. It's so much cleaner, even without having upgraded to Tahoe, and imagine that I don't even like tinkering that much, it just works.
Well, Cinammon is the windows manager for Mint, it's the barebones experience that's the closest to Windows (?) style, it's mostly what you see is what you get, but still very customizable.
KDE used to be extremely buggy 5-6 years ago and since testing it on my Steam Deck, from my experience, this is no longer the case. It's a bit more feature-rich and flashier than Cinnamon.
> Can I run KDE on a box that idles at 10 W and never turns the fan audibly on?
No laptop I'm aware of will do this, no idea about ARM adoption.
Personally I'm glad to have a windows manager that doesn't force dumb decisions down my throat. On MacOS I have to wait for half a second for the focus to land on the next window when I switch desktops, the only workaround exists as a minor feature recently introduced to BetterSwitchTool called instant desktop switching or something. And it's to be mentioned ofcourse that for all similar fixes you _must_ give full screen recording and accessibility permissions to 3rd party software. And don't get me started on the stupid windows management (maximize != full-screen, minimized windows not recoverable with keyboard only etc)
Actually... their MCP reflects more than just supporting AI. It demonstrates the future of closed, walled garden MCPs.
While Figma advertises that their official MCP "can now write directly to your Figma files", in reality it is restricted to create and read (as in CRUD), but not update nor delete. Currently, there is only one option to edit/update using the Figma MCP and it requires going through a third-party service with its own subscription and tiny token allocations.
Meanwhile, several developers have figured out how to use Figma's plug-in system to work-around these limitations, for a more robust CRUD MCP solution.
I don’t think so. Your product / tool has to be extremely specialized and deeply necessary to pull of a walled garden MCP. The more likely alternatives are that someone else comes along with a better (open) integration, the model internalizes your tool’s capabilities, or the AI labs themselves build 1st party competitors.
Figma has demonstrated that kind of aggressive lock-in many times. For example, they couldn't get enough companies to subscribe to FigJam and Slides, so they simply increased Figma's subscription price by that amount, and then said those apps are included for free.
BTW: that's usually illegal, but with the current administration, it's a Tuesday.
I live in Oakland, and the Easy Bay has had its share of random outages without incident. The last outage was just a split-second blip, but it broke a $1k computer monitor.
I'm pretty sure it comes down to radio vs interactive music licensing. A general radio license doesn't allow users to pick the track they want to hear. They only get a shuffled playback and face other limitations like "can't play an album all the way through". Interactive licensing allows users to pick exactly what they want, including playing full albums, but it's much more expensive per track.
It appears that Spotify's engines use a mix of these licenses to reduce costs. Since AI isn't explicitly user-made selections, it's quite possible that the AI playlist generator is limited to a radio license model for playback, simply to save money (considering the additional cost of providing AI).
Instead, most participants rushed through, most likely to end their own negative experience. Which is much more nuanced that "gosh, they told me to do it."
reply