I never had a problem with that. I want a specific application to behave the same no matter where I run it. I do not want my muscle memory for how to use an application to be confused by an application not looking or behaving the way I am used to when moving to a different platform.
Of course all the applications bundled with a specific OS should be designed to work the same and work well together. It still makes sense to have guidelines and standard widgets in a system. But I prefer very much any third-party multi-platform app to be identical everywhere I run it.
Not to defend Electron. There are many native frameworks that work the way I prefer, looking the same across platforms.
I use probably 70% Windows, 20% iPad, 5% Meta Quest 3 [1], and 5% MacOS -- for the latter though it is mostly "test that something works on MacOS" and "tech support for the computer the family uses".
I like web-based applications that behave the same everywhere. Personally I feel the MacOS widget set is a touch old fashioned, a little ugly and gauche. I can see though why somebody might like the MacOS terminal better than CMD.EXE. The dominant theme on Windows is that Windows has several widget sets that aren't consistent but the average user doesn't notice or care -- probably the worst area is the settings dialogs which seem to be mostly migrated to a Metro-based design lately. I was afraid before they wouldn't finish that migration before they churned to another framework but I think they've stopped the churn.
The best windows applications, in my mind, steal from web technology -- like they are either using some kind of HTML-based UI or they are made by people who grew up making web applications and reproduce those patterns w/ the desktop widget sets.
[1] I've got some web applications I wrote that run perfectly on the MQ3, especially after I got target sizes up to WCAG AAA level and it is fun to put the headset on and crash out on the couch and get things done