I'm convinced that web components (and the tech that makes up web components) will eventually find its place in everyday web development. That said, I do think people are making a mistake when they try to use it as a one-to-one replacement for react.
Part of the problem with the tailwind debate is that the appeal of tailwind is not just having your styles in your html, it's also having predefined style units, e.g. size intervals for things like margins.
CSS variable libraries like open-props also do this, only without the controversial use of utility classes. Add editor snippets to that and you have nearly the same ease of use as tailwind.
Personally I find the term "intellectual property" to be more messed up. It isn't property, it's a government granted monopoly on reproduction and distribution.
Calling it property allows for this bizarre concept of a form of "theft" that still leaves you with the thing "stolen" from you.
It might be more accurate to say that the democrats started taking the rust belt for granted. And it's hard to ignore the left's shift (in primary focus) from blue collar workers issues towards race and gender issues.
- Firefox? Sync but difficult browser profile management
- Brave? Multiple profiles due to being chrome based, but they use this weird sync system that I'm not a fan of
- Opera? Sync but no multiple profiles on mac (last I checked)
- Safari? Sync AND profiles, but the safari ui really doesn't do it for me
Hopefully this update to multiple profile UX in Firefox will make it viable for my typical use.