> this approach pre-dates the concept of putting all default behaviours into a unified panel When are we allowed to ask Apple to step it up, then? Because this

> this approach pre-dates the concept of putting all default behaviours into a unified panel When are we allowed to ask Apple to step it up, then? Because this has been available on other operating systems for many years. > something which would invariably lead to an incomplete list of available applications 1. What makes you think this? Many operating systems handle this just fine, right now, today. Apps register themselves with something like XDG services or Android Intents of whatever and in that way the OS gets a comprehensive list of them. 2. So? Even if a user wants an 'unregistered' app to be a default, you could always let the user browse to a .app folder or an executable or provide a command to execute (with some kind of pattern system for passing a file to be opened as an argument and so on).