Or even better, btop

Secret sauce: it’s much easier to get an employer on board with buying you a Thinkpad as part of a bulk order than it is to get them to spring for any of these more obscure models as a one-off.

I’ve used vim with a smattering of essential plugins for years to do this, and only this year moved to Neovim for the same.

It’s not Open Source, but I’ve also taken a hefty liking to Obsidian’s canvas mode. Likewise, I share a small selection of lists with my other half via Google Keep.

Only reason I’m holding on to my Windows partition at this point is for rare scenarios like needing to reprogram my VKB stick, which only has a Windows executable. Other than that, I’ve not fired it up in months. And I’m a pretty rabid gamer.

It’s taken a long damn time to get here.

Syslog (rsyslod) is usually the standard answer for the average sysadmin, but it depends a lot on your needs. A lot of newer loggers output as pure JSON, which offer benefits to readability and more approachable search logic/filters/queries (I’m so tired of regex).

When you start venturing down the road of finding the right way to store and forward the output of logging drivers from Docker containers, as one example, rsyslod starts to feel dated.

The easy answers if you want to throw money at the problem are solutions like Splunk, Datadog, or New Relic. If you don’t want to (and most people wouldn’t), then alternatives certainly exist, but some of them are just as heavy on system resources. Greylog has relative feature parity with Splunk Enterprise, but consumes just as much compute and storage if not more, and I found it to be a much larger pain in the butt to administer and keep running.

The likeliest answer to this problem is Grafana Loki, just based on what I’ve read of its capabilities, but I haven’t had a chance to circle back and test it out. Someone here who has might be able to weigh in and speak to its strengths/weaknesses.

This has been on my radar for a while, and I keep putting it off. How are you liking it?

Grafana’s Loki sounded incredibly useful and performant, with the added benefit of reducing storage requirements significantly under some situations.

Minimal issues here. Set up Arch, install nVidia, add build hooks before next kernel update, carry on.

Arch, i3, GTX 3080 12GB, and no issues. I’m holding off migrating to Wayland for the sake of full compatibility with all screen-sharing solutions.

I’ve never really experienced any issues pairing Linux with nVidia, so I have trouble personally relating to all the hate they catch. There have been a few times where the kernel and the nVidia driver were mismatched, which caused issues trying to start up Xorg, but that’s easily solvable.

One of the main reasons my wife hasn’t taken the Linux plunge is Photoshop support and a lack of feature-complete alternatives with sane UI design choices. We would gladly pay for a Linux version of Photoshop at this point.

It"s dawning on me now as I write this that Proton could be the secret sauce that slays this monster. Has anyone tried adding Photoshop as a non-Steam app to the Steam client, lately?

I distro hopped a lot in the 2006-2011 era, and eventually settled on Arch. I like the initial simplicity, the wiki was and still is the best resource to this day, and anything I needed from the kitchen sink was accessible via the AUR. I’ve ended up using it on my workstations, work laptops, and personal machines ever since.