Sloc Cloc and Code Revisited – Optimizing an Already Fast Go Application

Re:Sloc Cloc and Code Revisited – Optimizing an Already Fast... by drej on Tuesday December 25, 2018 @09:03AM (#18757431)

I only skimmed this, but why isn’t ripgrep mentioned? (While other Rust-based tools are.)

By the way, ripgrep author has a good writeup on performance comprison. https://blog.burntsushi.net/ripgrep/

[ Parent | on HN ]

Re:Sloc Cloc and Code Revisited – Optimizing an Already Fast... by ramchip on Tuesday December 25, 2018 @11:09AM (#18757880)

Ripgrep is heavily covered in a previous article: https://boyter.org/posts/sloc-cloc-code/

[ Parent | on HN ]

Re:Sloc Cloc and Code Revisited – Optimizing an Already Fast... by steveklabnik on Tuesday December 25, 2018 @09:16AM (#18757490)

Ripgrep is a similar but different kind of tool.

[ Parent | on HN ]

Re:Sloc Cloc and Code Revisited – Optimizing an Already Fast... by boyter on Tuesday December 25, 2018 @04:15PM (#18759248)

99% the reason I didn’t put ripgrep in there. Ripgrep, sift, Ag, pt, ack solve a totally different problem to scc, tokei, loc, polyglot and cloc.

The last 1% was because I didn’t want to have any comparisons made against ripgrep because early in scc’s development I was slightly comparing walk performance and ended up having a chat with burntsushi over twitter. To avoid marking more work for him I was careful to avoid any comparisons, as the last thing we want is him distracted from working on that and other tools.

[ Parent | on HN ]

Re:Sloc Cloc and Code Revisited – Optimizing an Already Fast... by drej on Tuesday December 25, 2018 @02:58PM (#18758952)

Of course, silly me, I take loc and ripgrep to be so essential I conflated them. Too much Christmas merriment, not enough proper thinking. Sorry.

[ Parent | on HN ]

Re:Sloc Cloc and Code Revisited – Optimizing an Already Fast... by steveklabnik on Tuesday December 25, 2018 @03:51PM (#18759157)

It’s all good! Have a great Christmas :)

[ Parent | on HN ]