Yeah, put me down for Strawberry too. I used to use Rhythmbox up until mid 2023, I started to get into high res music and I got a tidal subscription, so switched to Strawberry.

Its similar to Clementine because it is a fork of Clementine. https://wiki.strawberrymusicplayer.org/wiki/Differences_from_Clementine

That’s a good tip. My personal choice is celery. Celery has higher water content, and more insoluble fibre than lettuce. And you can eat it pretty quickly too.

The Devs who work on X are doing an amazing job

There aren’t any Devs working on X. That’s the whole problem. Xorg is the most modern and most popular implementation of X, was started in 2004, it no longer has any permanent maintainers, and it hasn’t been updated since 2018. Nobody alive fully understands the whole codebase, it is an unholy mess of multiple forks and multiple versions of many different projects all smushed together. There is no more room for innovation on Xorg because any time anybody fixes a bug or adds a feature, it breaks something totally unrelated. All of the big players who used to pay developers to maintain it, no longer do. Partly because they can’t find anyone willing to do it.

I’m not saying Wayland is the answer to the problem. Building a new display server protocol does not fix the problems with Xorg, and it has its own slew of problems. It really is a “rock and a hard place” situation. You’re a future-hating troglodyte who shuns innovation if you continue to use Xorg, and you’re a risk-taking early-adopter who forfeits functionality for shiny new toys, if you use Wayland.

I started using Trilium in early 2020, with version 0.40.2. Roam had released in 2019 and was growing in popularity quickly, I heard a lot about Roam, it looked cool, so I googled for an open-source self-hosted knowledge base note taking app with similar features to Roam, like notes arranged in a knowledge graph, and a backlinks explorer for each note. The only one that was available then was trilium. Looks like you’re right, the development of trilium was started in 2017, before Roam existed. This is a great interview with the creator, answers a lot of the questions I had. https://console.substack.com/p/console-169

Obsidian didn’t come out until a few months later (and remained under the radar until 2021), all my colleagues and friends use Obsidian now, but I prefer trilium. I had never heard of logseq before I read this thread. Just a quick glance, I see the first 0.1.0 version logseq was in April 2021, just before the first obsidian release.

Trillium was originally created to be an open source replacement for Roam Research. Trilium came out in 2017, and had Roam-like features before Roam even existed. It’s similarities to Obsidian are purely coincidental, probably because Obsidian is designed to be a cross between Roam and Evernote.

Have they fixed the copy+paste problem from the Firefox address bar under Wayland in KDE plasma yet? I’ve been holding off switching to Wayland in my Plasma desktop because of that one Firefox issue.

Edit: Nope still broken: https://bugzilla.mozilla.org/show_bug.cgi?id=1791417

It’s been reported and easily reproduced for more than 3 years: https://bugzilla.mozilla.org/show_bug.cgi?id=1717305

I get what you mean, it is an interesting question to explore.

For me, it think it appeals to my obsessive engineer-brain, I am hooked on chasing efficiency.

Eg, if one tool uses 10MB ram and takes 1second to complete a task, and another tool takes 50MB ram and 5 seconds to complete the same task, then clearly I want to use the more efficient one. The other must be wasting resources, right?

When it comes to real life software and real tasks, it is a lot more complicated than that, there are hundreds of variables to take into account and compare. But if one tool stands out among the others, optimising to achieve the best number (fastest time, lowest power draw, lowest ram use, etc) in each comparable variable, then I absolutely must use that one, it would be irresponsible not to, right?

Throw hardware acceleration into the mix, and it takes the situation to a new level. Why make my poor CPU render the text on the screen 60 times per second, when I can get the GPU to do it? It’s just sitting there doing nothing, and it’s better at the job anyway, and as a bonus you get even lower CPU utilisation and lower ram usage.

However, as I described in my previous post, chasing these numbers can come at the cost of usability. That’s the case with Alacritty, and why I will be switching to wezterm.

Wow, just had a look at the Wezterm GitHub page, read the features and the docs. I think you’re right, it does look like it will replace Alacritty for me.

For anyone else wondering about the differences between Alacritty and wezterm, or still on the fence, read this thread, particularly the comment from wez: https://github.com/wez/wezterm/discussions/1769

I’ve been using Alacritty for the last 4 years, it’s kinda the opposite of this nonsense. It’s written in Rust, it’s super light weight, highly optimised, and uses hardware acceleration to render the terminal. It’s top of the chart for every terminal performance benchmark conceived.

However, that lightness and fastness comes at a cost. There are some basic features they just won’t add because they’re outside the scope of the project. Eg, tabs (“just use a tiling wm and do your own tabs in the wm”) or a scrollbar (“just use a shell with a scrolling screen buffer like Tmux”), or different coloured backgrounds for each opened window (“why would anyone ever want to do that?”).

My holy grail terminal would be something like Alacritty, written in Rust, blisteringly fast and light weight, but with tabs, scrollbar, bookmarks, etc.

I find myself falling back to using Konsole a lot these days, it’s got all the features I want, is fast enough, and already installed on every system I use Plasma on.

Yes please. Sign me up.

Nobara these days. It’s based on Fedora 38.

In my experience, it’s always P@ssw0rd

I used be a computer technician at a small town computer shop around 2008-2011. More than half of our customers were over 60.

Sometimes I needed to take some tech support calls, and sometimes I needed to make house calls to troubleshoot the folks issues.

Literally every support call started with “Why doesn’t the email work?” while the actual problem ranged from ISP issues, and modem faults, PC faults, Windows configuration errors, to dead monitors or a broken mouse. Literally any computer fault could be described as a failure to access their email.

+1 for micro. I install it on every server I administer, and alias it to nano. If you’re a nano user and haven’t tried micro, I highly recommend it. It’s like nano, but built this century, it feels fast and modern.

That’s a good point about it going last in your PATH. Malicious applications running as non-root can still install payloads to ~/.local/bin and hijack common system functions.

Twangathang.

This is /c/memes, not /c/funny or /c/jokes. Memes are the sharing of popular things. Amogus are popular. Memes don’t have to be funny, they’re not jokes.

It puffs out in a cloud, like talc.

Ah, thanks, I didn’t realise it was a fork of Vuze. That explains the big overlap in features.