Earlier quoted context omitted.
Sure, there is one exec, but there must be someone under him who is responsible for OS X.
Nope. Craig’s directs are responsible for apps and all the platforms those apps ship on or cross-platform technologies that power apps.
Mac: Keyboard Shortcuts Killed by Bug
71–80 of 119 posts
Re: Mac: Keyboard Shortcuts Killed by Bug
#72My complaint about this preferene pane - no wildcards in menu names. macOS has a handy "Batch rename" feature in the contextual menu when you right click on files. The renaming GUI gives you options for sequential numbers, text replacement, prefixes, suffixes, inserting dates. But the menu to open this is called "Rename X Items…" so you can't assign a keyboard shortcut to it. Might be 5 items, might be 2914 items. Wi…
Re: Mac: Keyboard Shortcuts Killed by Bug
#73Lol. 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…
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.
Re: Mac: Keyboard Shortcuts Killed by Bug
#74Earlier quoted context omitted.
And overall power usage. I think I probably know more shortcuts and optimizations on macOS than most people at Apple.
Have any tricks you want to share? My MBP 15" gets 2 hr tops unless its plugged in. Even with "mere" web browsing
Try clicking the battery icon ;-)
Re: Mac: Keyboard Shortcuts Killed by Bug
#75Earlier 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.
Re: Mac: Keyboard Shortcuts Killed by Bug
#76Earlier 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.
Re: Mac: Keyboard Shortcuts Killed by Bug
#77I doubt it is developer apathy. It smells like a management issue. iOS is where the money is. I don't know anyone at apple, but here's how I imagine it is there: Every OSX engineer probably has more bugs on their plate than can be fixed in one career, in addition to feature development tasks. The OSX team is severely understaffed both because it is not a priority at Apple, and because it is getting harder and harder…
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.
- I upgraded to 10.13, and my stock graphics cards would slow, freeze, and then crash window server, logging me out. I spent the money to buy a hot new GPU from Apple's latest recommendation list, and it no longer crashes (though I'm having trouble getting both of my Apple displays to work, since apparently most of the "DisplayPort to dual-link DVI" adapters in the world are actually single-link).
Other issues I've run into recently with new or revamped features:
- Dark mode works great sometimes, and other times it's an unreadable mess.
- Xcode 10's new text editor broke control-T, which has worked correctly in every text field since the earliest days of Mac OS X.
- The new security around contacts/calendars broke my app. It doesn't work like it used to, it doesn't work like the documentation says it should, and it doesn't log anything useful to help diagnose the problem.
- The recent documentation, overall, is a big step down. developer.apple.com used to have long-form articles describing how things were built. Now, it's mostly just HTML versions of header files, and half the descriptions are "No overview available."
- The new WKWebView teases improved performance (and not being deprecated, like WebView), but removed major features I was using, or planned to.
- Dragging toolbar items in Safari 12 seems completely broken.
- You can set almost any accessibility option via script, except menubar transparency, for no apparent reason.
It was no coincidence that Macs used to be simple. "Simplicity is prerequisite for reliability"! When you've got only one color scheme, you can make it 'just work' everywhere. Once you've got more than one color scheme, now you have to go check everything to make sure this doesn't happen: https://twitter.com/KenHatesSoftwar/status/11059512173713530... (which depends on the dark-mode setting, the reduce-contrast setting, the desktop wallpaper setting, ...)
Multiply this by every permutation of settings. I don't think it's feasible any more for single-developer Mac shops. There just aren't enough hours in the day to make everything work well. Even Apple is struggling.
My next project isn't another Mac app. It's a web app in Clojure. CSS is still terrible to work with, but (with grid and flex) it's slightly less awful than it used to be, and much more consistent. And Clojure is infinitely more pleasant than Swift.
Re: Mac: Keyboard Shortcuts Killed by Bug
#78Apple should open source their OS. They would not longer have to waste their time and energy pretending that the MacBook market matters to them. Developers would be happy with them - its a win win situation!!
Re: Mac: Keyboard Shortcuts Killed by Bug
#79Earlier quoted context omitted.
I'm sure there are lots. This shows iphone dwarfs all other sources of revenue https://www.apple.com/newsroom/pdfs/Q4-18-Data-Summary.pdf Apple is a phone manufacturer. Computers are a side business.
A side business that is still a requirement for anyone to ship software into Apple’s iPhone ecosystem, so there’s at least some incentive for Apple to continue supporting it. But given that developers have no choice in the matter, they’re stuck putting up with whatever issues Apple doesn’t bother to fix. I’m sure Apple is well aware of that when prioritizing what bugs are important.
Re: Mac: Keyboard Shortcuts Killed by Bug
#80My complaint about this preferene pane - no wildcards in menu names. macOS has a handy "Batch rename" feature in the contextual menu when you right click on files. The renaming GUI gives you options for sequential numbers, text replacement, prefixes, suffixes, inserting dates. But the menu to open this is called "Rename X Items…" so you can't assign a keyboard shortcut to it. Might be 5 items, might be 2914 items. Wi…