3 ms·
It's kind of hilarious to see hacker news discover the second iteration in the series of three rewrites. This started with bashtop, then bpytop, and now it's bt
by anarcat 5y ago
It's kind of hilarious to see hacker news discover the second iteration in the series of three rewrites. This started with bashtop, then bpytop, and now it's btop.
There are probably dozens of HN stories discussing those too.
Can I call this a dupe? :)
- arglebargle123 5y agoShould we start a betting pool on how long it'll take him to rewrite it yet again in Rust? I give it a year.
- johnisgood 5y agoNot sure why he would do that. Seems like the issue was more or less bad performance, and that has been fixed by using C++.
- entropicdrifter 5y agoMemory management bugs are the only reason I could think of to switch from C++ to Rust
- seanw444 5y agox86 assembly re-write in 3.
- smoldesu 5y agoBottom exists[0], if you're looking for a rust-based resource monitor it's pretty much the best in the biz. [0] https://github.com/clementtsang/bottom https://github.com/clementtsang/bottom