Live data from Hacker News

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

github.com

131–140 of 190 posts

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

#131
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…

Any plans about create a library around this tool?

I'd be very happy to merge such a PR. Do you have a specific use case in mind?

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

#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...

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

#133
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…

Not too many direct deps

Networking: pnet, ipnetwork, trust-dns-resolver,

UI: tui, termion, structopt (CLI is UI)

Utility: signal-hook, failure, chrono, regex, lazy_static,

Async: tokio, async-trait

None of those seem egregious.

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

#134
post #65

Earlier quoted context omitted.

My complaint about the name is that it would be hard to "google" it. This means if I don't bookmark it or remember where I found it, then a couple of years from now when my laptop needs to be rebuilt, I'll have the darndest time finding it to install it again.

This effectively made github my second search engine. We should have an AskHN on how to find software in general.

I’m using multiple search engines more and more. Possibly this is due to me usually bypassing google to avoid the ad laden hits. A view with search results from a few sources comes to mind as a solution. Another back burner project.

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

#135
post #108

Earlier quoted context omitted.

Every browser has book marking syncing in some capacity these days. It's the equivalent of losing contacts with a new phone in 1999.

Not without creating an account, on Android. Chrome has no other export functionality. And firefox copied that lack-of-feature without even realizing the motivations. So now one have to copy them one by one.

I must be misunderstanding something here, can you please explain the missing feature?

I load a set of bookmarks into Firefox on client machines regularly, but I suspect this isn’t what you are discussing.

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

#136

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 find my use of bookmarks is usually write-once read-never

I found this with Instapaper. What was a bookmark and what was a read-later?

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

#137
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.

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

#138

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 ...)

A good name would be "nettop"; it's so good that several projects (on github alone) have already used it as the name of some network monitor. The shortened "ntop" is also taken. At least two projects have claimed "iptop".

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

#139

Earlier quoted context omitted.

This is one of the biggest problems I've had with any neat Rust thing posted up here. The language changes a lot. I have rust/cargo 1.37.0 installed (it's the latest marked stable in Gentoo) and adler32 v1.0.4 fails to compile with "`core::slice:: ::len` is not yet stable as a const fn". I'm installing 1.40.0 from the unstable tree to see if that will build it. I've had situations where I'm either not on the latest v…

There's no such thing as a "too current a version of rust". All Rust compilers (since 1.0) compile all previous versions of code and will continue to do so. In the rare case you might hit something that was removed/modified because of a security exploit, but those are very very rare.

This is not true in practice. Old code has failed to compile for various reasons; off the top of my head, new additions to the prelude, and denied lints that became more restrictive. It's not super rare.

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

#140
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?

Depends on the size. It’s not unheard of.
Post reply on HN