Live data from Hacker News

Neobrutalism components – A collection of react-tailwind components

github.com

21–30 of 52 posts

Re: Neobrutalism components – A collection of react-tailwind components

#21

The border radii don’t quite fit together, and you can easily see the gaps on an iPad.

It would feel more appropriate to me to not have rounded corners at all - you'd be hard pushed to find rounded edges on a truly brutalist block of flats!

Re: Neobrutalism components – A collection of react-tailwind components

#25
Congrats on the project, what you did looks nice but I have to say this: “brutalism” and “react” kind of clash in my mind. I understand you’re inspired by the brutalist aesthetics, but I read the very definition of brutalism as “not react”.

Re: Neobrutalism components – A collection of react-tailwind components

#26

As you're asking for feedback: the components are not accessible. I've assessed a lot of UI libraries [1] and most of them have issues. You can start with running Lighthouse (Audit tab in Chrome) to get and fix at least all the tool-detectable issues. [1] https://darekkay.com/blog/accessible-ui-frameworks/

I was sad to not see vuetify in the reviews. I was wondering how it stacks up since it lists a11y as core feature.

Re: Neobrutalism components – A collection of react-tailwind components

#29
post #27

"ugly" is not an aesthetic

ugly is an aesthetic and it communicates, when intentional, a focus on function or simplicity rather than looks. Now to your point, ugly in anything more than a css stylesheet is a little bit moot as it is an aesthetic that remains superficial and does not inform the implementation but only the consumption.

Re: Neobrutalism components – A collection of react-tailwind components

#30

Looks great! Not sure if this is a Tailwind thing or not, but I think any presence of hex codes in your examples is a little disappointing. It should be trivial to adjust colors from a fixed palette, rather than find-replacing hex codes across a codebase. Especially for modifier colors like the active tab states. EDIT: I realize now that this is meant to be copied into an existing codebase, not used as a library, so…

That's tailwind in a nutshell. If you want to change colors across a code base, you have to find and replace. Now, the colors are "named" using a system, but it's still f&r
Post reply on HN