All because the elites got too greedy and decided to destroy the only successful labor movement in America (the New Deal coalition) because they wanted more money.
They do, most issues that arise from making things accessible are self inflicted. Some people just want to redesign things for the sake of design while ignoring a core principle of design (accessibility) over aesthetics.
Sounds harsh but maybe somethings SHOULDN'T be designed a certain way because it breaks a11y when there are other roads to be taken that can still look pleasant, be accessible, and way easier to maintain (less brittle JS to worry about).
One thing to keep in mind regarding a11y, the semantic web is accessible by default. It's once you break away from establish norms do things become harder or tricky, but if you can stick to using actual semantic elements and not div-soup you will cover 90% of your use cases (assuming your use case isn't relying on just the canvas element).
If a sovereign government declared bitcoin illegal, it becomes illegal. There is nothing unique about any asset to stop this because the rules are all made up and can change anytime.
Look up something called "dedollarization," it's been talked about in academic circles for quite some time and now more mainstream institutions are discussing it more too.
Yes, in my undergrad government policy classes twenty years ago, we were talking about a "basket of currencies" that would replace the USD as the global reserve.
IMF has this, intra-countries, with their SDR ("Special Drawing Rights"). China was added in the 2010s, and USD has slowly been losing its percentage of the SDR's overall-makeup.
SDR's are a type of Keynes' "Bancor" concept, but only transactable between countries. Citizens may resort to the commoner's bancor, e.g. bitcoin (but also gold, silver &c).
Based on your description it sounds like you were halfway into reimplementing the virtual dom that react uses (or use to use? unsure if they moved away from that with the implementation of a compiler).
You aren't using it wrong, the only thing tailwind does better than 99% of devs is having default values that both look nice and mesh together well.
Utility based CSS has been around as long as classes have, tailwind is just one iteration of that. GitHub use to have a utility css library as well before switching to their new design.
Yes? I don't think anyone has ever argued that tailwindcss has a moat on anything, it has always been championed as a library created by a designer + dev who care about good UI design.
At least that's how I always seen it billed as, even when Adam was live streaming and saying as much in like 2018/2016.
reply