Hacker Newsnew | past | comments | ask | show | jobs | submit | lispre's commentslogin

The first reflection of many people on this post is that we already have tools like grep, ag, pt, ripgrep and so on, why you create a more junk thing. my answer is as followed: 1. I just need a simpler and more direct thing, just like "ls" has a lot of options, but I use the most high-frequency only ls, ls -l, ls -la, so every high-frequency use form Have been aliased, I use the highest frequency of grep is the recursive subdirectory search, very high frequency so that I want to create a tool to do only this thing, and do the fastest and best directly

2. In order to rewrite with Rust, I love C, Ada, Zig, and I want to taste Rust now.


But ripgrep's default mode of operation is to search a directory. That is, `so_stupid_search foo ./dir` and `rg foo ./dir` do the exact same thing. Even better, `rg foo` searches the current directory without needing to add a `./` argument.

> and do the fastest

Making tools like this fast is not easy. Your tool is approximately two orders of magnitude slower than ripgrep when searching the Linux kernel, for example.


Thanks for your comments, I will stick to optimizing my ugly code for the people who love small and tiny things


No, it is still bad.

Rust is not for good c/c++ programmer. It is for those who is not familiar with c/c++ but have some knowledge with functional programming.

As a C++ programmer, you can try golang instead of for productive


Rust is not for common project. Rust is only for safety.

I just recommend modern C++ and golang


Just as the data offered by this article, the best choice for the practical job right now should be Golang and OCaml.

if you don't love the two, just try C/C++.


Really? Picolisp was build with asm? not C as SBCL


Picolisp 32bit is C, but 64bit is asm. There is also Ersatz Picolisp which is Java.

All sources are really well outlined, and worth the read through. But you might start with the 64bit's README. [0]

[0] https://software-lab.de/doc64/README


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: