I don’t think you’re in the minority. That seems like a pretty common use case. The graphs aren’t pre-populated, they start from when the tool starts. Although zenith does have a persistent history feature that lets you navigate data from previous invocations.
I don’t find bottom’s graph (that one that displays usage for each individual core) to be very informative in your screenshot. Maybe they weren’t designing for so many cores :)
I need a large screen at work and a script to run all four of these at once in a tiled configuration. Then I can just have it going in the background of our open-plan office when The Boss is giving tours to prospective clients.
I don’t see why a lack of updates is a bad thing for bb, it’s not like top is very complicated. Why should it need to be updated?
In general, I dislike this idea that code always needs active maintenance. Projects can just be finished. It’s not like you’d critcise the original Super Mario Bros for a lack of updates. The game works. It’s finished. The bugs it has are basically features by now ;)
In general, I dislike this idea that code always needs active maintenance.
In general, so do I.
I don’t see why a lack of updates is a bad thing for bb, it’s not like top is very complicated. Why should it need to be updated?
Because the bugs in the issue tracker would indicate that it’s not finished (no offence to epilys intended there). epilys did indicate it was a weekend project so it would be perfectly reasonable to leave like this. As far as comparing them for my use though, development progress/completeness was relevant to me so I mentioned it.
You just reminded me I’ve written a small update and haven’t shipped it yet :) Process signaling using pidfds to prevent race conditions.
I might be in the minority here, but I tend to:
So I have the following questions:
I don’t think you’re in the minority. That seems like a pretty common use case. The graphs aren’t pre-populated, they start from when the tool starts. Although zenith does have a persistent history feature that lets you navigate data from previous invocations.
I don’t find bottom’s graph (that one that displays usage for each individual core) to be very informative in your screenshot. Maybe they weren’t designing for so many cores :)
Yes possibly. I figured it was a good machine to test them on for that reason. :-)
I need a large screen at work and a script to run all four of these at once in a tiled configuration. Then I can just have it going in the background of our open-plan office when The Boss is giving tours to prospective clients.
I don’t see why a lack of updates is a bad thing for
bb, it’s not liketopis very complicated. Why should it need to be updated?In general, I dislike this idea that code always needs active maintenance. Projects can just be finished. It’s not like you’d critcise the original Super Mario Bros for a lack of updates. The game works. It’s finished. The bugs it has are basically features by now ;)
In general, so do I.
Because the bugs in the issue tracker would indicate that it’s not finished (no offence to epilys intended there). epilys did indicate it was a weekend project so it would be perfectly reasonable to leave like this. As far as comparing them for my use though, development progress/completeness was relevant to me so I mentioned it.
Very fair. Gripe retracted :)