Mine isn't even that reduced and after 4 years I still miss instant, layerless access to the F keys.

We already have freetube

Definitive roadmap (for the lazy people edition):

1. Get some computing device
2. Install dokploy
3. Run whatever containers in it with a couple of clicks

Do you have a step by step guide? Cause I can't make it work.

I really wish this would work on KDE at some point. It looks super neat and I was indeed doing something like this on x11 before.

There are hdmi/dp dummy plugs of course.

Just fyi

a storage controller on an USB stick also has programmed "Gb" for addressing the flash storage. For example if you want to remove one of the flash chips, you could be asking how to reprogram the controller to use only half of it's initial capacity. Thats what I was confused about.

But you actually meant Gb/s.

What kind of controller and what kind of Gb are you talking about?

Storage controller for USB sticks?

Or gaming controller with an advertised Gb/s USB bandwidth?

I wish I knew how tails does it so that I could make my Linux do it as well.

Edit: oh, it's just spoofing the user agent af far as I can see. That doesn't hide it being linux at all.

Depends on their specific needs, so they should probably jump into some Linux community and ask for themselves.

My anecdotal evidence includes vastly different experiences.

I have a friend who hates Linux desktop and exclusively uses it for running dev related stuff via WSL.

Another who uses Linux desktop primarely, but dualboots Windows for certain games.

And I am on Linux single boot and rarely use KVM (without GPU) for running my CNC or other software.

Minisforum V3 is 12” and less than 1kg.

But it is not quite a laptop, expensive and very powerful - not sure if that suits you.

Linux wise, most of the stuff works (sleep, power profiles, volume buttons, fingerprint reader, face recognition, pen, touchscreen). Things that don't work are automatic rotate/accelerometer.

I'm super happy with it, running arch, doing development and using VMs.

Let me be more concrete then. What I am used to is the following:

• Open the relevant Jetbrains IDE
• Click on new project
• Find the correct template (e.g. Spring Boot Web Starter) and follow the wizard. (Alternatively the steps before can be replaced with cloning a repo and opening it with my IDE)
• I can click "Play" to start the app
• I can click "Debug" to debug the app
• Bonus: when doing Android or Web development, I can create the GUI by drag&dropping building blocks into a preview (contrary to manually typing out textfiles that describe the layout)

Every step is a button click or a entry field in a dialog. These steps also work on every major distro. And I wish for a similar experience when developing KDE Plasma.

For completeness, I will try to do the same dev things and list the steps for KDE Plasma development later (in about 8h).

Very nice.

I'm very excited, because in the past I have bounced off KDE development. Coming from a java and web background, the tooling and dev environment was just mindboggling.

You can either decide by what is currently in demand in the industry and then pick a project that you can exercise that language with or you can think of a project you'd like to do and then go by what the best language is for a given project.

In the end, languages are just like different wrenches. First you have to learn how to use a wrench, size or features don't matter much at this point (unless you already know that you want to become an expert with one particular wrench).

I think starting a new project is way easier than contributing to an existing one.

Best advice I have:

https://www.youtube.com/watch?v=0FPO4fm4nxc

Keep at it. Do actual projects. Actually use the tools for a while. It will eventually make sense.

Why do so many external entities care so much about constantly trying to reduce my privacy?

If they would not have started it, I wouldn't have started to care.

Install literally every package from the repo, then you can experience breaking OS every day.

The most annoying ones for me personally, in no particular order:

1. https://bugs.kde.org/show_bug.cgi?id=491230
2. https://bugs.kde.org/show_bug.cgi?id=483503
3. https://bugs.kde.org/show_bug.cgi?id=488060
4. https://bugs.kde.org/show_bug.cgi?id=482953
5. https://bugs.kde.org/show_bug.cgi?id=490055
6. https://bugs.kde.org/show_bug.cgi?id=477951
7. https://bugs.kde.org/show_bug.cgi?id=479391
8. https://bugs.kde.org/show_bug.cgi?id=482953

tldr: nothing works - sorry for being bitter

I have reported and/or commented on existing issues when plasma 6.0.0 rolled out on arch and there has been no work on them as far as I can see.

I even asked in the matrix dev rooms.

They were not even triaged. So some describe the same issue multiple times. Check the ones which had activity in 2024:

https://bugs.kde.org/buglist.cgi?component=rules&order=changeddate DESC%2Cbug_status%2Cpriority%2Cassigned_to%2Cbug_id&product=kwin&query_format=advanced&resolution=---

I just hope they fix window rules

As far as I can see it is just Debian with LXDE, firefox ESR and some other packages preinstalled.

If they respect the license, you as a user can ask for the source code by e-mail.

But from my point of view, you can just install plain old Debian and all the same software and get a long term proven OS that will not randomly disappear and a huge userbase for support questions.