I added semantic search to my React app without a backend (and it's under 1ms)

<h2> Search Is Harder Than It Looks </h2> <p><code>LIKE '%query%'</code> works until:</p> <ul> <li>Your table has 100k rows (Seq Scan, slow)</li> <li>Users misspell words (no

<p>Most semantic search systems don’t fail because of embeddings. They fail because of how the system is designed around them.</p> <p>When I started building a semantic search API

<p>I added search to all three of <a href="https://dev.to/articles/three-sites-experiment">my AI-curated directory sites</a> last month. The choice wasn't obvious — there are at

<p>Whenever someone asks me to add search to an application, I try to find ways around it. The implementation itself isn't the problem, it's everything that comes with it: extra

<!-- SC_OFF --><div class="md"><p>We spent the last year building a code indexing system and tried pretty much every retrieval approach along the way. Sharing what actually worked

<p>\n</p> <p>Documentation search is the silent killer of developer experience: 68% of users abandon docs sites that take more than 2 seconds to return search results, and 42%

<p>If you're an engineering leader at a dev-tools company, an AI infrastructure platform, or an API-first SaaS, there's a good chance your marketing site is a React SPA — Vite,

<p>Munchable answers one question: does this food fit the gut condition you live with. Until recently there was exactly one way to ask it, which was to hold a phone camera up to a