kurtextrem

I found this prompt works well to nudge it to use a better grep as the start, then just keep using grep (Cursors instant grep in my case):

``` - For planning, prefer using morph-mcp `codebase_search` - subagent that takes in a search string and tries to find relevant context. Best practice is to use it at the beginning of codebase explorations to fast track finding relevant files/lines. Do not use it to pin point keywords, but use it for broader semantic queries. "Find the XYZ flow", "How does XYZ work", "Where is XYZ handled?", "Where is <error message> coming from?" ```

(see also https://news.ycombinator.com/item?id=48205911; having higher quality results at the beginning of a thread seem to improve the output vs. having faster search later on).

Have you tried https://github.com/mksglu/context-mode? I prefer it over rtk / headroom (at least in Cursor). The stop hooks seem to work well / prevent the agent from blowing up its context window.

Related read (not from me): https://entire.io/blog/improving-agentic-search-in-coding-ag...

The clearest result was that faster search alone only modestly helps, while better-ranked results improve first-query retrieval and help agents find the right code sooner.

Their tool "pgr" is a research preview only, so it'd be interesting to see semble vs pgr.

I'm also collecting other tools that are similar, most notably is probably Morph's WarpGrep (has a free tier too). Apart from that, there is codemogger (https://github.com/glommer/codemogger), cs (the author also commented in this HN post).

In the similar area, but not fully related, the author of fff is also pretty involved in any thread that goes into that direction (see e.g. https://x.com/neogoose_btw/status/2052161471296225710). Similar to colGREP is also mgrep (by mixedbread) and osgrep (but they seem to predate colGREP). I also found codedb on X (https://codegraff.com/blog/codedb-code-intelligence), the post reads well, but haven't tried.

Just stopping by to say this is great usage of the new APIs.

How does it compare to jpegli?

Also, the vite team in collab with a few others is building https://rolldown.rs/, to replace esbuild and rollup in vite. It's goal is to be faster than esbuild, with extended chunking options and so on.

I'm not entirely sure if we can really tell anything about esbuild from that comparison, as vite's production build time is 1300ms (which uses rollup), but dev startup time 1100 (uses esbuild to prebundle). It seems like vite itself has overhead.

The only bench I'm aware of was presented in November 2023: https://x.com/boshen_c/status/1719596594985681275?t=x8FaB9Aw..., where esbuild was faster.

"xylitol-sweetened (30 g) water, an exposure comparable with a pint of numerous xylitol-sweetened ice creams, a xylitol-sweetened bakery good, or several pieces of xylitol-sweetened candy" (source: https://www.reddit.com/r/science/comments/1d9ql2u/comment/l7...)

Anything for Nancy pelosi?

Really cool stuff!

It tells me that its knowledge cutoff is Nov 2023. So pretty recent.

just curious, what's the difference to the other extensions doing this?

what happens in chrome, where afaik google's dns is the default?

do you know why Jon didn't compare near-lossless in the "visually lossless" part?

the jpegli progress is so awesome to see

Made also a JS implementation based on the golang one here: https://github.com/kurtextrem/js-sieve. It's a bit different than your reference implementation.

When I download the Windows .exe using Chrome, it says "Malicious download blocked", just fyi

I like the idea, it's nice. Thank you

Am I missing something or was exactly something like this on "Show HN" the last days? https://news.ycombinator.com/item?id=38327017

been using for longer now and I still love it the most. Might try Ghost from Vercel, or GHs latest font to compare, but every other mono font didn't come close to the italics and general style

I like your approach and it feels like you thought of everything that is needed for solving the problem your company has. The usage of immer also shows you put careful thoughts into it.

However, I wonder: is your company the only one out there with this specific problem? Has no one else tried to solve this in the react landscape based on the libs you've put in the readme?

Back in the days, when JSON became popular as response type for rendering in the client, I saw arguments such as "the JSON payload is smaller than sending full HTML, so you pay the download only once instead of N times". Only once, because what has to be done with the JSON has been downloaded in the JS bundle. With full HTML, full HTML comes back in every response.

However, I'm not sure if this is actually a problem or rather depends on how much interaction the user does (so where is the "turning point" of the overhead of having all in the bundle vs full HTML responses). What does everyone think?

Small heads-up, you might want to look at the PRs (I've opened the single open PR) :D

Take a look here: https://github.com/ascorbic/unpic-placeholder. Recently created by a Principal Engineer of Netlify, which kind of server-side-renders BlurHash images, so that they don't tax the mainthread. Maybe the same can be done for ThumbHash (I've opened an issue in that repo to discuss it)

Literally no one who is used to the Silicon valley comp will move to a new country for around half the pay in order to celebrate the Oktoberfest. Wtf.

Crazy results, really interesting experiment!

Idk but, at least from Germany Twitter now loads slower. The comments below Elon's tweet load slow, my home timeline loads slow, even the notifications load slow. Before the "reduced by 400ms" change everything was faster for me (I never understood who perceives the Android app or Twitter in general as slow - NOW I do).

I'm guessing a dev made US calls faster, so that he/she can tell Elon it's faster without mentioning for the US only.

If an official blog post, meant for regular users, lists using the search of Chrome Dev Tools to find hidden content instead of the actual Ctrl+F search: "in Chrome, you can search from within Developer Tools to match against all rendered text, which would include the text in drop-down menus and other areas of the site." it is maybe time to change the Ctrl+F search instead of recommending regular users to use developer tools.

Yet another BGP caused outage. At some point we should collect all of them:

- Cloudflare 2022 (this one)

- Facebook 2021: https://news.ycombinator.com/item?id=28752131 - this one probably had the single biggest impact, since engineers got locked out of their systems, which made the fixing part look like a sci-fi movie

- (Indirectly caused by BGP: Cloudflare 2020: https://blog.cloudflare.com/cloudflare-outage-on-july-17-202...)

- Google Cloud 2020: https://www.theregister.com/2020/12/16/google_europe_outage/

- IBM Cloud 2020: https://www.bleepingcomputer.com/news/technology/ibm-cloud-g...

- Cloudflare 2019: https://news.ycombinator.com/item?id=20262214

- Amazon 2018: https://www.techtarget.com/searchsecurity/news/252439945/BGP...

- AWS: https://www.thousandeyes.com/blog/route-leak-causes-amazon-a... (2015)

- Youtube: https://www.infoworld.com/article/2648947/youtube-outage-und... (2008)

And then there are incidents caused by hijacking: https://en.wikipedia.org/wiki/BGP_hijacking#:~:text=end%20us...

This is a clever trick (using mousedown to trigger a click), but breaks drag & dropping links, drag & dropping links to new tabs. and there is also a thing I tend to do: If I notice I pressed the mouse button down on the wrong link, I move the cursor away from that link and let the button go up on the correct or in free space, so the browser doesn't navigate (not sure how common this behaviour is, though)

Same issue here, worked months before but last few days really random.