Somewhat recently I caused a failed kernel update by accident:

Ran system update in tmux session (local session on desktop). But problem was that tmux itself got also updated, which crashed the tmux session and as a result crashed the kernel update. Only realized it upon the following reboot (which no longer worked).

Your described solution re “live ISO, chroot, run system update once more, reboot” was also what got me out of that situation. So certainly something worth learning for “general troubleshooting” purposes re system updates.

Have a ZOWIE EC2 for quite a while now:

• gaming mouse, 5 buttons
• USB compliant
• no special vendor drivers needed to use all mouse features (has buttons on bottom side for settings)

Works well on all OS.

I went through setting up netdata for a sraging (in progression for a production) server not too long ago.

The netdata docs were quite clear on that fact that the default configuration is a “showcase configuration”, not a “production ready configuration”!

It’s really meant to show off all features to new users, who then can pick what they actually want. Great thing about disabling unimportant things is that one gets a lot more “history” for the same amount of storage need, cause there are simply less data points to track. Similar with adjusting the rate which it takes data points. For instance, going down from default 1s internal to 2s basically halfs the CPU requirement, even more so if one also disables the machine learning stuff.

The one thing I have to admit though is that “optimizing netdata configs” really isn’t that quickly done. There’s just a lot of stuff it provides, lots of docs reading to be done until one roughly gets a feel for configuring it (i.e. knowing what all could be disabled and how much of a difference it actually makes). Of course, there’s always a potential need for optimizations later on when one sees the actual server load in prod.

Same here! Been using manjaro for more than 5 years by now on all my dev machines and I really like not being overrun by updates.

Once you form the habit of checking latest “stable update” forum thread (the eqivalent of checking the arch frontpage before an upgrade) and check for potential “manual interventions” (if any), then it gives you suprisingly good stability. But it’s still rolling release and “pretty current”.

And stability simply becomes more of a factor once your metaphorical “plate” becomes choke full and the last thing you want from your underlying OS is to act up on its own due to an update.

IMO (neo)VIM is great for writing text as well, when all you need is markdown level formatting. Personally I use vimwiki a lot (many years by now).

Just looked it up a bit: https://microsoft.github.io/monaco-editor/

AFAIU, monaco is just about the editor part. So if an electron application doesn’t need an editor, this won’t really help to improve performance.

Having gone through learning and developing with electron myself, this (and the referenced links) was a very helpful resource: https://www.electronjs.org/docs/latest/tutorial/performance

In essence: “measure, measure, measure”.

Then optimize what actually needs optimizing. There’s no easy, generic answer on how to get a given electron app to “appear performant”. I say “appear”, because even vscode leverages various strategies to appear more performant than it might actually be in certain scenarios. I’m not saying this to bash vscode, but because techniques like “lazy loading” are simply a tool in the toolbox called “performance tuning”.

BTW: Not even using C++ will guarantee a performant application in the end, if the application topic itself is complex enough (e.g. video editors, DAWs, etc.) and one doesn’t pay attention to performance during development.

All it takes is to let a bunch of somewhat CPU intensive procedures pile up in an application and at some point it will feel sluggish in certain scenarios. Only way out of that is to measure where the actual bottlenecks are and then think about how one could get away with doing less (or doing less while a bunch of other things are going on and then do it when there’s more of an “idle” time), then make resp. changes to the codebase.

Yeah, that browser zoom. And I too used / use Firefox. I’m not saying these kind of sites are common, but nevertheless I’ve encountered them occasionally. Back then, the most pragmatic workaround was to use desktop zooming of Xfce.

My intention on the previous comment was simply to give some examples of desktop zooming that go beyond the typical accessibility viewpoint (e.g. vision impairment).

That’s why regular backups are advisable.

Yeah, AFAIR, the issue of “windows messing up grub” could happen when it’s installed on the same disk (e.g. on a laptop with one disk). Something about it overwriting the “MBR sector”. At least that was a problem back before UEFI.

I too have been dual booting Windows 10 and Linux for many years now, each having their own physical disk, Linux one always being first in boot order. Not once did a Windows 10 update mess up grub for me with this setup.

Not the same as “on demand zooming”, which let’s one stick with a high, native resolution, but zoom in when required (e.g. websites with small text that can’t be zoomed via browser’s font size increase; e.g. referencing some UI stuff during UI design, without having to take a screenshot and pasting + zooming it in e.g. GIMP).

You didn’t mention how big those volumes are and how frequently the data changes.

Assuming it’s not that much data:

• use tar to archive each volume first, while using proper options to preserve permissions and whatever else is important for your usecase
• use restic to backup those archives
• use a proper pruning strategy to not let your backups get too big:
  • I’m not that familiar with restic, but maybe you can backup those archives separately and apply a more aggressive pruning strategy just for them
  • simply might be needed, cause deduplication (AFAIK) might not be that great with backing up archives
  • but maybe if the volume data and the resulting archive doesn’t change that often, deduplication would be sufficient even with a not so aggressive pruning strategy

Honestly, if all you’ve ever experienced in regards to terminals is windows CMD, then you really haven’t seen much. I mean that possitively. Actually, it will give you a far worse impression on what using a Linux / Unix terminal can be like (speaking as someone who spent what feel’s like years in terminals, of which the least amount in windows CMD).

I suggest to simply play around with a Linux terminal (e.g. install VirtualBox,.then use it to install e.g. Ubuntu, then follow some simple random “Linux terminal beginner tutorial” you can find online).

On top of that, 20 kHz is quite the theoretical upper limit.

Most people, be it due to aging (affects all of us) or due to behaviour (some way more than others), can’t hear that far up anyway. Most people would be suprised how high up even e.g. 17 kHz is. Sounds a lot closer to very high pitched “hissing” or “shimmer”, not something that’s considered “tonal”.

So yeah, saying “oh no, let me have my precious 30 kHz” really is questionable.

At least when it comes to listening to finished music files. The validity of higher sampling frequencies during various stages in the audio production process is a different, way less questionable topic,

That’s one of the reasons why the more modern fd is a nice alternative: it accepts command line args as you’d expect.

I’ve been using Manjaro (XFCE edition) as my daily driver, both on a laptop and a desktop system for more than 6 years now. I’ve tried many others beforehand: Ubuntu and its variations, Arch, Fedora, Tumbleweed, …

But Manjaro was what made me stop hopping around. While it’s true that it has some pitfalls (e.g. cert issues, AUR incompatibility at times), to this day it’s working well enough for me that I don’t feel like switching away.

I’m not just browsing web on it either. Software engineering, music production, image and video processing, etc.

Then again, I don’t consider myself a beginner at this point and can troubleshoot a fair amount of issues now that I simply couldn’t when I started using Linux more than a decade ago.

I also try to:

• not overdo the amount of AUR stuff I use
• read the official forum post BEFORE whenever I run a system update

I also always appreciated the fact that I could get away with not doing a system update for like six weeks and then do a big one (as mentioned, in combination with reading their update announcement). That’s always something that didn’t quite work for me on Arch in the past (then again, I still was a beginner back then, so most “reinstall to solve this problem” situations back then were on me).

What if Manjaro really would get worse enough so I’d want to switch? I guess EndeavourOS would be an option, because it’s very close to Arch, but at the same time, it seemingly offers a graphical installer that hopefully will set itself up properly on a laptop. Then again, I haven’t installed Arch in quite a while now. Maybe the install experience has gotten much nicer.