[emseetech]

When building out a new app or site, start with the simplest solution like the html-only autofilters first, then add complex behavior later.

It's good to know these things exist so there are alternatives to reaching for a fat react component as the first step.

[zdragnar]

Until your client tells you that it doesn't work in Edge and you find out it's because every browser has its own styling and they are impossible to change enough to get the really long options to show up correctly.

Then you're stuck with a bugfix's allotment of time to implement an accessible, correctly themed combo box that you should have reached for in the first place, just like what you had to do last week with the native date pickers.

[emseetech]

Right, don't add complexity until you have to.

[abustamam]

I'd argue that adding complexity from the get-go to ensure that all users have a pleasant experience from the get-go is better than simplicity at the expense of some percentage of users.

I think it's important for web devs to spend more than two seconds to think if the complexity is necessary from the get-go though.

[emseetech]

When building out a new app or site, which means a percentage of zero users is zero.

[willparks]

It’s great to see practical examples that push us to consider what the platform already offers before adding more layers of complexity.