It’s going to be a lot smaller since it doesn’t bundle a version of chromium in every build. Instead it uses the systems native web view. This does pose the problem of vendor specific rendering issues… How snappy it feels is down to how the front-end programmed. It can still be a mess of bloated JavaScript 🙂
After you explained it a bit further in another comment it was pretty obvious you didn’t mean cryrocurrencies. I really did latch onto “crypto” as cryptocurrency, unfortunately the case for a lot of people.
The trend towards subscription services for basic features is garbage and replacing controls which should be easily accessible with a touchscreen is stupid if not outright dangerous.
Also isn’t a Tesla kind of a “premium” vehicle? For mass adoption they should be affordable without all the silly add-ons that will be woefully our of date in 5 years.
I don’t want to own a car that could cost 1k+ dollars to replace the headlights.
Yes, we all know crypto and scalability go hand in hand /s
Prioritizing developer experience is not the reason we use front-end frameworks. People expect the web to work like a desktop app (no page reloads). The initial request might take a little bit longer, but in the end a well written front-end app will feel faster.
The problem is that people don’t worry about bundle size and cram every library off of npm into their website.
A lot of posts in here complaining about shitty commercial radio. Do you all not have local radio stations? I love my local stations.