lobsters score: 1 · tags: release
This will sound flippant but I really don’t mean it to be: what exactly does this fork give me over the old abandoned one (RIP yorhel)? I’ve been using ncdu forever and it kinda just works, does everything I need it to and I’ve never encountered a bug. And it’s not like POSIX is a fast-moving platform where the tool needs to be kept up to date with new APIs
score 1 · canonical
This project carries significance for me, not only as a learning resource but also for future projects which is why I’ve forked and will aim to maintain it for the foreseeable future. I’m still getting familiar with the codebase beyond what was required to update it so any potential issues will be handled on a best-effort basis. I didn’t see any actionable issues in the issue tracker but that doesn’t mean there aren’t things that can be implemented or improved upon. I aim to implement some form of CI/CD at some point as well.
score 1 · canonical
Could you tell us a little about the post-fork work you have done so far? The commit messages are not very descriptive and some of the diffs are quite big. On a quick glance it seems to be focused on keeping up with Zig language and library changes?
score 1 · canonical
That’s about it. The noisiest parts of the diffs are
zig fmtand Zig 0.16’sIochanges. If you view them with whitespace changes disabled, it should be easier to parse. I think the original project was mostly feature complete save for maybe multithreaded scanning. I want to update the README with installation instructions and so on at some point as well. Future projects based on this project will feature more opinionated changes.
score 4 · canonical
How does this compare to https://github.com/BratishkaErik/ncdu (packaged in nixpkgs)?
score 1 · canonical
I don’t want to put down someone else’s efforts or project. As I stated in another reply in this thread, there are some decisions that were made that I would not have and will not make. That this project lives on with more than one fork shows its original significance. I think that’s what counts.
score 1 · canonical
If you are interested in some constructive critisism I would suggest separating commits containing fixes or features from commits marking a new version.
score 1 · canonical

