Remembering that this thread is in the context of using native browser engines for desktop apps vs Electron, and the original poster's suggestion was quite meas

Remembering that this thread is in the context of using native browser engines for desktop apps vs Electron, and the original poster's suggestion was quite measured (i.e. we don't need electron for every desktop app). I don't think your point about push notifications is particularly relevant in this use case (personally I don't want desktop apps sending me any push notifications when they're closed - am I in a minority?) A review comparing the bleeding edge versions of Chrome, Edge, Safari, and Firefox on caniuse.com shows that Safari is doing quite well: https://caniuse.com/?compare=chrome+117,edge+114,safari+TP,firefox+115&compareCats=all https://caniuse.com/?compare=chrome+117,edge+114,safari+TP,f... Many of the areas of "no" for Safari are also "no" for Firefox, suggesting Chrome/Chromium features without a consensus amongst browser vendors, and many don't make any sense for desktop apps (e.g. Vibration/Gyro/Accelerometer APIs). The GP made a fairly broad statement about web technology support which is what I was responding to - I know they've lagged behind on Push Notifications but what I'm arguing is that I think the narrative of "Safari is slow to adopt new web tech" is more a perception driven by Chromium constantly pushing new features into their browser (and them being regarded as 'web tech' rather than 'chrome tech' simply by nature of their position in the market) than Safari actually lagging behind standards implementation generally. P.S. On Web Push, I don't think anybody whose older relatives use Android and get regular advert-laden push notifications (from sites they didn't realise they were accepting push notifications from, and often aren't sure how to stop them) would disagree that Google's attitude on Web Push was foolhardy, and Apple taking a more thought out approach is welcome (although I agree that it should have happened faster)