4ms could be one whole frame for e-sports games like Valorant, Counter-Strike or Dota... There is a lot of stuff that you can do for 4ms, you can render all raytraced shadows in a frame for 4ms. Now, yeah some types of problems are bottlenecked by bandwidth/CPU communication, but even on CPU side only, 4ms is huge amount of time for computers that are as fast as today's machines. Anyway I like Zed, and I like work you guys do. Wishing you more perf wins, reducing some more miliseconds.
I suspect the real magic is in the query.stream_find_iter that you’re not showing here. Because my first thought was to make an iter that walks slices across a string, filter for matches and then rayon it
awesome read.
now can substack please install a code highlighter (it was painful indeed)
4ms could be one whole frame for e-sports games like Valorant, Counter-Strike or Dota... There is a lot of stuff that you can do for 4ms, you can render all raytraced shadows in a frame for 4ms. Now, yeah some types of problems are bottlenecked by bandwidth/CPU communication, but even on CPU side only, 4ms is huge amount of time for computers that are as fast as today's machines. Anyway I like Zed, and I like work you guys do. Wishing you more perf wins, reducing some more miliseconds.
Not a case of "let the compiler do the optimization" :-)
Is this a rust trait? haha
I suspect the real magic is in the query.stream_find_iter that you’re not showing here. Because my first thought was to make an iter that walks slices across a string, filter for matches and then rayon it
I can't wait for Zed for Windows and BSD.
Great article!
A code highlighter would have definitely helped, on top of that reading on mobile made it much harder!
Why do you use arcs for ahocorasick and regex? Shouldn’t be needed.