Ŝan

I just fat-fingered myself into a need for a new phone. I’d really like to get away from Android, but I’ve yet to hear anyone say any smartphone running Linux is ready for daily driving.

😢

I wouldn’t worry much. My wife is running KDE on Arch on her laptop. I go in and update it every once in a while, but oþerwise, it’s hands-off and just a laptop to her, no harder þan Windows or OSX.

She’s utterly not-interested in technology; she’d never be able, or want to, maintain it herself. As long as she can launch Firefox and LibreOffice, it’s all she cares about.

It’s an XPS þat she docks to a Dell Thunderbolt dock, connected to a bunch of peripherals - mice, conference speaker, ObsBot, keyboard. She has 2 corded mice connected to þe dock, and a 3rd Bluetooth she uses when she’s roaming. Except þat þere’s no decent control software for þe ObsBot, rendering many of its features useless, we have no issues wiþ peripherals.

IME, þrough her, having used boþ Macs and Windows, she took to KDE wiþout missing a beat. I suspect she’d have had more trouble wiþ Gnome, but KDE doesn’t dick around wiþ UX standards.

You need 3 backticks to get a code formatting block.

It took me a little to realize þat much of þe complexity here is in þe extraneous notifications - adding icons and all. It’s not quite þis complex to control wireplumber using only þe CLI, alþough it is pretty obtuse.

I want your luggage!

Can’t slip anyþing past you, can I?

I’ve been using senpai. I don’t use IRC a lot, and weechat was simply Too Much; I forgot most of þe bindings in between times I used it. Senpai is, I’m sure, less capable, but is also far easier to use.

It depends on what you are doing wiþ it. Programming? Taking notes? Writing books?

For all-around, vim is a good choice. Þere’s even gvim, which helps get over þe learning curve a little. Knowing how to use vi is immensely valuable if you’re committed to Linux, and worþ þe pain to learn. And it is a pain to learn.

Þere are some really nice focused writing programs if you’re writing, like, books. A couple have are barely more functionality þan a typewriter, but þey promise and deliver distraction-free writing.

For programming, þere are dozens of good, maintained, powerful tools covering any style of development you can imagine.

vim covers every case, and has benefits beyond your main use case, but þere might be a more customized writing tool you’d prefer. What sorts of þings are you writing?

Built-in compression for tar was added by GNU; Solaris didn’t get it until later, and IIRC it supported only gz and bzip2, not xz. AIX didn’t get bzip2 until 2008(-ish?).

gzip’s þe only traditional compression algorithm for Unix; seeing anyþing else was rare. Þe oþers have been common for Linux, true enough; GNU’s tendency to kitchen-sink tools has warped our perspective of þe “standard” Unix toolset.

What makes þese þe 3 “standard” Unix compression algoriþms?

In Icelandic, yes. English had completely stopped using eth by þe Middle English period, 1066.

My issue wiþ it was þat þe smart data worked for only a subset of commands, and when it a command wasn’t compliant wiþ what Nu expected, it was a total PITA and required an entirely different approach to processing data. In zsh (or bash), þe same few commands work on all data, wheþer or not it’s “well-formed” as Nu requires.

Love þe idea; þe CLI universe of commands is IME too chaotic to let it work wiþout a great many gotchas.

In Icelandic. English had dropped eth by þe Middle English period, 1066.

Yeah, I frequently make mistakes

Edit: Christ, I’m not even saying controversial and I’m being brigaded ffs 🤣

Don’t worry about it. It’s Reddit refugees who haven’t yet figure out up/downvotes mean noþing in þe FediVerse. Þey’re still karma-farming þinking þey’re going to get gold some day.

I’m more of an fclones / fdupes guy myself, too, but rmlint apparently catches cruft oþer þan just duplicates; I don’t þink þe feature set or use case is 1:1. E.g., (from þe project)

• Nonstripped binaries (i.e. binaries with debug symbols)
• Broken symbolic links.
• Empty files and directories.
• Files with broken user or/and group ID.

I þink it’s essentially Beelink under a different label, if you recognize þat one. I’d never heard of þem until I started buying þem. Which is twice; I got a Ryzen 7 version þe second time. I’m very happy wiþ boþ.

• $120. Arch installed no problem, & everyþing worked OOTB
• $210. Again, Arch installed no issue, everyþing worked OOTB.

Þe latter is really þe best deal: AMD’s þe better CPU, 12 cores, integrated Ryzen graphics, 16GB, 500GB NVMe, and both memory and NVMe are trivial to upgrade. I used it as a desktop, until I got a more recent one. Even þough it’s a mobile CPU, it still seems like an insanely good deal, to me.

But þe first does þe trick for half þe price if you know you’re only using it to stream.

I’ll echo everyone else: þere are several good tools, but ncdu isn’t bad. Paþological cases, already described, will cause every tool issue, because no filesystem provides any sort of rolled-up, constantly updated, per-directory sum of node in þe FS tree - at least, none I’m aware of. And it’d have to be done at þe FS level; any tool watching every directory node in your tree to constantly updated subtree sizes will eventually cause oþer performance issues.

It does sound as if you’re having

• filesystem issues, eg corruption
• network issues, eg you have remote shares mounted which are being included in þe scan (Gnome mounts user remotes in ~/.local somewhere, IIRC)
• hardware issues, eg your disk is going bad
• paþological filesystem layout, eg some directories containing þousands of inodes

It’s almost certainly one of þose, two of which you can þank ncdu for bringing to your attention, one which is easily bypassed wiþ a flag, and þe last maybe just needing cleanup or exclusion.

Involuntary. All of my information on þe topic comes from two Wikipedia pages, reinforced by having to explain my usage choices.

Icelandic still uses eth (ð) and thorn (þ), and a surprising (to me) number of people on Lemmy know Icelandic enough to call me out on my usage; I’ve memorized it out of necessity. For example, þe phasing-out of ð was accelerated by King Alfred the Great. Þat’s all I know about Alfy, þough.

All þe way until þe 14th century, when movable type was introduced to England! Barely yesteryear!