pull down to refresh
I went around looking at some things people made with base ui and much is awesome... until I do it on my phone, then half of it breaks.
Base ui is a thin/unstyled wrapper around html things, so it itself does not know mobile from desktop. I'd guess it's the inheriting project's lazy styling (and to your point, subsequent QA) that's making it break.
When automating coding, well thought out architecture of both the product and development processes becomes really important. I'd say this would be including comprehensive CI and human QA.
100%. I've seen a weird systemic apathy result from automated coding. If writing the code is easy, why would I bother continuing to do other hard stuff?
I pay attention to what the developers I know are using + have GPT Pro do surveys of options. Kind of like googling "best <thing> in 2026" once was. Then I follow the references, read the docs, browse the code, and do follow on searches from there, arriving at developer blogs and reddit posts. I concluded, tentatively, on stylex/base after several days of repeating this process a few times.
How the slider works is a headless component thing (radix in shad). Shad just couples styling presets with the slider which is most of what I don’t like about shad.
Also shad is already beginning to add base ui components too - they live alongside radix. They abstract away components really well, so as shad user you shouldn’t notice the transition.
maybe i've been unclear, but i'm trying to validate my decision to switch to base/stylex - not deciding if i should switch. i'm trying to think through what systems properties i want, attempting to avoid use this thing generally everyone uses by default without understanding the tradeoffs (and let's be honest, vibing and dgaf for the most part)
i know i don't want to use shad already. it's perfect for people that want presets and want these decisions to be made for them, and i get you can customize it too. that's what boostrap was for a long time, so i don't have anything against that.
having some experience being an end user of enshittified 3rd party libs now, I'm trying to pick things i'd be happy to troubleshoot/review/maintain myself. i want to provide the abstraction layers - which i will probably vibe too tbh, but at least i'll understand them.
by chemistry analogy, i'm looking to make my own molecules so i'm looking for the right atoms/elements. i'm not looking for a premade molecule.
maybe i should be looking for a premade molecule though. i just don't see much reason to start there when i can vibe my own molecules.
It never ceases to amaze me what a shitshow the front end is.
It amazes me that it works at all. A frontend is like a function that takes the human body as input. The shitshow is the input, the humans, not where the code is located.
Did you see the tailwind media not long ago about having to lay off a majority of their workforce?
I saw that. I loved their book and they get a lot of stuff right. Selling licenses just isn't the business that it used to be.
This is like the asymmetric advantage of harassing a woman until she dates you.
I'll make her life miserable until she says yes. She eventually will say yes because I'm sexy. Unfortunately, she's an idiot and needs to be harassed into seeing how sexy I am. The only way this doesn't work is if she's a lesbian.
Oh, and if you don't like my approach to dating you're jealous of how sexy I am.
Sorry about that. We need to fix these limits. We talk about it regularly. It requires making a bunch of defensive decisions. This will be a priority after the wysiwyg ships.