Yeah shared worker are awesome. I love having a single instance of the core of my app running in a worker, and then each tab the user opens is just a UI view of that one instance. It greatly simplifies keeping things in sync across tabs.
But it's just not possible for Safari... you either have to make your code much more complicated, or add some hack to prevent users from opening your app in multiple tabs at the same time :(
What percentage of your users use Safari? If it isn't impactful to your business, you could ask them to use Firefox or Chrome.
I realize we need more browser diversity and not less, but at the same time we should encourage all participants to keep up so that the burden doesn't fall on smaller players.
Depends on the market; I don't think it's that common in enterprise, for instance, to have Windows 10-using orgs with virtually no use of the default (Edge) browser, but large numbers of users with both IE and Chrome because of (legacy and modern) app demands.
I guess some people don't care about the browsers very much, and will just use whatever is installed. If there are multiple browsers installed, they may learn to use different browsers as a simple way to have different easily distinguishable browsing contexts (different icon/app name) - instead of having multiple windows of the same browser that looks pretty much indistinguishable.
Depends on the site. In some cases, less likely. E.g. at this point in time, Facebook or YouTube or even Slack could make a browser change demand with little to no consequences.
But it's just not possible for Safari... you either have to make your code much more complicated, or add some hack to prevent users from opening your app in multiple tabs at the same time :(