The biggest mistake I did in 2025 was picking shadcn because it was so hyped. Saw it importing from radix anytime you enter a command. First red flag.
Then I saw the radio component. Second red flag. You should see what they've done with the select component. But we were too far into the deadline for a project with running targets. So I just gave up and asked copilot to make the changes for me, and I'm not a fan of AI anything.
Funny enough we did a POC for the same project before that without shadcn and looking back, it's so much leaner and easier.
I might just break one night and redo the whole ui library with vanilla html elements.
They hype-train on all of this stuff is unreal. React+NextJS+Tailwind+ShadCN is just a mess. It's complexity piled on deeper complexity - for little gain! But suggest any of that in many circles and you'll get the standard, "skill issu bro" comebacks. Say what you want about Remix/ReactRouter 7 (there are plenty of issues to talk about there) but at least those guys _tried_ to stay closer to existing web standards. I could go on and on about the disaster of NextJS caching. I could point out RSCs being one way to solve a problem that could already be solved by loaders in other frameworks....
Tailwind was my moment of saying, "Nope, I'm gonna sit this one out". I have a few trusted friends that assure me I'm missing out. I've told them to come back to me after they've done their first major refactor. If they tell me it was a pleasant experience, I'll have another look.
In general, Tailwind and React don't match well. Why use a soup of CSS classes when React has props? If someone needs an a11y-focused base for their component library, they can start with Radix UI directly, ignoring Tailwind and Shadcn.
This could be a bait. I was going to comment how wrong you are. How much better and advanced the windows model is compared to linux and how making products that co-operate with other companies (read: people with products they want to get paid for, when did that started being a bad thing?) instead of being "gatekeepy" over ideologies will always have an upper edge.
But seeing how companies have worked in the past, you might be right, some middle manager there might just axe the most valuable part of their product.
Either I am stupid or you're being dishonest. There is no one click way to disable it.
Only on pro versions of windows, with a group policy otherwise a couple of obscure registry keys no regular users know.
Just too small I think. It's neither hosted on a common forum software or worth targeting specifically. If you turn on `showdead` in your profile you can see the caught spam. It's usually pretty thin on the ground, and when it does it occur there's almost no diversity, suggesting just 1 bot source being interested in the site at a time.
(yes, hardly anybody remembers that there was a Windows version between 7 and 10 - but it did exist, I'm not making it up, saw it with me own eyes on a coworker's PC once).
Considering Windows 7 (if you count ESM) was supported all the way up to 2020, it's no wonder people skipped 8 (start menu tiles aside). It was a weird release schedule, and it was split into two versions 8 and 8.1, with 8 only having like 3 years of main stream support, and no ESM and 10 released just two years after 8.1.
If you count paying for ESM, someone could have gone from XP->7->11 and still been within support the whole time. Or from vista straight to 10.
Fun fact: Windows for Workgroups 3.11 was supported all the way to 2008. I believe it was the longest supported version of Windows.
For most people, Google Docs, Zoho, M365 Online, Proton Docs, or some web hosted instance of OnlyOffice or Collabora Office handily meets the majority of needs.
As someone that is 100% on Linux and is occasionally forced to use Teams (where a fat client is no longer possible and was worse than the browser version when it was), I'm curious what that 5% was for you.
what's missing in the linux teams client out of curiosity? I use it every day and, besides being slightly less stable it doesn't seem to be more junk than the windows client (which in itself is pretty junky. There was so much moaning when we switched from telegram to teams at work just because message delivery was not rock solid)
11 is a step in the right direction for a modern consistent look of Windows.
But there's still a long way to go; they still haven't managed to put all the system settings in a single app. And I wonder if they'll ever be able to get rid of the Control Panel; too many legacy applications need it.
reply