Live data from Hacker News

Mac: Keyboard Shortcuts Killed by Bug

eclecticlight.co

91–100 of 119 posts

Re: Mac: Keyboard Shortcuts Killed by Bug

#91

lol: "The bug has occurred because of a simple programming error using what I believe Apple refers to as an Outline View. The error is that the first column width, containing the command names, has been set too narrow, and isn’t adjustable by the user either. In coding terms, it’s a trivially simple error which should take a few seconds to fix." that makes no sense at all looking at the behaviour described. if you wa…

You began this post with with a sentence fragment and a massive quote from the article everyone just read wherein no particular point required a reference. You used "lol" in written communication which makes you sound like a 12 year old girl texting her friends. You then continued in mid stream and concluded a sentence that you never began. You said "make sure you understand what is a computer" which makes zero sense…

> Your entire communiqe could have been written like do.

It's not clear what was gained by your point-by-point rebuttal (of presentation rather than content), but it was worth it for this unproofread line.

Re: Mac: Keyboard Shortcuts Killed by Bug

#92

Earlier quoted context omitted.

Nope. Craig’s directs are responsible for apps and all the platforms those apps ship on or cross-platform technologies that power apps.

I'm not sure what point you are trying to make here. macOS is a product. With releases, features, etc. Someone or some group of people must necessarily make decisions about what makes up "macOS 10.14.5". Even if that team is "Craig and his direct reports" or whatever, and even if that team has other responsibilities.

> Even if that team is "Craig and his direct reports" or whatever, and even if that team has other responsibilities.

And if those "other responsibilities" are iOS, tvOS, and watchOS, then there is no "macOS team." There is the software engineering organization.

Re: Mac: Keyboard Shortcuts Killed by Bug

#93
post #64

Lol. Even when that dialog worked as intended, it was total crap! It mostly worked for certain menu items only. Fun game: try to remap Ctrl+a to select all, Ctrl+c to copy etc to mimic unix/windows. (or god forbid, to make your limited mobility device that cost thousands of dollars several years ago to work on your work provided macbook pro) Every single app will behave differently and you will see how broken usabili…

I'm not saying it is easy or logical, but it is possible. System Preferences > Keyboard > Keyboard > Modifier Keys... In this dialogue you can remap what the modifier keys means, so you can make the ctrl-button act as cmd and make the cmd-button act as ctrl. Personally i use it to make the caps-lock key act as escape.

now you have the problem of making your crap accessibility hardware closed source firmware to send the caps lock key code instead of ctrl. Good luck with that.

Re: Mac: Keyboard Shortcuts Killed by Bug

#94
> Right now, if I open my list, it displays like yours, without any ellipses. If I add and then remove a shortcut, half of the list spontaneously turns to “…”. But if I close and open System Preferences again, I’m back where I started, with a properly displaying list

By the author's own admission (in the comments) this doesn't even seem like a major bug. His refusal to report it isn't helping anyone, and it's a display issue that's fixed by closing and re-opening a window. How was any keyboard shortcut actually killed here? What a terrible clickbaity headline.

Re: Mac: Keyboard Shortcuts Killed by Bug

#95
post #54

Earlier quoted context omitted.

For any feature on OSX there are some people who love that feature. But the reality is the core reliability of OSX has been declining for years, and many of the bugs are becoming more egregious. Especially some of the recent security issues. They are all symptoms of an under-resourced team. I have no doubt the OSX engineers are heroes to a person. But I can't imagine they have the resources they need. I also can't im…

I administer approximately 30 macbooks. 2018s with a few 2017s still in there. They're mostly unreliable garbage. In particular, zoom.us, our teleconferencing solution, crashes them regularly with spewed messages about GPU stuff in console. We're about at the point of running windows vms so my salespeople can have a reliable conferencing solution. The keyboards also do not hold up at all. I've gotten into a shouting…

Is there a PC laptop vendor you would recommend?

Re: Mac: Keyboard Shortcuts Killed by Bug

#97

Earlier quoted context omitted.

I'm not sure what point you are trying to make here. macOS is a product. With releases, features, etc. Someone or some group of people must necessarily make decisions about what makes up "macOS 10.14.5". Even if that team is "Craig and his direct reports" or whatever, and even if that team has other responsibilities.

For example, I believe if macOS had a dedicated VP with specialized software teams like the type we are speculating here, my guess is we would have fewer bugs of this sort than we do now.

This is my take as well.

Re: Mac: Keyboard Shortcuts Killed by Bug

#98

Earlier quoted context omitted.

The iPhone integrations (assuming you mean Handover) are one of my favourite parts of the MacOS/iOS ecosystem and one of many reasons why I can't see myself moving away from either OS for a long time. I've also experienced very few bugs in MacOS which have affected me on a day to day basis. Not saying they aren't there, but to me the MacOS team are doing a pretty great job.

For any feature on OSX there are some people who love that feature. But the reality is the core reliability of OSX has been declining for years, and many of the bugs are becoming more egregious. Especially some of the recent security issues. They are all symptoms of an under-resourced team. I have no doubt the OSX engineers are heroes to a person. But I can't imagine they have the resources they need. I also can't im…

It’s called macOS. It hasn’t been called OS X for years, and it was never called OSX.

Re: Mac: Keyboard Shortcuts Killed by Bug

#99

Earlier quoted context omitted.

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.

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.

>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.

Re: Mac: Keyboard Shortcuts Killed by Bug

#100

Earlier quoted context omitted.

For any feature on OSX there are some people who love that feature. But the reality is the core reliability of OSX has been declining for years, and many of the bugs are becoming more egregious. Especially some of the recent security issues. They are all symptoms of an under-resourced team. I have no doubt the OSX engineers are heroes to a person. But I can't imagine they have the resources they need. I also can't im…

My MBP (2016 model, touchbar, macOS Mojave) kernel-panics every time the battery runs out, while attempting to wake up after I plug it in. I frequently work away from my desk and have symptoms of ADHD (inattentive variety) so this actually happens at least 3 times a week. The MBP I had previously (same model, exchanged out due to keyboard keys sticking) did the same thing.

Ditto, except in my case the previous is an MBA. (I still have it, but the battery's dying, so it does it at about 26% instead.)

Additionally I find if the battery hits 5%, it doesn't actually register that it's charging in time to save it. Fair enough, but call it zero (so implicitly I'm warned earlier).

Post reply on HN