Take basic functionality - a phone app (calling). After certain audio sessions use (calling via WhatsApp) I can’t make regular calls over cellular - the UI app immediately cancels the call. Only reboot helps.

Or notes - for many years/iOS versions, they lived with a bug where a text note may just become blank - and only restarting Notes app makes it visible again.

Or AppStore - if an app has to be updated (I have auto updates off) - and I press Update - it gets downloaded, installed - and then AppStore is back to showing “Update” button! If you just go to the app, it’s a new version. But if you press that “Update”, it will redo update from scratch.

Sometimes I’m so frustrated, and thinking of my options - it’s either move to Android, or go get hired at Apple with a mandate to fix bugs in various products… but knowing Apple secrecy culture/silos, it’s not going to work, and requires change in their hiring process/perf review/QA.

That's extremely serious because the call you're trying to make could be an emergency call. A bug like that would have top priority in the org I used to work in. If I'd had to guess it cancels the call because there's a crash in a process somewhere. Possibly because of audio handover between apps.

I’ve only ever noticed maybe like a few actually bothersome bugs in the however many years I’ve been using iPhones which is pretty impressive.

Anyway, hope they get it together. Performance and optimization are a very difficult and very thankless job that might not get you promoted the same way cool sexy feature work does. Such is corporate life I guess.

I face none of the issues on my Samsung S23 phone, which the parent commentator describes - no issues in phones calls (I make 4-5 calls daily, mix of WhatsApp & regular calls), no major issues in Google Keep (which I use 2-3 times daily, specially never of a note becoming "blank"), and again no major issues in the Google App Store or updates (which I use on an average once a week).

So maybe, the software quality varies by user experience rather than one platform being universally better.

As for all Apple software, I might use Preview or Numbers (spreadsheets) on occasion, and I'm forced to use Finder, which I hate. And Terminal works well. I avoid Safari.

Apple "PC" hardware is solid. I use third party apps though, little Apple software, there are better alternatives. I've used Android since the HTC Dream (I think it was the first Android phone in the USA) and have stuck with Android since, with few problems.

Edit: I thought the Apple Vision Pro would be interesting (I couldn't justify the expense) but I saw the value supposedly would be greatest for those fully bought into the integrated Apple app ecosystem and iCloud. I'm not the target user.

Same. I have two "deal-brakers" when it comes to notebooks: 1) it's got to sleep consistently and without problems when I close the lid. 2) it should be silent when I'm doing simple things or nothing at all.

I have never seen a Linux or Windows laptop that does these things well. Even Intel MacBooks would spin up the fans seemingly at random. I don't think I've ever heard the fan in my M1 MBP. I'm looking forward to the new M4 MBA to replace an older Windows 10 laptop, which spins up its fans all the time, and sometimes doesn't sleep, sucking the battery dry in the process.

Had to swap the WiFi module to get the power management to work properly.

I'm triggered. How many times have you reached for the 'end call' button, but the other person ended the call a moment earlier than you, and as you press down the screen immediately flips to your "recent calls" screen and you call a random person straight away?

This is such a common and terrifying experience for me, and yet it's been the default UX on the Phone app since probably day 1.

and this is such an easy fix, just don't make components touchable for X milliseconds after they are visible, some value below average human reaction time.

this could of course get in the way of people quickly navigating via muscle memory, but there's a probably a threshold where it can prevent one without affecting the other.

Reminders too. For at least 5 years, creating multiple reminders in a certain order will not create multiple reminders, and will just append the text to the end of the first one. Surprise — hope you didn’t set any important reminders in that batch!

And the great thing about their standardization between iOS and macOS code means the exact same bugs exist in both versions. Yay.

Sometimes 3s will pass before I even see anything after I've already typed in my search term (I'm always searching for a local app btw - it's how I open apps).

It's like it waits on an http request for every keystroke.

Also, you used to be able to search for an app in any of the secondary languages you have in your settings. Which is great because apps have different names in different languages (Settings vs Configuración vs Réglages), so it would be annoying to have to remember which word to search based on which language is primary. For years it would show you multilingual results (e.g. you can search for "Settings" as long as English is one of your secondary iPhone languages yet "Configuración" or "Réglages" would still show up).

It was the sort of polish I came to expect from Apple. Well, that stopped working a couple years ago.

Those aren’t options, they’re fantasies. Like dreaming of suing out of existence a company that wronged you, or fixing the world by ruling it, or winning the lottery without playing.

Android isn’t perfect either, it’s a different set of frustrations. And why would Apple ever need to hire you for that specific task, do you really believe there aren’t engineers inside just as frustrated as we are?

The way I see it, the yearly release cycle is to blame. No one inside the company has time to do anything properly anymore. Features are announced and rushed every year, and we’re reaching the point where by the time something which was announced at a WWDC is out of beta, we’re preparing for the next one.

What these companies need to do is slow down and stop chasing every shiny thing. You know, like Apple used to do with macOS. Tim Cook needs to go.

I'm not saying nobody can be like Steve Jobs, but Steve Jobs was an anomaly when it comes to C-Levels, and even when it comes to management in general, at least from reading things like www.folkore.org and interviews with people who worked with him.

And I'm not even talking about talent or vision or whatever, it's just about saying no to pointless features that are there for someone's ego or so that someone can get a promotion.

https://mjtsai.com/blog/2025/02/26/testimony-on-external-pur...

I’m not saying anyone will be better than Tim Cook, I’m saying he’s actively bad. Will his successor be actively bad too? Maybe, but the sooner we find out, the better.

The general publics opinion of Apple is that they are golden and untouchable, the best tech company out there. The reality is much different.

- Because a lot of journalists are Apple fanbois

- The press publishers don't want to sour relationships with Apple (because of advertising deals)

- Publishing bad things about Apple would infuriate the many Apple fanbois among the readers, causing a shitstorm against the medium

The advertising deals with apple are not that lucrative, iirc.

So bad reviews are avoided to ensure the media gets the early review clicks.

Not "never", but it is indeed my observation that the press is much "nicer" in their reporting and much more "forgiving" to Apple than to other similar companies.

In some circles, this observation already has become a running gag when the pen pusher is again too impressed of some Apple marketing.

https://en.wikipedia.org/wiki/Criticism_of_Apple_Inc.

There is even a joke amongst Apple developers who all know that Apple’s claim of “don’t go to the press, it never helps” is a blatant lie as it’s the one thing that works.

So why isn't that happening?

Yes, you may implement a solution more efficiently by not overengineering it. But at some point constant seek to reduce "complexity" so that more features fit into sprint (funny how story point measure complexity, not time, but sprint is sized in both time and SP capacity) is bound to hit feature completeness. Once you cross over that metaphorical Rubicon it's game over - quality starts to slowly go downhill.

You will not notice it immediately. That edge case that was ignored may not surface for months or years. It may take several idiosyncrasies to line up for a feature to be declared FUBAR. At some point that technical debt does bite you back, but at that point the process (tm) has already optimized away most if not all opportunities for deep refactorings fixing previous rushes to deliver.

Furthermore, Sprint Planning/Refinement are just innocuous ceremonies whose only aim is to facilitate productive discussion between a Product Owner/Manager and an Implementation team as regards delivery timelines and priority ordering thereof. Done properly, it allows a pragmatic approach to achieving a predictable software delivery cadence via mutual compromise.

If the process turns into 'fit as many features into the sprint as possible' at the expense of Performance/Stability/Functionality or Technical Debt accumulation, you're really just doing the 'fast' version of Cheap/Fast/Good Waterfall Project Management.

I never buy products when they are first released. I prefer to wait at least 3-4 months so that production has had time to tweak all the settings and weed out the funky first component deliveries. Also the software devs will have fixed the worst bugs by then.

At many places where I've worked, the mentality is: "If that bug didn't block last year's release, then why would it block this year's release?" So it survives one release, it never gets fixed.

I don't see a connection between yearly release cycles and a broken notes application. They shouldn't be doing anything that is particularly affected by such changes and the problem they are trying to solve has been mostly solved for 40+ years now.

While it certainly applies to some things, there's a different, bigger issue happening as well.

My understanding is that Apple outsources loads of software not seen as "critical". I think that's the first place for them to look.

Some of this could be resolved by open sourcing their less important apps like Files, Notes or Home which barely ever get touched, yet are full of quirks and bugs. Those apps should be public examples of good SwiftUI coding.

Who is dealing in fantasies now, friend? :)

Apple's software really isn't in crisis. It's just very low quality relative to what people who've written software for a living know to be possible.

But it doesn't matter - Apple is a prestigious jobs guarantee program for rich kids first, entity that delivers value to consumers second.

It's not that they're chasing shiny things. They're cosplaying competence and they genuinely don't know it. They think they're actually competent, elite really, because they attend 'elite' schools, get good grades and go work at the 'best' places.

They have it ingrained in them that anything a poor person says can be disregarded because poor people are losers, because they're poor. They're an unintentional suicide cult. They genuinely don't know it. You can't convince them of anything because they are rich. If you complain - go see a therapist, there's something wrong with you.

You can youtube search Garys Economics. It's a poor kid who slipped into the rich kids club and defected. It's quite eye opening.

I said they need to, not that I think they will. But they have in the past. There is a reason Snow Leopard is still lauded today.

> It's just very low quality relative to what people who've written software for a living know to be possible.

No, it’s low quality relative to what Apple users came to expect. There was a time when “it just works” was an aspirational goal which permeated their decisions and you could see the results.

> Apple is a prestigious jobs guarantee program for rich kids first, entity that delivers value to consumers second.

What a bizarre conspiracy theory. No company gets to that stratospheric level of success by making hiring incompetent rich kids their primary goal.

By the way, I did catch the rant you posted before. I tried to reply to it but after writing it up and hitting reply, you had already deleted it.

You've gone ahead and made it the first goal in the context of all goals a company has (thus making it 'primary').

That's not a legal move - switching contexts and claiming that the sentence plucked out of its original context and inserted into your context becomes a 'conspiracy theory'.

That's on you, not me :)

And yes, I edit my posts plenty. Including this one.

It goes back to 2019 - certainly more than 100 calls

In Calendar (macOS) create a new event.

In the start or end time, type in the Minutes field, but type slowly.

For example, type "2" pause a bit, then type "1"

If there's more than ~300msec pause between the two keypresses, the 2 changes into "02" and then the 1 overrides it, so you end up with "01" instead of 21.

Works with any two kepresses. Same problem in the date fields.

Completely wrong, and super bad for accessibility.

From a developer perspective many of these inconsistencies are rooting from inconsistent access patterns - operating system (ABI?), applications (ICP?), remote (TCP, HTTP, LDAP, FTP, ...?). All of these are "execution" or "information" but have to be programmed against differently.

s/ignorance/apathy

1. If you copy some text

2. Select other text

3. Paste the text you copied to replace the selected text

Notes will crash. This has been known for years.

Also if you turn off all suggestions in Spotlight on iOS and just use it as an app launcher, it will still take seconds for Spotlight to show you the results. For something that's supposed to be an indexed look up.

I don’t mean to be rude, but that’s how an iOS intern would implement it.

A bad one maybe

Not sure about iOS, but Android has sort of magnifier when users start to select so they can clearly see what characters they are selecting. It definitely helps. However, what I should want is some sort of arrow keys that I can press to select characters instead of relying on my fingers.

I wish they implemented backspace like they do with fine scrubbing on seekbars. i.e. you could move your finger up & down while holding the backspace key to select the granularity of deletion between letters, words and paragraphs.

No, Ellie isn't a typo and I didn't actually mean Emma.

Can't think of any more at the top of my head ... it feels a lot like Windows, where there are a bunch of eternal bugs one just sort of knows and works around, even though it's a kind of shitty and occasionally very frustrating experience.

- on a recent macOS version, right click on the desktop, select 'change wallpaper' => the new settings panel opens

- click on 'Custom Color'

- now hold and drag around the 'color cursor' in the color selection circle for a few seconds

- stop dragging and notice how the color cursor continues jumping around erratically (it's impossible to actually select the exact color you want)

- same thing happens when using the linear slider below the color circle

This bug doesn't lurk deep in some obscure part of the settings panel, it's the only way to change the desktop background color. A QA specialist would stumble over this in 5 minutes of trying to break the app.

I made it a hobby to check this bug after each OS update, it's broken since the new settings panel was introduced in Ventura. As a good citizen I also wrote a Feedback Assistent ticket (FB13805690 - 21-May-2024) with attached screen recordings and all, but of course I could just as well have sent that report into a black hole :)

BTW I have found a workaround using BetterDisplay and an EDID override (to more closely match what the monitor is actually telling macOS).

Related bug: macOS defaults to variable refresh rate when available instead of remembering my choice of 144hz. This is confounded by my hub (Caldigit TS3 Plus), which has trouble with variable refresh rates that result in a black screen.

The cherry on top: either I use a HDMI cable and deal with BetterDisplay forcing RGB to fix YCbCr, or a black screen when using DP through my hub due to the above bug.

Sometimes I wish Apple would get broken up just so macOS could have a chance at getting more love.

Example: iCloud Photos syncing is complete crap on macOS. If it has synced recently it’s not going to do it again. So you sit there like an idiot waiting 10 minutes for a photo you just took on your phone e to show up. When a pull to refresh or refresh button would have fixed it.

https://www.anker.com/products/a8317?variant=42329259475094&...

Does your adapter work at 120Hz without updating the firmware? If it does, does it support HDCP?

Yeah I had to flash the firmware on the Anker dongle, following this guide: https://forums.macrumors.com/threads/dp-usb-c-thunderbolt-to...

I just tried streaming 4K through the Apple TV app on my M1 Macbook Pro and no issues, so I'm assuming HDCP works.

As much as I like the integration between the phone and macOS I like the idea of desktop Mac getting more love.

I cannot get osx to actually output at 1080p, all it does is output at 4k and scale the result.

The downscaling in the projector adds input lag and just drives me crazy. I really wish they'd just let you control these things rather than poorly guessing.

I didn't know about better display, I guess I should try it and see if it can fix this problem.

FWIW, here's the hacked script[0] which only keeps the EDID data patching part. Be warned it's very hacky with the base64 EDID to be patched hard-coded in line 8 of the script. It prints out the patched EDID base64 which should be entered back into BetterDisplay (which is also where you can get the unpatched base64 EDID).

[0] https://gist.github.com/karmakaze/f795171a6a795491e754c3d092...

Also extra fun is guaranteed if one end of the video cable is encoding with e.g. BT.601 primaries, while the other end is decoding as e.g. BT.709, or vice versa.

[1] https://www.microsoft.com/en-us/research/wp-content/uploads/...

2560x1440 is a strong indicator of a monitor, but 4k over HDMI tends to get detected as a TV

BetterDisplay provided a workaround, but it needs to be selected every time the monitor is hooked up.

(I guess that's normal for Apple stuff nowadays - when I hook up my ipad to my projector, I need to tell it every single time not to use the audio output of the projector, but keep using the bluetooth speaker.)

also - it's such a bummer that they have decided to shit the bed so hard on software at a moment when their hardware lineup is arguably at its pinnacle. like, the hardware has been firing on all cylinders since M1 but the software degradation is making it less and less pleasant to use.

I'm not saying this is what happens. But it's scarily plausible and it really shouldn't be.

Chrome removed ublock origin for me today and I thought to myself why am I even on this OS anymore? What’s keeping me here? Decided to use the outrage over that to just make a clean break from Windows too.

I installed Ubuntu tonight, but this time I’m sticking with it. It already feels so good to have the software behave in a way that makes sense and isn’t some dark pattern meant to harm me and extract value somehow from me.

[1] https://getaurora.dev/

All non-core software is provided by Flathub (through the Discover app) and Brew (for cli apps). Both have worked flawlessly for me as well.

Ubuntu pushing snaps like MS was the last straw.

Dude... Mint, Arch / Manjaro, Void, even Alpine is better. Plenty of good and very lean+mean options out there.

Ubuntu is the Windows of the Linux world. Has been for several years now.

Try looking up what Canonical did and still does with the Snap store.

An example: new PowerToys https://github.com/microsoft/PowerToys/

The FancyZones "window snap" UI takes upwards of half a second to activate when dragging a window and the Zone Editor is at around 5s. All in all it is only very slightly less buggy than 3rd party tiling WMs like komorebic.

The PowerToysRun utility input is extremely variable, takes between 1 and 20(!) seconds. A lot of the plugins shipped with it simply don't work or have no suggestions/hints once you enter their prefix. The search relies on WindowsSearch, which is about 500x slower than https://github.com/sharkdp/fd and has not improved since Win7. Who cares, nobody ever searches for files, right? As a whole, PTRun is simply worse than https://github.com/Flow-Launcher/Flow.Launcher which uses the same UI kit as far as I can see. WTF?

There's another app that does this in the registry I think, but I keep forgetting the name of it.

Go have a tour on Github for the endless collection of issues, some of them 5 years old, when Project Reunion was announced.

Unfortunately, to stay on top Apple doesn't have to do well for the customer. They only have to do better than wintel/android machines.

So far, I am not willing to ship anything in SwiftUI. I don't think it's up to the task.

I know that SwiftUI has some native wrappers, like maps, but the way that SwiftUI works, is so radically different from UIKit, that I think mixing them is problematic.

Open Activity Monitor, and type in System Settings into the search. Then open the Settings app and press the down arrow key through all of the menus. You'll notice that each one of them appears as their own line item in Activity Monitor until you quit Settings, and if you keep going up and down through the menus, it'll (probably) get slower and slower; it seems like there's a memory leak or something going on there, and my hunch is that each old settings menu was thinly wrapped in a SwiftUI view and gets launched as soon as you click its nav item.

So is Swift just too crappy for this kind of UI, that accesses low level system stuff? or are the devs just incompetent? Who knows…

I think Apple has decent QA for low level stuff (remember how they quietly converted every iphone to APFS and back just to test that it will work later) but bad QA for final GUI.

Most of cocoa/objc stuff was written long ago and back when QA was better. If this was cocoa and objective c today it would be equally buggy.

True, imo.

> But even that doesn't matter > Most of cocoa/objc stuff was written long ago and back when QA was better. If this was cocoa and objective c today it would be equally buggy.

I don't think I agree about this entirely. Although you can write unperformant code in any language and framework, SwiftUI is a different world of heavy abstraction. Writing a list view in AppKit using the documentation available allows for and encourages much more deliberate implementation in such a way that it'll be an almost night and day difference compared to the likely NavigationSplitView they're using in Settings. It's an inverse relationship with performance that SwiftUI takes; efficiency of piecing together the high level details first, and little to no control or clarity on how you'd optimize for performance.

My hunch is that with Settings, they're using a NavigationView or NavigationSplitView and not letting each view be recreated on selection, so they're sticking around in memory. However, if they were recreating each pane on selection, it seems like the render of the view waits for some kind of I/O, maybe reading their .plist or interacting directly with a system level CLI, which is why there's a delay before the UI renders.

Another possibility is a combo of both, they're retaining the views in memory AND triggering I/O immediately on selection, so the reads and threads accumulate quickly without being released

At least some of them are actually web pages:

https://blog.jim-nielsen.com/2022/inspecting-web-views-in-ma...

Just one anecdote, but some reports definitely get looked at.

I assume this would have landed them in hot waters with EU privacy regulators, so they were very keen to replicate the bug and then have me check if it no longer happened.

On the other hand, the "first screenshot fails to display screenshot preview and doesn't flash the screen" has been in iOS for 3 versions now. I've reported it thrice, and no one has given the tickets a second look, marked it DUPLICATE, or anything. And every time I mention it, at least 3-4 other people comment on also experiencing the bug, so I assume Apple must be pretty aware.

My suspicion is that there's a really gnarly race condition as the root cause, and they haven't been able to find it.

You will never get a response to tickets unless it is affecting a lot of people and they need more information e.g. crash reports.

They are all read/triaged though.

Granted that was over a decade ago, and "no QA team" doesn't mean no testing, but given the numerous bugs in macOS today, and that they almost never get fixed, I'm not surprised.

(FWIW, I do not experience this bug you mentioned)

To be fair, Apple can still pull off the occasional amazing feat of vertical integration -- HDR, APFS, keeping audio latency under control despite the relentless assault of apathy from all directions -- but they never had the same level of consistent drive forward, at least not until a year or two ago when the big push for AI integration started. Apple gets ragged on here, but I think their integration is actually some of the best. They were putting neural cores in chips back when that sort of thing got mocked, not lauded, and every step has been thoughtfully tied in rather than airdropped from a ChatGPT science fair project. But they never got good at building or deploying leading-edge models themselves; I hope they turn it around because this is important.

See my longer comment here: https://news.ycombinator.com/item?id=43249634

You felt a real sense of ownership to the thing that you worked on. You worked hard and fixed bugs because it felt like it mattered, because you thought about how e.g. your mom would end up using the product, and also Steve Jobs would see it, so it had to be great. Also, teams were small. Something would involve only 1-2 people, and then we would look over at Redmond and they'd have dozens of people working on the same thing. The need-to-know secrecy was not just for PR value; it helped keep circles of communication tight, cutting out a lot of noise, so you could just focus. The organization was stable (and relatively flat, around 5 levels from junior engineer to SJ). I think in my 9 years or so there, there were no major reorgs. Avie phased himself out and retired, and Bertrand moved up. The only major disruption was when the iPhone project happened.

Release cycles were annual. Throughout most of the release cycle, it was pretty free up to each team and engineer to decide what to work on and how to prioritize it. Near the end of a release, it would get more and more strict on what you were allowed to change, up to the point where Bertrand sometimes would even ask to see code diffs.

I don't really know what is going on over there now. They have moved to a more agile approach, with more frequent integration checkpoints. In theory this should be better, but I suspect there's less sense of ownership and more of a feeling of a software factory. But it's probably mostly to do with the fact that the systems are way more complex, both the tech and the org, with way more moving parts. Even the programming language itself (Swift) is a moving target. I know (from talking to friends) there's a lot more politics and career-building going on, the kind of corporate douchebaggery that would not have been tolerated under Steve Jobs. People are thinking about RSUs and their promotions, rather than the products.

Ultimately, I think it boils down to this observation by jwz at Netscape, that there's "two kinds of people: those who want to go work for a company to make it successful, and those who want to go work for a successful company." Post-iPhone, Apple has filled up with the latter. A majority of the people at Apple now didn't work there under SJ, and the senior management who did experience that is now aging and retiring. At least from the outside, as a customer and end-user, it feels obvious that the founder-led product-obsessed culture is gone.

Edit: Repro-ed using the additional steps you mentioned below. As someone who handles external bug reports and writes them, it's so often the case that there are additional steps or a specific start state required, which both prevents reproducing the bug and narrows the affected user base.

* in safari private mode, open image picker

* switch to different app (e.g. go to WhatsApp to save a new image)

* go back to safari

the image picker can now no longer be spawned from that safari private tab, you'll have to open a new tab to re enable the image picker.

And god, don't even get me started on how the icons rearrange themselves when you're organizing your home screen / control center. I can't believe they actually shipped it like that and still haven't made it any better.

If you try moving one of the icons anywhere, it snaps back to the top right corner right away.

I haven't found a fix. The only fix is moving the icons away from the Desktop into another folder using a Finder window.

Sequoia 15.3.1 (24D70)

It seems the difference is that with the "custom color" button, Settings applies the colour directly to the background, whereas the plus button at the bottom only applies it when you're done. Applying it directly seems to be computationally expensive (ass various elements of the UI need to figure out whether to render their text in black or white, depending on the colour - would be my guess at least).

I see this Custom Colour thingie at the top-right corner of the Wallpaper section, above a "Show on all Spaces" checkbox and left of a fairly big representation of the current desktop background.

After a bit of tinkering: this Custom Colour element is replaced with something else depending on the current background mode. If you selected a wallpaper image, it shows the name of the wallpaper. If you select a predefined colour, it shows the name of the color. When adding a custom colour, it will show an interactive element which allows to change the color in place, and that shows the buggy behaviour for me.

Ok, this at least explains why other people don't stumble over this as an obvious bug, I assumed it would be obvious, because the first thing I always do on a new Mac is to customize the background color by right-clicking the desktop, and since that moment I have that buggy Custom Colour element sitting there.

Not a great UX either way though.

PS: ...and now after adding a new custom color via the to bottom row of predefined colors, the bug in the 'Custom Colour' widget is gone and nobody will believe me it was ever there. Great :D

PPS: nope, it's coming back after going through the 'desktop => right-click => change wallpaper...' route again, phew.

In a way it's a perfect little example of how a bug can seem obscure to some (most) users/developers but seem glaring and unacceptable to a few (the few who happen to use the relevant feature a lot).

[1]: http://euclid.psych.yorku.ca/SCS/Gallery/colorpick.html

I’ll grant I might just be mole-eyesing it, it’s been a long day.

Look at the state of Xcode, a tool that's fundamental to the iPhone's appeal. Every developer knows that this thing needs a massive rewrite. The word is that nobody within Apple even understands it thoroughly anymore, so it's way past time to strap it on and build a modern tool from the ground up that's maintainable, instead of slapping band-aids on Project Builder indefinitely. Come on, Apple, you can afford to throw resources at this for a year and just get it DONE.

Meanwhile, Apple is letting open, "urgent" QA personnel requisitions sit unfilled for YEARS. We can all see the results.

Data-point of one, but: the new Settings panel is very much appreciated by the non-technical users I support, because it approximates the iPhone settings panel they're accustomed to. Personally, I hate it, but I also like that my colleagues are better able to discover and make changes for themselves. I figure learning new tech is a core part of my job description (but not theirs), so my frustration counts for less than their comfort, so I suck it up.

Xcode, however? I completely agree with you there.

Yes, but code reviewers signed off on it, our unit tests have 100% code coverage and they all passed. It must be okay.

now reopen the wallpaper setting again, click on top right custom color and do this, somehow the behavior is different. Now it change the wallpaper color as you drag over the colors rather than mouseup. My guess is clicking on + button at the bottom is triggering the popup config to update on mouseup, while opening it fresh will configure it to trigger on update, until the + button is clicked.

I mean for god’s sake these morons (yes, “morons”) have not yet figured out how yo sync browser tabs which is something new browsers get right in a few days to few weeks time, and sometimes on top of their incompetently done iCloud and related SDKs.

Apple sometimes comes across as a glasshouse built as marketing, too much money, (sadly) a huge army of fans and loyalist apologists (and not demanding customers), and an absolute lack of decent competition; and the biggest of it — a deliberate attitude of non-openness!

I mean everything Apple is closed! So how can anyone even quantify how bad their iOS is, how smelly their cloud suites are, how ridiculous their security is!! If you can’t see what happens behind a wall and the entity behind that wall has money more than most nations and a PR and tech propaganda machinery rivaling some of “those” nation states, how can you even be sure!

I feel like a lot of the Apple issues come from the fact they keep building on top of iCloud. It’s only very recently that people started trusting the sync.

It’s like MS, where anything built on top of sharepoint is going to be garbage.

https://gally.net/temp/20250304macoswindowopeningposition.jp...