What capabilities do you need that current web browsers don't satisfy? I hear this argument quite a bit with Safari bashing. While Apple does seem to favor the "native" approach, I also use Mobile Safari exclusively for my own apps, and it works fine.
At a previous job they were moving away from Blazor (which bummed me out, I love the philosophy) because every time they deployed it broke sessions/disconnected all active users.
The tech contributions are fungible, to be honest. Sure, they're popular because ~Facebook~ Meta is a giant company, but if they disappeared overnight, other equally good solutions would soon take their place.
This is my anecdotal experience too. There's a (non-sequential) human thread that connects all my work experience. Ironically the exception was my very first development job, which was a blind application.
Just makes me think of my bank's site, which shows a few seconds of "loading" animations on each section of the page. Maybe if the main content loaded quickly and ancillary content was lazy-loaded it would feel faster.
Yeah, I really loved the clarity of the 2x2 product matrix Apple had immediately after Jobs' return: 2 desktops, 2 laptops, one "consumer" and one "pro." Of course there were configuration variations within those broad categories as well. I realize we don't live in that world anymore, though.
There's a major intersection about a mile from where I live, which unfortunately is next to public schools/local library/etc. The other day I was in my car waiting for the light when I saw a young girl on a scooter push into the crosswalk. She had the right of way, but I inwardly cringed and hovered my hand over my horn button, just anticipating that a vehicle was going to turn without seeing her. Fortunately she made it through OK.
ironic that the benefit of using web tech (platform abstractions) can be totally negated by such a small footgun, which then requires insane knowledge of the browser rendering pipeline to solve