Seriously. Those are EXACTLY the thoughts I had after I was forced to deal with Python after a ton of time writing projects in JS.

I have a dedicated directory with subdirectories for each project and that’s it

The link you provided is one to the concrete post, not the subcategory on the KDE Blogs page.

https://blogs.kde.org/categories/this-week-in-plasma/

This is what I was talking about.

Here is the link:

https://blogs.kde.org/categories/this-week-in-plasma/index.xml

Each blog has an RSS icon right next to its title if you open its home page. This icon is also a link to the feed.

https://blogs.kde.org/

I highly recommend checking out either Fedora KDE Spin or Fedora Kinoite! Both are great choices, especially if you want to leverage the power of Flatpak for app installation, as they both push the user towards it. Additionally, if you ever need to install .deb packages, you can easily do so using Ubuntu in toolbox.

Alternatively, EndeavourOS might also be a good fit for you, providing a user-friendly Arch installation with a rolling release system. You’ll have a modern and flexible environment while still being able to use Flatpak effortlessly. You can also install distrobox there to, again, use apt inside of an Ubuntu system.

Whichever you choose, you can’t go wrong! Happy tinkering and remember that the best way to choose a distro is to try it out.

I’m just using Arch in my toolbox. Can’t run into upgrade troubles if you run a rolling release system

This will only show the idiots over at Western governments that FOSS is hurr durr bad, lets Ruskies evade sanctions

For those who don’t know about Escobar’s axiom: https://www.econjobrumors.com/topic/escobars-axiom-of-choice-1

Did you also set the path to Nvim in settings.json? I had to do so to clear at least one error.

Yup. I set it to /run/host/usr/bin/nvim after exposing system libraries and binaries to VS Codium through KDE’s flatpak permission manager. Prior to that it kept throwing me ENOF errors (or something like that, I don’t remember now).

Unfortunately, that “disconnected” error is either not caused by a race condition for me or I was really unlucky, because at some point I restarted the extension 30 or some times out of frustration and nothing changed 😅

I didn’t have any errors in the init.vim file because I didn’t have any. I added an example init.lua file with contents from here and configured the extension to pull this config file, yet it still says Nvim disconnected each time I restart it. I just gave up and resorted to VSVim

I’ve had issues with that one because I’m using VS Codium flatpak. I’ve exposed system binaries and the extension found the nvim binary, yet it kept erroring out with the message that Nvim was disconnected. VSVim is better in that regard for my case, because it is a stand-alone extension.

Woah, that’s pretty cool! i installed an extension for vim keybindings inside VS Code recently, as I find them very powerful. Unfortunately, I rely on VSC’s plugin ecosystem and thus can’t fully switch over to neovim, but I’ve liked it so far for everything else I do on my system, like writing bash scripts.

I am yet to meet someone who doesn’t use VSCode for web development.

Flatpak does NOT provide sandboxing. It containerises your applications. It’s better for permission management but by no means makes the system invulnerable to malware.

Mine too didnd’t notice. Non-tech savvy people don’t even know what an Internet browser is :)

FOSS Communities:

KDE update day is a happy day

You could write a bash script to automate this process. Pacman supports hooks for updates, so after kernel updates you could set it up to automatically run the script.

Fr, Mac does a much better job at serving their target users than Windows will (likely) ever do

A paper with “It’s Kase, not case, fools!” written on it.