Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ant Design – the second most popular React UI framework

github.com

Post reply on HN
Print view View original

41–50 of 67 posts

Re: Ant Design – the second most popular React UI framework

#41

Post by hreynier »

jumploops wrote: post #37

Most of the Antd components wrap `rc-[x]` components[0] with a stylish UI. In the past we've found Antd doesn't play well with custom components, and can often have weird performance implications. It was a decent way to get a nice UI up fast, but we quickly found a need to build custom components or go elsewhere. Styling was also a bit of a pain iirc, though I believe things are better with Antd 4+. At my new gig we…

> plus an increasing number of GPT-generated one-off components :)

Sounds interesting, what do you mean by this? Do you have a workflow or process? Is this generating styled reusable components?

Re: Ant Design – the second most popular React UI framework

#42

Post by mikojan »

danielvaughn wrote: post #30

I've worked as a freelancer on a couple of projects that used Ant Design, and personally I hated it. In one case I was working on a real estate platform, so I had to build a listing search page (similar to Zillow). This means you're rendering lots of little dots on the map, and on hover, each one will open a popover with the listing details. Using Ant Design brought this page to a standstill - massive performance iss…

Rendering "too many" components is an issue with most popular React frameworks.

But it is also an issue w.r.t. usability. Group elements and use progressive disclosure instead.

Re: Ant Design – the second most popular React UI framework

#43

Post by diob »

danielvaughn wrote: post #30

I've worked as a freelancer on a couple of projects that used Ant Design, and personally I hated it. In one case I was working on a real estate platform, so I had to build a listing search page (similar to Zillow). This means you're rendering lots of little dots on the map, and on hover, each one will open a popover with the listing details. Using Ant Design brought this page to a standstill - massive performance iss…

I've always defaulted to MUI and never regretted it. Easy to style, customize, and great docs.

Re: Ant Design – the second most popular React UI framework

#44

Post by ajkjk »

danielvaughn wrote: post #30

I've worked as a freelancer on a couple of projects that used Ant Design, and personally I hated it. In one case I was working on a real estate platform, so I had to build a listing search page (similar to Zillow). This means you're rendering lots of little dots on the map, and on hover, each one will open a popover with the listing details. Using Ant Design brought this page to a standstill - massive performance iss…

Was there some reason that Ant inherently require it working that way, as opposed to it being a mistake in the application code?

Re: Ant Design – the second most popular React UI framework

#45

Post by pocketarc »

hreynier wrote: post #41
jumploops wrote: post #37

Most of the Antd components wrap `rc-[x]` components[0] with a stylish UI. In the past we've found Antd doesn't play well with custom components, and can often have weird performance implications. It was a decent way to get a nice UI up fast, but we quickly found a need to build custom components or go elsewhere. Styling was also a bit of a pain iirc, though I believe things are better with Antd 4+. At my new gig we…

> plus an increasing number of GPT-generated one-off components :) Sounds interesting, what do you mean by this? Do you have a workflow or process? Is this generating styled reusable components?

Given it's Tailwind + shadcn, I'd be surprised if it's not v0[0].

[0]: https://v0.dev

Re: Ant Design – the second most popular React UI framework

#46

Post by xigoi »

satvikpendem wrote: post #13
osmano807 wrote: post #7

Isn't there any UI framework alternative for the web that doesn't use JavaScript or Typescript? Something like DaisyUI but using other languages when needing interactivity. Also, tested the DatePicker and it's examples with time is unusable on mobile, renders outside of the viewport without option of scrolling.

I mean, you can use any compile to WASM language and framework like Flutter, Rust, .NET, all of which have their own UI libraries.

But then the UI will be rendered on a canvas instead of using the DOM, which is awful for accessibility.

Re: Ant Design – the second most popular React UI framework

#47

Post by satvikpendem »

xigoi wrote: post #46
satvikpendem wrote: post #13

Earlier quoted context omitted.

I mean, you can use any compile to WASM language and framework like Flutter, Rust, .NET, all of which have their own UI libraries.

But then the UI will be rendered on a canvas instead of using the DOM, which is awful for accessibility.

Not all of them are canvas based, some like Dioxus render HTML and CSS.

Re: Ant Design – the second most popular React UI framework

#48

Post by tobeagram »

Back in 2018, I worked on projects where we used Ant Design. At the time it was one of the best choices out there for a quick project, as it had all the standard components with a relatively good design out of the box. Since all the easter egg fiasco / css bloat I've avoided using it.

These days, there's just much better options such as shadcn/ui [1], chakra [2] or radix [3] which when paired with frameworks such as floating ui [4] are just much better.

[1]: https://ui.shadcn.com/ [2]: https://v2.chakra-ui.com/getting-started [3]: https://www.radix-ui.com/primitives/docs/overview/introducti... [4]: https://floating-ui.com/docs/getting-started

Re: Ant Design – the second most popular React UI framework

#49

Post by hombre_fatal »

ajkjk wrote: post #44
danielvaughn wrote: post #30

I've worked as a freelancer on a couple of projects that used Ant Design, and personally I hated it. In one case I was working on a real estate platform, so I had to build a listing search page (similar to Zillow). This means you're rendering lots of little dots on the map, and on hover, each one will open a popover with the listing details. Using Ant Design brought this page to a standstill - massive performance iss…

Was there some reason that Ant inherently require it working that way, as opposed to it being a mistake in the application code?

It's more general to spawn a portal per component because then you can show multiple popovers at a time, like popovers that are always visible or only go away if you click "Close". So it makes sense to start there for the naive solution.

Re: Ant Design – the second most popular React UI framework

#50

Post by hombre_fatal »

klaussilveira wrote: post #14

How anyone finds this code maintainable is beyond me: https://github.com/ant-design/ant-design/blob/master/compone...

Compared to what? It's a complex component that doesn't get any simpler if you change UI platforms.

And while complex, it's not hard to follow.

Here's the source of DataTables: https://github.com/DataTables/DataTablesSrc (https://datatables.net/)

Post reply on HN