It's not about my search engine, though. It's about any new search engine. It's about the future possibilities. I care about how my customers experience Circle

It's not about my search engine, though. It's about any new search engine. It's about the future possibilities. I care about how my customers experience Circle. If your customers care about privacy and security and browse with JavaScript disabled by default, they will be annoyed. If they have disabilities and use a screen reader, they're likely screwed. If they get lost in your docs and decide to use "site:circleci.com" query to find the page they need, they will get nothing. If they would want to use a mini-crawler to download your docs for local usage, they will get nothing. That is user experience, and those things are objective. They either work or not. On the other hand, performance gains and development time gains of single-page apps are -- debatable. If you were to create a new search engine, and it didn't take into account one-page-apps, I'd say you've built the wrong architecture too. There is no reliable way to build a search engine that would crawl through websites created mostly in an imperative language. Even unreliable ways to do that are complicated enough that Google and Microsoft fail miserably at them.