3 ms·

Compare the native picker to e.g. one from antd: https://ant.design/components/date-picker/ https://ant.design/components/date-picker/ Actually, compare every

Compare the native picker to e.g. one from antd: https://ant.design/components/date-picker/ https://ant.design/components/date-picker/ Actually, compare everything they have to native elements. If the project can afford it (in terms of bundle size, etc — it's fine for intranet), I don't even bother with native controls anymore.

neogodless 2y ago
I'm on a sub-optimal connection, so the Ant Design one took me about a minute to be responsive, while the native one worked in seconds. I also am confused by this Ant demo page. Is every single date item supposed to be selected in a different element? In this comparison, I vastly preferred the native date picker over the Ant ones. But I am probably misunderstanding the demo page. Or maybe it's just giving you "too many" options? I just need to pick a date and this seems like overkill, at best.
- spookie 2y ago
  I'm not in the most common browser and even for me, with a good connection, it took a while to load.
- test6554 2y ago
  Better native standards could mean ant.design updates their components to use less js with the same ux. So everyone still wins.
Y-bar 2y ago
I really like my native pickers and UI compared to those examples. I can start with the fact that those are not usable on iOS 18, and they took almost a minute to load.