41–50 of 208 posts
It says start typing to search. So i started typing and it didn't search. I really expected it to be some sort of typeahead search without requiring focus on the the search field :)
Query autocomplete is on the roadmap :)
One feature request at first glance: please default to the system font stack for code snippets. I see you're currently using Consolas, a Microsoft typeface, which is not pleasant to see as a mac user.
You can use this to default to the system font on every platform:
font-family: "SF Mono", "Monaco", "Inconsolata", "Fira Mono", "Droid Sans Mono", "Source Code Pro", monospace;I searched the following in say hello.so.
"Service worker fails on request for audio file"
I got back a couple of results related to general service worker use but none that get close to discussing the core problem that lead to the solution.
The same query in Google returns several results that together pointed me to the solution (it was around range headers in requests for media data types).
This is just one example though. I think the problem you are trying to fix is worth the effort. I just wonder if this is where humans are still stronger than computers - gathering unstructured data to use in problem solving.
Congrats on the launch! Looks promising, so I'll try it out for a couple of days. One feature request at first glance: please default to the system font stack for code snippets. I see you're currently using Consolas, a Microsoft typeface, which is not pleasant to see as a mac user. You can use this to default to the system font on every platform: font-family: "SF Mono", "Monaco", "Inconsolata", "Fira Mono", "Droid Sa…
It would be a good idea to preserve whitespace, or arguably better, integrate optional syntax formatting
Overall, this search engine looks promising
Pretty decent overall. Though some code that comes back is a little dense and hard to read. This appears to be caused by how the scraper/parser handles whitespace. For example, the query "make a curl request in php" returns an example from the comments section in the PHP docs where the entirety of the comment has been returned as code, but the tags have not been converted to newlines. It would be a good idea to prese…
Pretty decent overall. Though some code that comes back is a little dense and hard to read. This appears to be caused by how the scraper/parser handles whitespace. For example, the query "make a curl request in php" returns an example from the comments section in the PHP docs where the entirety of the comment has been returned as code, but the tags have not been converted to newlines. It would be a good idea to prese…
I've played around just a bit and clicked some of the preset examples and like what I'm seeing so far. I bookmarked it and will try it out more as I code over the next few days.
Main initial feedback: I'd really like to see version/last-updated-at info accompanying all results. One of the biggest problems with Google for code stuff is finding outdated examples and docs. Even better would be a dropdown that lets me see results depending on the version of the language/framework/tools I'm using.
The answer never loads if using Brave with Shields up, even after allowing JS.