This is practically the most useless project becuase you can not run it without sudo permissions, but it was insanely fun to work on it
supports ext4, btrfs, and apfs. Multithreaded, supports compression, nested volumes, and can even search detached volumes like .iso and .dmg without mounting
An interesting bonus point: you can't really vibe code it cause clankers can not run sudo commands
it is absolutely amazing experience on mobile if you guys do not understand how to use a search bar and a couple of segmeneted controls -- there is nothing much I can do about it
I have open sourced the fastest code search implementation. Comprehensive SDK for both file finder and grep file search that is over 100x faster than ripgrep
I agree though the main problem for me is not the API it's missing functionality of patterns like ./*/*.c. There is a very long running thread in the gnu mailing list where authors do not like this idea.
While I need this because everyone expects it to be available. Another reason is the API for thing like someone else asked here already (match in memory over a list of paths)
That's one of the reasons I built zlob. It literally has an endpoint to do this but if you are talking about glibc there are 2 options
1. fnmatch function which is not ideal because it doesn't take into account all the path specific optimizations and does not support BRACE
2. ALTDIRFUNC flag for globbing let you simulate file system which absolutely sucks
in zlob you can simply call zlob_match_paths(<pattern>, <list>, flags, ptr)
where list would be either c string or rust/zig like slices
100% POSIX and glibc compatible globbing library for C, Zig, and Rust that is faster and supports all the modern globbing formats (more than libc and rust glob crate)
It supports all the formats like * and {a,b} expansion as long as have a very efficient syscall and SIMD optimization for faster processing
I printed a lot of gears from this website (well I built it because I had to print a lot of different gears) and they came out very nice and reinforced. If you use the optimized for 3D printing export it doesn't need anything from your printer software to just print it, and they mesh with existing gears just fine (for sure if you calculated module correctly)
Libraries are simple: threejs for preview, meshlib for watertight export, used some frontend framework for state management too
more correct would be - do not use kernel file system