Stats – macOS system monitor in your menu bar
github.com
github.com
It's fantastic for catching when a bunch of processes haven't been killed and are stuck at 100%. For figuring out if my code is actually running on the GPU or not. For seeing what my network transfer rates are, when a download or transfer gets stuck, and which process is suddenly downloading hundreds of megabytes without telling me?
It gives me the security I have a top-level overview of what my computer's up to. Can't imagine my menubar without it.
Back in the old days the fans going to 100% was a good bug finder. But computers can be so quiet now, you have to use your eyes ;)
Exactly! I've been using iStat Menus for years and I find it invaluable. I've been able to identify system-wide problems a few times already just by glancing at the graphs and going "huh, that should not be happening right now". And it's not just stuck processes, but also misbehaving processes.
I did blog about this situation over a year ago here: https://blogsystem5.substack.com/p/hard-disk-leds-and-noisy-... :)
The activity monitor in my dock set to show CPU is sufficient for my needs.
I used to open up Activity Monitor, but every single time my laptop fans kick on, it was the browser. with the browser performance monitor, i can see exactly which tab is being naughty. So now, I skip Activity Monitor and go straight to the source. Usually, a cmd-R on the offending tab brings it back under control. I assume some JS dev has not tested their code by having it running in a tab for an amount of time other than how long it takes to test their changes.
`about://performance` doesn't work at least from my FF, but `about:performance` redirects to `about:processes`
the // was just muscle memory/brain fart/oops
i never really noticed it redirected to processes.
It may have been just one of the display modules, as I didn’t use the default set, but I never felt like tracking it down, so I uninstalled it.
Every now and then, I try reinstalling it, but it still crashes the system. Not a big deal. Just eye candy.
For me, it doesn’t really have a ton of actual utility. It’s more of a “toy,” so I don’t really lose sleep over it.
I’m sure it works fine, for the vast majority of folks, so it’s obviously not something the authors worry about.
My first computer (a VIC-20) had 3KB of RAM. There was so little memory, that I had to write most of my software in 6502 Machine Language.
I learned Photoshop 2.5 on a 5MB RAM/40MB HDD Mac IIvx (512KB video RAM, hell yeah). Seems incredible now, but that capability after upgrading from a pre-Windows 286 felt incredible then.
Now my Apple Silicon machine bogs down when everything’s trying to use the same core for UI I guess, and each browser tab consumes more resources than Mac OS 7.
That was a top-of-the-line Mac, back then. On a par with a maxed-out Studio.
It made more sense when I used a dirt cheap computer and squeezed every Hz of it.
These days i keep Little Snitch's network monitor around, which i actually do look at sometimes, though mostly to get a glance at where my traffic is going.
Another #TIL for Apple hidden features
IMO it's essential to see cpu / mem / network consumption at all times and, on top of that, the top 5 apps consuming each one of them. It should be a default feature of computing devices by now, but it's so far from that which only benefits bad actors (resource hogs, bad software). I shouldn't have to launch activity monitor every time I want such basic info.
I'll try this out.
Why?
It used to be that noise from hard drive activity and fans spinning up were a pretty good proxy for this, like how my iMac G5 would do its best impression of a jet engine whenever a flash ad banner appeared on screen. These days on M-series Macs though a random browser tab can be keeping a whole core pegged in the background and the only reason I’d notice is if I happened to touch the bottom of the laptop and notice it’s slightly warm.
I might be bad at my job but it’s not uncommon for me to design something and discover it’s sucking back resources to some crazy degree. I don’t want to discover that in flame charts way after the fact. I’d rather see it in real time and diagnose the issue early on in the process.
Lets you build intuition about what is normal vs abnormal. And it's also essential for letting you perceive which apps are bad citizens (and good citizens). Try one of these tools out for a month and you catch all sorts of random things.
Funnily enough, the computer's fan used to perform part of this role. But that has increasingly gone away as laptops become increasingly silent.
Once I randomly opened Activity Monitor on my M1 Macbook only to find that vim was using 100% of a CPU core, and the timer said it had been in this state for days! It wasn't even in the foreground of any terminal tab. Just in a spinloop in the background doing who knows what. And it might have stayed like this for a year until I'm forced to reset the computer for an update.
Another example that you might find more compelling is when your computer's network jumps to 5MB/s. It should always be explainable.
https://github.com/lpar/RedPill/issues/8 (the screensaver I use)
https://www.jwz.org/blog/2023/10/xscreensaver-6-08-out-now/ (linked from there)
Maybe I should submit a PR with this workaround.
Basically Apple made a new "safe" API for screensavers (via .appex) but is only using it internally. 3rd party screensavers must still use the old unsafe API (that uses plugins, so unsafe code).
To bridge that gap, Apple made legacyScreenSaver, an .appex that loads the plugin code. It's a great concept in practice, but the implementation has been a mess since macOS 10.15 (Catalina...), breaking many things (multi monitor support was a big one, broken in many different ways over the years). Some Apple built in screensavers haven't been ported to the new API, so you may still have issues with legacyScreenSaver without that.
With macOS 14, Apple broke it again and indeed, legacyScreenSaver no longer tells the third party screensaver to quit! My rough guess is that this is linked to the way they implemented the transition with the new built in aerial videos they added that "slows" down on your desktop (on practice, it's not the screensaver that becomes the desktop, but 2 separate process/video players that gets synced up!).
Anyway, it's been a mess for third party developers for a while (I make one called Aerial). Our best workaround is to listen for a macOS event that tells us the screensaver will exit, and time our way to forcing an exit (literally, we call exit() which we shouldn't do, but that's the only workaround that works-ish). It works maybe 99% of the time. But sometimes legacyScreenSaver still craps out on its own.
Killing it manually will fix things (you will get a black screen + some CPU usage until you do, that can get bad depending on the screensaver) too.
I (and others) reported that bug multiple times but it's been 1 year+ and nothing. It's a mess.
Good times.
I've tried Stats over the years as the project has evolved and I keep coming back to iStat Menus. Stats feels very inspired by iStats Menus's design as well. The one thing I appreciate about Stats though is support more SMC sensor values.
Edit: I just see the battery widget not any of the other ones. This is a confusing onboarding experience.
Edit2: ah, they were all hidden because of Macs crap UX on menubar space. No indication there are more menu item. What a poor design decision Mac.
Back in the day I paid for https://www.macbartender.com/ to get these features.
defaults -currentHost write -globalDomain NSStatusItemSpacing -int 8
defaults -currentHost write -globalDomain NSStatusItemSelectionPadding -int 8
Changed your mind? No cap, just undo it with these: defaults -currentHost delete -globalDomain NSStatusItemSpacing
defaults -currentHost delete -globalDomain NSStatusItemSelectionPadding
Then, log out and back in. Boom, you’re golden.https://www.reddit.com/r/ProgrammerHumor/comments/1963h4k/cs...
I have a system prompt for haiku to convert messages to genz slang. I use it to confuse friends with it sometimes and we have a laugh. I had the instructions somewhere stored and just wanted to rewrite them before posting them here because I am paranoid and did not remember if i posted them verbatim in another place with another username.
I know this is not really the place for this sort of thing, but if some people smiled a bit I am good with that
In this case, the term "bet": I remembered hearing that for the first time in the late 1980s in a song by Fresh Prince (Will Smith): "... bet, well let's go then..." (As We Go, 1988)
Also I am genz and calling someone old is rude
On my previous laptop, I set it up once and then forgot about it. No need to update, no fuss, it just worked.
System Settings > Control Center > Weather
I am still on 15.1.1 too as I have been waiting for a 15.2.1 for bug fixes, but they released 15.3 instead.
thanks. now i'm wondering why it hasn't been pestering me to upgrade. i just went and looked, and now it sees the upgrade possible. i must have told it later and promptly forgot about it
I've heard about running them directly from SMB but have never been the kind of person to try out such a stunt https://learn.microsoft.com/en-us/sysinternals/#sysinternals...
The config ui is unbelievably slow with a very early windows 7 aesthetic. But I've seen that screen maybe three times in as many years. It's fine, I guess.
The main.taskbar widget seems perfectly cromulent though. No noticeable impact on system resources, and the updating feels plenty snappy. I'm happy with paying a few bucks for this widget.
Seems like with AI + the faux Apple claims of running (any meaningful) AI, people are just not using it.
Like there has been a near total drop-off of mention since ~May 2024.
Have been using this for about a year now without issue.
What does this have that menumeters hasn't?
Ha! You can rip my Intel Mac from my cold, dead hands.
Hey iStat users, what makes the paid tool worth it for you?
[1] https://extensions.gnome.org/extension/3010/system-monitor-n...
[2] https://github.com/mgalgs/gnome-shell-system-monitor-next-ap...
https://github.com/corecoding/Vitals/issues
Vitals is a GNOME Shell extension for displaying your computer's temperature, voltage, fan speed, memory usage, processor load, system resources, network speed and storage stats in your GNOME Shell's top menu bar. This is a one stop shop to monitor all of your vital sensors. Vitals uses asynchronous polling to provide a smooth user experience.