Live data from Hacker News

Precedent – Building Blocks for Next.js

precedent.vercel.app

11–20 of 50 posts

Re: Precedent – Building Blocks for Next.js

#11

Looking to learn and build a react app, should I start with this? Did review some html css prior.

If you want to learn, my advice would be to focus on learning one thing at a time. Pick up react. Just react. NextJS (and other libraries included here) solve specific problems in specific ways. It's hard to know if they solve them in the way that works for you if you don't understand the problem they are solving, or what other approaches might look like.

Once you're comfortable with how react works, then start layering in additional libraries and tools, and get a feel for how they work. You may also find they introduce new pain points that don't work for your particular project. When you're trying to learn everything all at once, it's hard to figure out where a pain point is even coming from.

Re: Precedent – Building Blocks for Next.js

#15
post #7

Looking to learn and build a react app, should I start with this? Did review some html css prior.

Ant Design is phenomenal, mature, and fully featured. I highly recommend it instead of this.

But it's very hard to not look like Ant. Some of the components are great though.

Chakra is easy to design with, and fully accessible. Well thought out.

Re: Precedent – Building Blocks for Next.js

#17
post #7

Earlier quoted context omitted.

Ant Design is phenomenal, mature, and fully featured. I highly recommend it instead of this.

Is it better than Tailwind UI?

I despise flat/Material design and Tailwind's entire philosophy, so I would say "yes"

Re: Precedent – Building Blocks for Next.js

#18
post #7

Earlier quoted context omitted.

Ant Design is phenomenal, mature, and fully featured. I highly recommend it instead of this.

But it's very hard to not look like Ant. Some of the components are great though. Chakra is easy to design with, and fully accessible. Well thought out.

> But it's very hard to not look like Ant.

I don't know why this matters. Users certainly don't notice or care. Worrying about it early in the development cycle is a waste of time.

They also have general theming to allow you to quickly get it to look like your brand's colors: https://ant.design/docs/react/customize-theme

Re: Precedent – Building Blocks for Next.js

#19
post #18

Earlier quoted context omitted.

But it's very hard to not look like Ant. Some of the components are great though. Chakra is easy to design with, and fully accessible. Well thought out.

> But it's very hard to not look like Ant. I don't know why this matters. Users certainly don't notice or care. Worrying about it early in the development cycle is a waste of time. They also have general theming to allow you to quickly get it to look like your brand's colors: https://ant.design/docs/react/customize-theme

Tamagui gets you Chakra-like features with even better theming, performance and works on Native to boot.

Re: Precedent – Building Blocks for Next.js

#20
post #3

I've checked out the component [1]. What's the reason to go through so many hoops instead of just using the HTML native element [2]? [1] https://github.com/steven-tey/precedent/blob/main/components... [2] https://developer.mozilla.org/en-US/docs/Web/HTML/Element/di...

The native does very little on its own in terms of functionality. It's mainly there for accessibility/semantic markup
Post reply on HN