When HDDs used to be the norm, that would raise an obvious audiovisual signal that something isn't right. Unfortunately with almost everyone using SSDs these days, and the loss of activity indicators[1] on a lot of machines, it would be barely noticeable.
[1] I suspect that it's also in the interests of "officially sanctioned" malware to hide its presence.
This is one of the (several) modern trends of computing that I dislike severely. There are lights for all kinds of nonsense but actually useful information, like Wifi status, disk activity, and even POWER ON/OFF are removed for some misdirected sense of minimalism or style.
my issue with them is i don't need my house lit up like a christmas tree at 2am in the morning when everything is "off", i've never found having a flashing light a great way of troubleshooting when there's a lot better tools to measure disk or network usage anyway.
disk activity lights can be pretty keen when you're trying to figure out whether or not the system is entirely halted or just slogging through a heavy workload.
the kind of time when a tool that is good at measuring such things won't ever even attempt to load.
I also enjoyed the sound that the HDD made when something was happening. So even if the computer froze, the sound gave me a bit of hope. If there was no sound from the HDD and the computer froze, I just restarted the computer, abandon all hope.
I understand this; on the other hand I pretty much want a totally quiet computer, so I don't really miss the sound. A frantically blinking LED is useful, and desirable if not too bright.
Yes. Related, I really do not need my headset to blink in the eyes of the person I sleep next to this hard. Why does it blinks seven times every time I use any command like volume up and down?
So thick black tape it is. (Can't do anything about this voice screaming the headset's status though.)
LEDs that are too bright on my laptops get similar treatment. I try to leave them a bit visible, enough to see in a dark room whether they are on, but the laptop not sending light including when it's suspended is more important.
> when there's a lot better tools to measure disk or network usage anyway.
Only if your system is working fine.
Only if you are okay with switching the context.
'Flashing lights' aren't the best troubleshooting tools, but they are OOB and works constantly. Frantically flashing HDD LED would say you about why the system froze for a couple of seconds way sooner when you oculd launch some performance monitor things.
monitoring the presence of disk and network activity in general was a lot more useful when computers only did things when you told them to and only made connections to remote hosts when you explicitly requested it. Never knowing what your devices are doing or who/what they are communicating with without having to launch a full scale investigation was nice.
I like my Lenovo X200 with all its glorious light indicators, some of which one can even see when the lid is closed. I wish modern laptops would have those again.
We didn't have rainmeter back when hard drives were used as boot drives. I have a pretty large set of windows performance monitor and HWInfo readouts running on all of my windows machines with modified versions of the simpleperfmeter and now rainformer skins.
No need to have uncontrolled diagnostic feedback when you can make it be exactly what you want in a much more rich/dense format. Clicking doesn't tell you much compared to time traces of read and write activity, drive temperature, and page fault rate.
For a modern OS a some inductor LED for drive activity would just be constantly flashing at different rates. Something is always writing to a log somewhere, just on the OS itself.
To actually be useful more information would need to be carried: different rates (by colour, brightness, or a simple bar of variable length), an indicator per drive if multiple, ...
I've done that in the past, back when I was running Linux on very slow & apparently somewhat fragile solid state devices on a netbook, and when trying to keep traditional drives as quiet as possible in a desktop pretending to be a server that was on all hours, but for the most part I leave logging on and not overly buffered these days. SSDs are quiet and reliable¹ ATM.
--
[1] though for anything I care about I still RAID1² everything
[2] with devices from different sources, to reduce the chance of both dying at the same time (or the second dying before the first is replaced and the mirror rebuilt)
This is not true at all. I'm running Linux and I am alerted by the HDD LED when it lights up and then I realize that I left the BitTorrent client running or something like that. But in regular browsing and using the device, the LED is mostly off, blinking once every 10 seconds or so.
I find that SSDs have a terrible failure mode too. Everyone thinks they are "fast" so they do all sorts of file operations that would have previously been considered too slow. However, consumer SSDs are only "fast" until they run out of DRAM buffer or SLC cache. Then they slow WAY down, like slower IOPS than my spinning rust disk. That means your busy machine goes from perfectly fine to nearly locked up, because even the OS now thinks file operations are "cheap" enough to block on and rely on in all sorts of hot paths.
Once that buffer or cache runs out, all those mostly extraneous IOPS just pile up, and the SSD will basically never catch up, because the technology fundamentally cannot catch up to a sustained load like that, but the load is sustained because all the software was designed with "SSDs are fast and lots of small writes will be fast" so they just keep growing the queue.
Previously most of the OS would be in memory and only page out if absolutely needed. It feels like modern windows is perfectly willing to page itself out because "SSDs are fast" and have random, pointless file ops everywhere. So if your SSD gets bogged down, now your operating system basically dies too, so good luck killing whatever app(s) are causing the problem
My new-ish Dell XPS laptop actually does make noises; I think from the SSD due to [0]. It can indeed be quite useful for figuring out when something’s not quite right.
Also, it checks the entire system for JARs and injects it’s stage0 bootstrap!, that includes maven and gradle caches. Reading this part sent a slight cold shiver down my back. Am infected mod dev could become a new spreader
God im sick of "everything you run runs under your full rights". It doesn't reflect reality, it may have in the 80's. Now it's impossible to know what is being executed so it shouldn't make sense that it has free reigns. IT SHOULD ASK FOR EVERY FKIN RESOURCE IT WANTS TO ACCESS
When HDDs used to be the norm, that would raise an obvious audiovisual signal that something isn't right. Unfortunately with almost everyone using SSDs these days, and the loss of activity indicators[1] on a lot of machines, it would be barely noticeable.
[1] I suspect that it's also in the interests of "officially sanctioned" malware to hide its presence.