> It's not quite "copy and paste this component". When I google "typeahead react" the 1st link is a pretty popular npm package that seems to support everything

> It's not quite "copy and paste this component". When I google "typeahead react" the 1st link is a pretty popular npm package that seems to support everything I want (and some stuff I didn't even know I wanted). > it's more like "which framework is easier to blindly stumble through (with ChatGPT's help) to get what I want". I understand the sentiment but tech-wise it's a good thing that it's harder to do. The other way would have you installing a (probably large) dependency, of which you'd use perhaps use 10% of its capabilities, expecting a response from the server that you might not have, and add more custom CSS that you'd have to wrangle together with your own styling. Which might be fine if it's just you and you understand the tradeoffs, but if it was a team of 20 people each of them would do the same thing and the app would grow by accretion. Not just in size but in complexity. Which would necessitate more build tooling, more tests, maybe even changes to infrastructure... Cobbling together things like that, while fast and fun, isn't necessarily great engineering. Sometimes we all have to do something quick and dirty, sure, but being forced to take a step back to think it through isn't a bad thing.