Live data from Hacker News

What: A terminal tool to check what is taking up your bandwidth

github.com

161–170 of 190 posts

Re: What: A terminal tool to check what is taking up your bandwidth

#161
post #75

Hey, I am the author of "what" and am very happy to hear people like this tool I made. :) "what" was my first real attempt at rust, and I love the project very much. That said, it is a hobby project - and so I will likely be a few days responding to all issues and contributions that came from this thread. "what" has already received some great contributions that are major parts of the code base. I would be very happy…

What are your thoughts on Rust so far? What primary language(s) did you come from? I've been planning to learn Rust but haven't made the leap yet because I expect a big time commitment due to the learning curve. I poked around your source code and it was inspiring. Your code looks simple and straightforward compared to some of the other Rust projects I've examined.

That's high praise - thank you very much for saying so.

My major language in recent years has been javascript (and years before that perl). Rust was a breath of fresh air for me as I did not previously have "access" to system-level functionality.

I very much love the ease with which I can rely on other people's code (feels like home coming from node.js) - even though as mentioned in this thread it does have its downsides (eg. longer compiler times).

The learning curve is indeed challenging, but the tooling is amazing, the compiler has better error messages than I could even have imagined, and the community is incredibly friendly and welcoming. All in all, I'd say it's worth the effort. :)

Re: What: A terminal tool to check what is taking up your bandwidth

#162

Bad naming.. WHAT(1) BSD General Commands Manual WHAT(1) NAME what -- show what versions of object modules were used to construct a file (MacOS ...)

This is the main problem keeping me from using this right now. I don't like installing binaries that conflict with system package names because I'm tin foil about stability and the super small chance that some installation/config script for some other package I rely on references `what` and breaks. @imsnif 2 questions: 1. Any chance you'd be willing to rename the package? I get it if not, but that would be so dope. 2…

1. Done. It's now known as "bandwhich" 2. This is in progress: https://github.com/imsnif/bandwhich/issues/9

Re: What: A terminal tool to check what is taking up your bandwidth

#163
Thank god for the name change! I saw this project this morning and it looked super interesting. I tried googling around for it to install it, but nothing worked haha "bandwith monitor what", "github rust what", etc. And this is coming from a hypocrite who's most popular project is named 'c'.

Bandwhich is a clever and easy to find name!

Re: What: A terminal tool to check what is taking up your bandwidth

#164

Earlier quoted context omitted.

Tons of stuff. Various aspects of dependencies, for example, should this affect resolution? Is this a semver range? A minimum version? Is whatever we choose reasonably forward compatible for any extensions we might pick in the future? Can you write `cfg` attributes based on versions? Many of the same questions apply there. Etc etc etc. It took about a year to get stuff figured out.

I also suspect that if the plan is to add this as an attribute that developers put in Cargo.toml then there will be a lot of packages that will have the value set to a higher version than need be. Speaking for myself, I don't know in which exact version of Rust the features that I use was first introduced, and I don't think anyone else knows that either if they use a lot of different Rust language features. So if I w…

I’m imagining that’s too much resources, yeah. It’s the same issue with anything that’s created by people; I’m sure that it’ll be fine over time. If and when we do LTS releases that’ll make it easier too...

Re: What: A terminal tool to check what is taking up your bandwidth

#165

Earlier quoted context omitted.

That was a response to them having an issue with losing bookmarks. Are bookmarks in general now a negative onus?

As search engines have gotten better over the years, I find my use of bookmarks is usually write-once read-never. Part of that is due to the fact that iOS is now my primary consumption platform, and finding bookmarks in a complex structure is much more awkward than it should be. Part of it is just laziness: trying to manage a complex bookmark folder is more work than I care to do when search engines give me 99% of wh…

I even pay for pinboard and barely use it.

It'd be great if every time I went back to a website, all the pages on the site that I already bookmarked would pop in a sidebar...

Re: What: A terminal tool to check what is taking up your bandwidth

#166

What's the difference between what and nettop? Other similar tools: nettop iptraf iftop nethogs

I immediately thought if iftop and iptraf

https://www.binarytides.com/linux-commands-monitor-network/

There's already a ton of tools that do this. It's a nice show-off project but I doubt OP is in for the long haul.

Re: What: A terminal tool to check what is taking up your bandwidth

#167
post #159
post #132

Getting an error: .cargo/registry/src/github.com-1ecc6299db9ec823/bytes-0.5.3/src/bytes.rs:121:18 | 121 | len: bytes.len(), | ^^^^^^^^^^^ error: aborting due to previous error error: Could not compile `bytes`. warning: build failed, waiting for other jobs to finish...

It requires a very recent version of rust. Do a 'rustup update' to get the latest stable release. You can't use the distribution's packages for rust and cargo if you want to play new rust programs.

Makes sense.

Re: What: A terminal tool to check what is taking up your bandwidth

#168

Bad naming.. WHAT(1) BSD General Commands Manual WHAT(1) NAME what -- show what versions of object modules were used to construct a file (MacOS ...)

cargo install what (fails) Package `trust-dns-proto v0.18.0` does not have these features: `tokio-compat` (MacOS 10.15.2)

First, it’s really cool that their using trust-dns! Second, they probably want to upgrade to the 0.18 release. It’s interesting that the cargo.lock file didn’t restrict the package versions for this case.

Anyway, this tool should probably upgrade to the current 0.18 release now that it’s out, if possible.

Re: What: A terminal tool to check what is taking up your bandwidth

#169
post #129
post #17

Installation with yay/crate can be slow. This small tool took 4 minutes of compile time, the Rust crates seem to be very fine granular (like node.js vor example) and require much compile time. 204 crates needed to be compiled. I found that, using yay or another aur helper on arch linux, having a few rust utilities installed that have regular updates, significantly slows down the average system upgrade time. I tend to…

204 depedencies?! Is that normal for a Rust project?

Rust has a really good package manager, so it's pretty standard for projects to depend on a lot of things just from that.

Re: What: A terminal tool to check what is taking up your bandwidth

#170

Earlier quoted context omitted.

This is in the top class of utilities (htopm etc). A good name could probably be bwtop, or tcptop or iftop. Actually I searched for these, and turns out iftop exists! ( https://linux.die.net/man/8/iftop )

whatif or whif would be great names

i really like whatif.

whif less so, that just doesn't seem to smell right.

Post reply on HN