3 ms·
> As a front end dev you are in the business of making products, not managing leap years. Native date pickers are limited in how you can style and customize th
by schwartzworld 4y ago
> As a front end dev you are in the business of making products, not managing leap years.
Native date pickers are limited in how you can style and customize them. As a dev, I'd always prefer a native one, but if design wants a unified look across platforms or any unusual behaviors, bespoke might be your only option.
- likortera 4y agoThen you use an existing datepicker library, and customize it. Writing your own datepicker is 99% of the times a rookie mistake.
- schwartzworld 4y agoWould you not consider the people working on those libraries to be front-end developers?
- selfmodruntime 4y agoThey are developing those for their companies or in their free time. If I‘m hiring a front-end developer I‘m sure as hell not paying them to write custom datepickers all day. Development is full of compromises.
- schwartzworld 4y ago> They are developing those for their companies And what do you think their job title and experience are? > If I‘m hiring a front-end developer I‘m sure as hell not paying them to write custom datepickers all day. This is the opposite of what you said above.
- likortera 4y agoYes, those are frontend developers, we all agree with that. Should every frontend developer be reinventing date pickers from scratch just to demonstrate how good they are? I don't think so. That's why I said 99%. Maybe there's an 1% or even less where it makes sense to reinvent it because you're Airbnb or Amazon or Google or you are in the date pickers business. But yes, you are still a frontend developer if you don't do your own datepicker and focus on shipping your company product. And date pickers are built by frontend developers. What's your point?