Not nearly enough people in the react community are focused on sharing raw styles without associated functionality. Most React generic component libs are garbage cause they try to be super flexible and provide tons of functionality at the same time
The fact that CSS in JS hasn't managed to make popular solutions here is a failing
This is also why I think CSS in JS should be classname-centric and why I think it's good to mix and match CSS-in-JS and classnames
IE11 is the browser that holds the web back more than any other browser being commonly used today. Over the last year, Edge has barely made any dent in IE11's market share.
Yesterday I found out one of the reasons why: Microsoft Support is still recommending IE to people
One of the main reasons people haven't moved off of Internet Explorer is because Edge drops support for a lot of their non-standard features like ActiveX.
But if you search around, it's impossible to find any resources on how to migrate off of these non-standard features
Microsoft needs to do more to get the web up to date and off of non-standard features. It's their responsibility here, and based on my interaction with MS Support, it doesn't feel like they are even trying
There was an internal post at my job today talking about how an open source project seemed like it was going to die because one of the maintainers changed jobs recently
WHY THIS IS NOT COOL: THE THREAD
Maintainers have lives, they have careers, and they are allowed to do whatever the hell they want. Stop putting all this weight on them to hold *your* shit together for you forever.
It's on you to make sure your own dependencies don't go unmaintained. It's part of your codebase, it's your responsibility. When you installed it, you took partial ownership. Never ever approach open source as being someone else's responsibility, it's *your* app thats gonna break
On a separate sibling layer you could have all the styles for your elements, stuff that is mostly static and controlled directly by designers. They could ship components/states (atoms/molecules/etc) as just classnames or mostly static css-in-js
Imagining a CI service which allows you to run all your local dev workflows in containers in the cloud through a CLI. Instead of running scripts locally, you just trigger builds in "CI". No more installing, no more setting up local dev environments, just code (...)
Of course, it couldn't be a typical CI service which runs on a single machine which starts up cold. It would have to be your own machines which are warmed up with containers and already have most of your code checked out and installed and cached (...)
The machines you run your builds on could be configured through the same YAML file that you configure all your build pipelines. The CI service could automatically scale on GCP/AWS/Azure depending on workload. It would look a lot like @buildkite (...)
I know this CSS thing has been dragged out enough, but if understanding specificity rules of CSS is such an important part of CSS (that you need to change careers if you're unwilling to learn it), why did more than half of the respondents (presumably webdevs) get it wrong?
I would argue that something that a majority of people get wrong and still manage to do their jobs is clearly non essential knowledge and is probably just poor design
I don't know what it is about CSS that it's proponents demand you never be critical of its language design.
Tech workers: Failing to act when your company is doing wrong in the world means you are complicit. You should be held accountable for your complicity. It is your responsibility to do the right thing.
I know for some of you that is too much to hear. So go sleep on it.
I asterisk this to make an exception for workers who are not in a privileged position to speak up.
However, considering demographics, most tech workers do have that privilege.
When I worked for Facebook, I did hold myself personally accountable. I spent months speaking out about the treatment of trans people. I went up in front of the company to speak out about it. I left in part cause it felt like I couldn't change the harm that Fb does
MDX would be better if it operated within markdown syntax that would render well with existing tools
Rendered JSX should've been done inside code blocks with commonmark metadata