It's quite cold a lot of the time in Northern Europe, and people who are cycling to commute there often really aren't going very fast so won't sweat much.
You can also get "moisture wicking" clothes, that might help with a certain amount of sweat.
There is quite a lot of e-bike use in Amsterdam and Copenhagen. Google "bakfiets" - it's a whole "suburban parents with a family size e-bike" cliche (but a good one!).
You don't avoid naming - you name the components and the styles live in the components. The key is to avoid the false separation of concerns of style and structure.
If you're making a wholesale design change, you should expect a wholesale code change. If you're making a small change to a component that's the same every everywhere you should ideally expect to make that change in a single place. If you don't have that, that's a problem, but it's not Tailwind's fault.
Global defaults are a separate matter. As are prose styles / styles for UGC text because you don't know the HTML structure ahead of time - by all means use the cascade here, but for almost but for everything else you have two maintainable options:
1) Some CSS naming system or scoping system, e.g. BEM where you enforce proper naming and selector complexity limits (except in rare circumstances). This is extremely hard to do in the long term on a big project.
2) Leverage the component system / template system of whatever system you're using to make reusable components and use utility styles.
Using the cascade extensively on a long running project is a recipe for maintainability disaster - you will face a wild goose chase for the file you want every time you want to make a change, and then another wild goose chase for unexpected changes because your selectors weren't specific enough.
I'm also pretty strongly of the opinion nowadays that separation of concerns of CSS and HTML is a false separation - the single concern is how a thing looks on the page.
You really need to cut out these accusations of dishonesty - it’s a bad look.
He’s not saying “separation of concerns and good naming practices” are bad things, he’s saying that separation of concerns between HTML and CSS is mostly a false separation (it’s the same concern - making the UI look right) and that good naming practices are hard - best just do that in one place, the component that address the concern with both style and structure.
Option 1: Find a visual error, open devtools, find the nearest most descriptive class or id (.primary? Oh no…), open IDE, global search in styles folder structure (most likely but not the only place to find CSS) for “.primary”. 40 files returned. After 15 minutes find a file that looks like it might be the right one. 10 minutes to understand the CSS (lots of advanced CSS in here…). Find the cause of the visual error, make the 1 line change. 30 minutes - job done.
Option 2: Find a visual error, open e.g. React Devtools, find the component name, open the IDE, find the component source file, find the HTML, change the utility style class, job done - 5 minutes.
These are not contrived examples. I had a one liner take 40 minutes to find in a codebase a couple of weeks ago. Not an exaggeration.
I really used to believe in separation of concerns but I don’t any more, because of all the time I’ve had to spend fighting with “option 1” codebases over the years. Pretty much any big codebase with normal CSS is going to be an “option 1” eventually unless it’s the work of a single good CSS developer (rare skill), or a team where someone who’s a good leader also cares about CSS enough to enforce a convention like BEM in perpetuity (even rarer skill).
Anyone building anything complex these days is using some component abstraction - whether it’s client side or not - to manage complexity. May as well make use of it for styles if it’s already there.
The reason that there’s a backlash against separation of concerns, the cascade, and (low) specificity is that each of these things is a complete disaster for maintainability in the long run.
One note in making an example of that Catalyst button. If you wrote out all the styles required to do the amount of work that button is doing it would also be extremely difficult to understand, and what’s more, it’d be in a completely different file to the single thing that gives it any meaning - the HTML.
This is exactly my experience as well. CSS in bigger codebases becomes unmanagable pretty quickly, and making small changes can become a big pain point. Tailwind doesn't completely solve this problem, but it absolutely improves it by reducing the distance between related concepts - and that's always a good thing.
The absolute worst thing about forced installations of pay-as-you-go energy meters is that they carry the highest per-unit energy price in the country. We force the neediest to pay the most.
Sadly this is nothing new in the modern world. Just look at how much taxes are paid by the rich vs the common folk.
This assymetry and the exploitation of the most vulnerable is part of the system we currently live in.
In the UK at any rate, the top 1% of earners pay 33% of all income tax. A full 50% of the workforce now receive more in state benefits than they pay in taxes.
The problem with this is that the wealth of the rich wouldn't pay for much earnings.
I mean people complain about medicine as well. And then you check. If we fully nationalized all pharma, and put their profits at zero (but kept development going) ... that would mostly be a 10% drop in the cost of medicine on average at most (more like 2-3% for the really common ones), 20% for some of the more expensive ones and there would be the exceptional medication getting 25% off.
This is not the price reductions for medicine that people are looking for when they're complaining ...
I suspect this is similar. If you redirected all profits to employees, it would be those sorts of numbers. 10% more. 20% more, with 30-60% of the increase going to the state. 100% and more increases would be limited to some companies that are already paying pretty well, like Google or Facebook.
INSULIN is bloody cheap. You want the old bovine insulin in common use 15 years ago, and still in use in much of the world? You can get a bucket of it for ~$200.
There's problems with it. It's not the right variant of insulin, it's very fast acting, requiring you to do the measurement-inject dance every 2 hours or so. It's slightly uncomfortable to have in your veins (because it's not really purified, and includes a couple thousand other proteins, some of which are irritating) ...
Re-inventing insulin the way people want it to work:
1) adaptive. Currently means combining making minute quantities work perfectly, but slowly, which is, of course, a total contradiction.
2) the perfect form of insulin, not just the human form, but variants that actually feel better, for you personally (ie. not the same variant for every patient)
3) VERY long lasting (which is of course also a total contradiction because the dose has to vary over time, however 4, even 24 hours without eating, is doable)
4) Keep developing this further, to get to oral application, but at some point totally adaptive without an implant would be excellent.
5) without using animals, or even animal cells (even though that doesn't really matter)
6) oh and without using cancerous cells, which is the other trick we know
7) so in essence using the newest, most expensive, most patented trick we know, "yeast expression"
8) which necessitates the most expensive protein purification tricks we know
9) administered using an implanted insulin pump
10) all of this approved by doing studies on >5000 patients (who get all medical care necessary for such studies for free for at minimum 2 months)
Yes, this is expensive. And, uh, well of course it is. Now, I get it, the best treatment is the best treatment and the most expensive one, and everyone should get it, and of course doctors will advise the most expensive one, for good reason. But there's currently various compromises available too.
> In the UK at any rate, the top 1% of earners pay 33% of all income tax.
that statistic is disingenuous without also stating how much of the national income the top 1% earn. i.e. Its obvious that the top 1% pay the most tax because they earn the most.
Actually, the most relevant statistic (which is, of course, much more difficult to calculate) is how much tax each pay relative to their disposable income—ie, the amount left over after necessities such as food, shelter, and clothing have been paid for.
With any vaguely reasonable calculation of this, it becomes painfully clear that the poor pay far, far too much (because they have, effectively, no disposable income) and the rich pay far, far too little (because almost all of their income is disposable).
However, disposable income has a technical meaning. When the ONS publishes disposable income statistics, they mean income remaining after tax (I presume they subtract income tax and NI, but not council tax because that's local). They don't subtract e.g. energy bills or food.
From where I sit, "income after tax" doesn't really seem to fit as the meaning of "disposable income", though I suppose I can see why it would look that way to an office like ONS.
Now, to be clear, "where I sit" is in the US, and I've never seen "disposable income" be given an official usage like that over here; its only meaning that I've known is, much more colloquially, just what I said: the amount of money you have left over each $timePeriod after paying for the basic necessities of life. (How one defines those, specifically, varies greatly from person to person.)
unless you supply the raw figures as well, it remains a sleight of hand.
Let me put this another way; anyone in the 99% would happily swap income with the 1% and then pay twice as much tax on that income than the current 1% do.
I find any conversation about the "1%" that centers around discussions of % paid in anything to be highly amusing/sad. Talk in absolute dollars and see how things turn out.
As a PROPORTION of their wealth/income what percentage do the Rich pay and the poorer pay?
The poor pay a higher PROPORTION of their income in taxes than the rich pay. But because the poor earn so little it amounts to such a small amount of the total taxes collected.
Your static actually highlights the vast gulf in wealth/income between rich and poor. Shame on u for not seeing that.
You can also get "moisture wicking" clothes, that might help with a certain amount of sweat.
There is quite a lot of e-bike use in Amsterdam and Copenhagen. Google "bakfiets" - it's a whole "suburban parents with a family size e-bike" cliche (but a good one!).