@discuss.tchncs.de
In general, I would like to note that a rolling distribution does not necessarily always have to offer the latest packages as soon as possible. Rolling primarily only means that updates are offered gradually via the same package sources.
But this is just a general remark. :-)
As always, such statistics should be treated with caution.
What methodology is used to calculate Statcounter Global Stats?
Statcounter is a web analytics service. Our tracking code is installed on more than 1.5 million sites globally.
It is assumed that there are more than one billion websites worldwide. It is therefore not exactly unlikely that a Linux user will not access any of these 1.5 million websites.
Furthermore, it is quite common for Linux users to use tools such as Pi-Hole that simply block such statistics scripts. This means that these users would not be counted even if they accessed one of these 1.5 million websites. For my part, I also use computers with Linux that I don't use to access websites. Some of these computers don't even have access to the Internet. They are therefore not counted either.
Finally, let's come to the most important point. Percentage values say not much if you don't know the actual number of users behind them. Let's assume, for example, that 3.5 per cent Linux users were detected in December and only 3 per cent in January. However, if the total number of users was higher in January, it is therefore possible that more users were detected in January.
when it’s the main reason why so many people use Arch Linux?
AUR is one reason why I use Arch. But not the reason. Besides AUR, Arch has many other advantages from my point of view. Like for example the wiki that also users of other distributions use. Or the many vanilla packages. Or that you can easily create your own packages through the PKGBUILD files. Or that, based on my own experience, Arch is quite problem-free to use despite the current packages.
One reason why other distributions don't have something like AUR could be that AUR is not an official offering, so no verification is done in advance either. Thus, it has happened at least once that someone has manipulated PKGBUILD files in bad faith (https://lists.archlinux.org/...). The Wiki does not warn against the use for nothing.
However, it is much easier for the user to check the files in the AUR in advance than it is, for example, with ready-made packages in an unofficial PPA.
With https://build.opensuse.org and https://mpr.makedeb.org there are also at least two offers that are somewhat similar to AUR.
However, one should first read through https://wiki.archlinux.org/... and consider whether it is really worth the risk.
For my part, I will simply wait until Plasma 6 arrives in the official package sources.
You can follow the submissions via an RSS feed.
For example, if you use the link Https://lemm.ee/feeds/u/Corr.xml?sort=New, all your previous posts will be displayed.
Instead of lemm.ee you need to specify the instance where the user in question is registered. And instead of Corr you have to enter the username. For example https://discuss.tchncs.de/feeds/u/fryboyter.xml?sort=New. That would be in this case my contributions.
Here are the things I’ve gathered are non-cosmetic:
Based on https://kde.org/de/announcements/megarelease/6/, I think that many more things are not just purely cosmetic changes.
I must be missing something.
I would say you simply have the wrong expectation that with a so-called mega release a lot of big changes have to happen that the user has to notice immediately. However, many of the changes in Plasma 6 are probably not huge. But many smaller changes are also many changes.
And as others have already written, the changeover to QT 6 was probably not an easy task.
I also see Plasma 6.0 as a basis for things that are planned in Plasma 6.1 or later versions, for example, and are therefore not yet visible to the user. Articles on the development of Plasma are regularly published at https://pointieststick.com, which provide a more detailed insight into the development process.
Nowadays, servers that are not connected to a monitor, keyboard or mouse are often referred to as headless. Regardless of whether they have a graphical user interface (which can be used with tools such as Guacamole, for example).
I'm not trying to say that this is correct, but simply to point out that the term "headless" is now often interpreted differently.
Therefore, from my point of view, the disadvantages outweigh the advantages. Therefore, I do not have such a tool permanently installed, neither under Linux nor under Windows. However, every 6 months I scan my Windows installation with a USB-bootable virus scanner. No actually harmful programme has been found for years.
In my opinion, the following things are much more important than any security software.
Especially the last point is a problem for many users. I can't tell you how many times I've witnessed someone receiving an alleged invoice from mobile provider A by email and opening it, even though they had a contract with provider B.
All this should be much more useful than doing anything on Reddit.
When it comes to SBC, the choice has always been a Raspberry Pi. Why? A Raspberry Pi may not have the best performance. But in return you can be sure that it will still be supported after a kernel update. And that is exactly the problem with many alternatives. They support a certain, mostly old, kernel. And that's it. Furthermore, the community around the Raspberry Pi is simply huge.
It's more than just a simple tool with which you can tweak audio. Some features are listed at https://valvesoftware.github.io/steam-audio/. The tool is mainly intended for the development of games (also under Linux).
And yes, it's basically just about the fact that Steam Audio is now completely open source.
To go x86_64-only was a mistake for Arch.
Therefore, from my point of view, they have done everything right. Just like other, non-Arch based distributions, which are also now only offered for x86_64.
Distros like Fedora or Debian, or openSUSE have universal building systems and infrastructure for building packages for different architectures.
Right. And all have more collaborators and more money. For example, according to https://nm.debian.org/members/, nearly 1000 people participate in Debian.
Arch's core development team, on the other hand, consists of just 28 people without being paid for it. In addition, there are some "trusted users" (a bit more than 60 iirc) and some people responsible for support (wiki and IRC moderators etc.).
Arch just creates unnecessary fragmentation for the GNU/Linux landscape: software need to be packaged for the distro and for the same time PKGBUILDs cannot be reused in general for anything to go full Arch Linux.
Fragementation has always existed. Before Arch I had used Mandrake / Mandriva. With it I often could not use Redhat packages although they technically used the same format (RPM).
By the way, in the case of Arch or distributions based on it, you can in many cases use PKBUILD files for other platforms as well. Often it is sufficient to modify the line arch=('x86_64') accordingly. I have done this in some cases where a software for Alarm (Arch Linux ARM) was not officially offered. I simply took the PKBGUILD file from Arch Linux and changed it accordingly. And yes, this does not always work.
according to StatCounter's data
Our tracking code is installed on more than 1.5 million sites globally.
Such statistics are always to be taken with a grain of salt.
There are more than 1.5 billion websites worldwide. Statcounter therefore covers only a small fraction of them. So chances are good that you as a Linux user do not use any of these 1.5 million websites that Statcounter uses to create their statistics.
Furthermore, I suspect that many Linux users use tools like uBlock Origin or Pi-Hole, so that the things that are used to track users are blocked.
Apart from that, I have several Linux installations with which I never access a website. Sometimes they have no direct connection to the Internet. Thus, they are also not recorded.
But now to the most important. 3 percent of what? Percentage numbers don't tell anything if you don't know the number of users behind them. Let's assume that there were 2.8 percent Linux users in May. In June, only 2.6 percent. Nevertheless, it is possible that there were more actual users in June if the total number of all users increased accordingly.
Ran sudo pacman -Syu; sudo pacman -Syy like I do every few days
Syy forces the package database to be updated even if no updates are available.
In my opinion, this makes no sense, especially after you have already run pacman -Syu before. Basically, you only generate additional, unnecessary traffic on the mirror you are using. Pacman -Syu is normally always sufficient.
The journal was really long so I moved past it
The display of the systemd journal can be easily filtered. For example, with journalctl -p err -b -1, all entries of the last boot process that are marked as error, critical, alarm or emergency are displayed.
Has anyone else ran into this issue when updating?
Not me. But other users do. Some of them also use a distribution other than Arch (or a distribution based on it). When I look at the problems, the current kernel is probably quite a minefield as far as problems are concerned.
Any advice for preventing future crashes or issues like this so I don’t fear updating?
As other users have already recommended, you could additionally install the LTS kernel. And if you use BTRFS as a file system, create snapshots before an update (https://wiki.archlinux.org/...).
And it should be obvious that important data should be backed up on a regular basis.
I have several virtual machines here with Arch that I often don't use for months. And when I do use them, I proceed as I do with every update. So before an update, I check if something has been published at https://archlinux.org/news/ that affects the installation in question. This is done automatically with the help of the tool informant. If something has been published that affects my installations, I take that into account. Otherwise I run pacman -Syu as usual. And that's it.
Is the current SystemD rant derived from years ago (while they’ve improved a lot)?
In my experience, the same arguments against systemd (not systemD) are still used. No matter how often they have been disproved or whether the problem has been fixed in the meantime. With many users I am sure that it is only about making the project systemd bad.
Should Linux community rant about bigger problems such as Wayland related things not ready for current needs of normies?
I would prefer it if there were no rants at all. No matter what the topic. Because that doesn't help in any way. It would make more sense to invest the energy in the projects in question or in alternative projects to improve them.
In my opinion, users who already use vim are not the primary target audience of Helix. I see the target group more among users who want to switch from a "normal" editor to a modal editor. The selection → action model and the easier shortcuts probably make the switch easier for many. I personally don't like vim at all because of the handling (purely subjective view). Helix will definitely not be my default editor but I get along much better with it than with vim or neovim.
On Arch Linux, Plasma 6.0.1 was released a few minutes ago in the testing package sources.
I am curious if this version will reach the official repositories or if there are still reasons to delay an official release.
Edit: That went faster than expected. Plasma 6.0.1 has been moved from Testing to Extra.
Based on https://docs.atuin.sh/..., "fuzzy search" is used as standard.
thanks for using Leebra!
go to feed...