[deleted]
The Overcomplexity of the Shadcn Radio Button
31–40 of 351 posts
Re: The Overcomplexity of the Shadcn Radio Button
#32Earlier quoted context omitted.
This interactivity definitely adds a wow effect.
Is it sarcastic or does it appear only on high frame rate devices? To me it simply feels like another radio button.
I'm pretty sure it was a sarcastic comment.
On a recent MBP, it's indistinguishable from a vanilla radio button.
Re: The Overcomplexity of the Shadcn Radio Button
#33I normally share the sentiments of the article. But I am also curious, if the goal was: - Implement the radio as the designer sent in the figma file (e.g. something like the radix demo one they're commenting on: https://www.radix-ui.com/primitives/docs/components/radio-gr... ) - Make sure it looks the exact same across all browsers How doable is it with vanilla css? The example they gave was rendered to a black/white…
Where do you draw the line tho? How many kilobytes and how much future maintenance work is avoiding a potential slight visual inconsistency with a radio button worth? Is it worth to lose the x amount of people who have bad network connection? Use this approach everywhere and the actual content of the page (you know: the stuff people came for) suffers. All I can think about is a quote by world famous video artist Nam…
Based on profits of many webapps, there is no line. What eng here forget is that they are oft not the targeted consumer. The hypothetically perfect website doesnt sell as well as a colorful fat choncker does. It is like fast food, not every cares about farm to table.
Re: The Overcomplexity of the Shadcn Radio Button
#34Earlier quoted context omitted.
How do you implement this keyboard navigation with SSR (if you use buttons)? https://www.radix-ui.com/primitives/docs/components/radio-gr...
I can’t tell if this is sarcasm or not! Radio buttons support keyboard navigation without JS.
That's what I mean: if you reimplement it, you need client-side JS to support keyboard navigation.
Re: The Overcomplexity of the Shadcn Radio Button
#35[flagged]
Re: The Overcomplexity of the Shadcn Radio Button
#36Did they ask the original authors of Radix why it's the way it is?
Exactly this. OP fails to understand that there are reasons why it was done this way, and that someone who spent thousand of hours working on this might know something that they don't.
I mean, that much is obvious just based on casual reading of a few articles/discussions about "modern" front-end dev.
I am 100% convinced that "Modern" front end developers are in fact, afraid of CSS and HTML. Like, "it will steal my eyeballs and look back at my face with them" scared.
Nothing else explains things like this, tailwind, JSX components, etc. Nothing. There is no explanation besides absolute morbid fear of the underlying technology - because the browser support has improved immensely but apparently they're all deathly scared of using it.
Before you tell me that I don't know what challenges these problems solve: I was primarily doing front-end development.... 20ish years ago. One of my first jobs in the space was adapting the client side code for a J2EE app - mostly this meant removing an IKEA worth of tables and using CSS - in IE6 of all fucking things. Subsequently I created reusable UI frontend components (i.e. output some HTML, maybe this little bit of corresponding JS, you'll get a usable interactive components in a browser) for two different organisations.
I have said it before and I'll say it again. I think JavaScript developers heard about (or saw over someone's shoulder) how J2EE guys had ant/etc build toolchains, and had abstraction like FactoryFactoryImplementationFactoryBuilderFactory and said HEY THAT LOOKS COOL, and if it's harder to understand they can't fire me!!
It's like NIH syndrome but for an entire community of people whose primary goal is chasing the shiny, followed closely by resume padding.
Re: The Overcomplexity of the Shadcn Radio Button
#37This is the reason I absolutely hate shadcn. The number of dependencies and files you introduce for trivial components is insane. Even tiny little divs are their own component for no good reason. I genuinely don’t understand how front-end developers accept this level of needless complexity. Shoutout to Basecoat UI[1], so implementing the same components using Tailwind and minimal JS. That's what I am preferring to us…
> I genuinely don’t understand how front-end developers accept this level of needless complexity. in my anecdotal experience as a bit of an old fogey with a greying beard, the enthusiastic juniors come along, watch a video by some YouTube guru (who makes videos about code for a living instead of making actual software) proselytizing about whatever the trendy new library is, and they assume that it's just what everyon…
Please name some names of these performative developer/engineers. I want to know how many are on my bingo card. Ill start, something imegen and tnumber geegee.
Re: The Overcomplexity of the Shadcn Radio Button
#38Earlier quoted context omitted.
Exactly this. OP fails to understand that there are reasons why it was done this way, and that someone who spent thousand of hours working on this might know something that they don't.
Can here to say this exactly. Not saying they don’t raise an interesting point but the complete lack of curiosity why a group of experts in simplicity and accessibility decided to take this path is jarring
> a group of experts in simplicity and accessibility
According to who? This alone is a pretty damning case against such a claim.
Re: The Overcomplexity of the Shadcn Radio Button
#39Yup. Unfortunately common I think - not just with UI components. Occam's razor is sometimes only for others.
Re: The Overcomplexity of the Shadcn Radio Button
#40[flagged]
[deleted]