As you're mainly complaining about CSS layout features being used here:
For a long time we were forced to use the ugliest hacks imaginable to get to the nice (responsive, design-minimalist(!)) layouts we wanted, because CSS layout tools were utter archaic bs, for years on end, because browsers iterated so slowly.
Then things started speeding up, and we're getting to make better websites (and apps!) that are way easier to design (with the correct design theory equivalents), implenent (with less code) and easier to maintain (i.e., understand). And you're not missing out if you just keep your browser up to date.
I know it sucks if you're on an unsupported device that doesn't get any updates, fair.
But let's face it: 99% of the population is better off security-wise when we're not enabling them to run unpatched devices forever.
Security updates have nothing to do with level of support for css3 modules.
Much of the issues of layout were already solved more than 12 yrs back, ie when css3 became mainstream.
The issue is devs are unaware about different levels of css3 or just plain ignorant about it.
Are you aware about the different levels of css3? Are you even aware there are levels to css3? Why are these frameworks not listing them and simply saying that they comply with web standards? Which specific web standards do they comply?
Any new css3 feature should have a fallback if they say they comply to web standards, which these frameworks don’t add.
To be fair on this particular point, talking about iOS Safari before version 14 isn't "some random old build". It depends on your own users, but I saw plenty of 6-year-old iPhone user agents in the web logs when dealing with a doctor's surgeries app.
The actual logic (mechanical relays, timers, potentiometers and the like - analog modular setups built by electricians) would have sat in an electronics cabinet separately from the dashboard, which itself would have had simple lightbulbs, dials and buttons.
People had to wear a suit and wanted it to be as cheap as possible, which led to a race to the bottom in suit quality. In the end we had fused jackets and synthetic fabrics which made you sweat with people in turn not even bothering to get cuffs and hems adjusted. Absolutely horrible. This is why casual took over.
Maybe it's time for us to recognize that a good suit serves you for years and decades and as such can cost a few hundred bucks.
And despite the little supply due to classical menswear being irrelevant today, there are also incredible deals to be found at goodwills and the like.
If you live in Germany and have a Fritz!Box router, you can just buy a second old-ish Fritz!Box and a simple landline phone (from the likes of eBay, Kleinanzeigen...) and hook them up via WiFi.
Voilà, telephone service as it used to be. No proprietary payphone with questionable ToS and privacy policies needed.
For a long time we were forced to use the ugliest hacks imaginable to get to the nice (responsive, design-minimalist(!)) layouts we wanted, because CSS layout tools were utter archaic bs, for years on end, because browsers iterated so slowly.
Then things started speeding up, and we're getting to make better websites (and apps!) that are way easier to design (with the correct design theory equivalents), implenent (with less code) and easier to maintain (i.e., understand). And you're not missing out if you just keep your browser up to date.
I know it sucks if you're on an unsupported device that doesn't get any updates, fair.
But let's face it: 99% of the population is better off security-wise when we're not enabling them to run unpatched devices forever.
reply