[freditup]

It's a bug for sure, but conclusions like this are over the top for a single small bug:

> This isn’t an Apple which has any concern over the quality of its products, or for its users. It’s just another leviathan corporation which has stopped caring or taking pride. One small bug reveals a deep and pervasive problem.

I'd rather see a more measured approach to drawing conclusions from a single anecdote.

[falcolas]

Straws break camel's backs. You can be sure this isn't the only, the first, or even the last time this particular developer has found a major bug. It's also safe to assume that past bugs they have reported (especially small usability bugs like this) have languished, or been closed as "will not fix".

At some point, the back is broken, the developer gives up on trying to help an obscenely profitable company QA their own products, and rants about the lack of care being shown.

[sixstringtheory]

The process for even submitting bugs is time-intensive, so much so that I started keeping a TODO list of bugs to report, which I never found the time for and wound up stopping even writing new bugs on it because I couldn't keep up.

[protomyth]

If this was the only item, I would agree with you, but it isn't. Finder is buggy and broken since Mavericks (along with some bugs that look like the got rebroke in [edit]10.14[/edit]). Each new version of Mac OS breaks more stuff. This is exacerbated by their hardware failures and constant "only affects a small number of users" line that gets old. Its a constant stream of breaks these days and they need to start looking at the details.

[rectang]

My 2012 MacBook Pro Retina has been more stable on Mojave than on any previous OS. It used to crash at least once a week; at the moment `uptime` tells me it's been 21 days since a reboot.

I attribute this to improvements in the reliability of Airplay: my machine used to be prone to crashing after connecting via Airplay (either sound only or mirroring) to my old Apple TV.

I'm sure other things have been broken along the way, but it seems to me like Apple is tackling hard problems at the OS level and making progress.

[protomyth]

Airplay is something iOS uses, so I would expect it to get fixed. Finder and Keyboard Shortcuts are Mac OS only, and it shows in its lack of testing. I don't think Apple is tackling the hard problems unless it benefits iOS.

[duxup]

Yeah the "Apple doesn't care about users" line of thinking for one use case or bug here or there is a bit much.

Personally I've introduced bad ... choices because I cared about users a few times. It just was a mistake on my part, and yet the whole time I was thinking "this will be better for the user".

[slantyyz]

>> Yeah the "Apple doesn't care about users" line of thinking for one use case or bug here or there is a bit much.

To be fair, a lot of people choose OSX over other OSes because Apple has the reputation of "sweating the details" in both their software and their hardware.

Some of those people in particular are now noticing that the attention to detail may not be like it was, so it is unsurprising that some are complaining over seemingly little things even when the product as a whole might still be better than its competitors.

[PhasmaFelis]

Yeah, the bet where he basically says "I refuse to report this bug to Apple because they obviously know about it already and are maliciously ignoring it" is just weird.

[Supermighty]

I completely agree. No one sets out to create bugs in their software. I'd give the engineers working on this the benefit of the doubt versus a grand conspiracy of product apathy.

[falcolas]

No-one sets out to create bugs, but these days it feels like nobody sets out to proactively identify and fix bugs either.

Expecting the customers of obscenely profitable companies to QA that company's products (for free) is silly.

[Supermighty]

You paint a picture of Apple ignoring all QA responsibility and pushing it on the users, only to later ignore their requests. Surely this is not the case. It's just another bug that slipped through. It doesn't have to be the result of a greedy corporation cutting corners.

[falcolas]

>another bug

>slipped through

At what point do we hold companies responsible for their products? At what point should we, as software developers, hold ourselves responsible for our products?

I think it's entirely reasonable to answer "when the company is a multinational, highly profitable company" and "when they are among the brightest software developers in our generation"; "another bug" "slipping through" should not be considered to be acceptable.

[michaelmrose]

Slipped through for a year?