Video gets higher engagement. If you want your information to be consumed, video is a better bet.
That will not stop every video from having a top comment complaining about it though.
I prefer written content myself. But, as you say, I am happy for content in whatever form I can get it. I did not pay for it. How it is generated and shared is not up to me.
Soon I hope, we will have a bot that transcribes every video. Then that can be the top comment instead of the endless complaining.
I agree with you that using what other “normal” people are using has a lot of value and Ubuntu is still the most popular distro by far ( even I do not like it ).
I think both Fedora and Mint are popular enough as well and a better base than Ubuntu. But that said, Ubuntu is fine.
It has been a couple of years now and the response to these articles is always the same. The person making the comment cannot accept that they produce code with bugs. So the problem has to be that the people being measured in the article must not know what they are doing.
Look at the source of these articles though. We are being asked to believe that the code in Android, Windows, AI frameworks, and databases are all being pumped out by junior devs. It is not that Rust results in fewer bugs than C++ generally, it is that Google engineers have not been properly trained or motivated.
I mean, the denial is Sith level strong in these people.
This is absolute gold.
Exactly what evidence is there that bugs in new code are from new devs? To me, it feels like you have fallen victim to motivated reasoning.
I like the idea of a stable distro as the host OS and Distrobox with Arch and the AUR for applications.
For most of my machines, I do not need the latest kernel or even the latest desktop environment. But it is a pain to have out of date desktop apps and especially dev tools.
I think this strikes a nice balance.
Imagine how much less would get done overall and how many fewer people would participate if we did not let people work on what they wanted to work on.
The only choice left would be to contribute or not and more people would choose not to contribute (probably the choice you have made).
Property tax has nothing to do with unrealized gains. It is an attempt to charge a services tax in an equitable way. It is like putting road taxes in gasoline. Framing it as a crude consumption tax would be more appropriate.
The property tax you pay on your home is a tiny fraction of its value. If we were charging those kinds of tiny percentages to billionaires you would be up in arms.
I do not have to argue abolishing property taxes because they do not introduce the kinds of brain dead distortions that “unrealized gains” taxes would. Even still, there are actually carve outs for them in most countries. Where I live, as an example, seniors can defer property tax until the property is sold ( you know, until the wealth has been realized ). As I said above though, it is really a service tax and so, even when delayed, the amount is based on assessed value every year.
If property tax was a model for your unrealized gains tax it would have these features:
Based on the discussion here, a tax like that is not going to satisfy the mob.
Like I said, tax the rich. Tax the hell out of them. Just don’t do it in such a broken way.
Stop acting like I am defending rich people or arguing against taxes. I have been very clear that I am not. It seems equally clear that you have no rational response to what I am saying which is why you keep pretending that I am arguing for wealth inequality instead of just math. The people hit hardest by bad tax policy are always the middle class. The same would be true of a wrong-headed unrealized gains tax, no matter how much shouting about billionaires was used to make it more popular.
Sure. One of those cons is that you have more packaging problems when you interact with non-Manjaro repos—like the AUR.
I thought there were two units working now ( maybe not everything ). One Lenovo and one Asus if I recall.
EDIT:
ASUS Vivobook S15 & Lenovo Yoga Slim7x
https://www.phoronix.com/news/Linux-6.11-SoC-Platforms
6.11 is released now.
I will just say that SUSE 4.2 was not built off the same base as SUSE 1.0 either. It is not going to be as clear cut as finding a cloned Red Hat source code repository.
SUSE 4.2 was really version 1.0 of the distribution we call OpenSuse today ). It was a reboot. This version was no longer based on Slackware and it was the first version using RPM.
Debian introduced packages in 1995 ( before Debian 1.0 ). RPM did not appear until Red Hat Linux 2.0 in the fall. SUSE 4.2 came out in 1996 and could have used either one.
I was not trying to cause any offence. Mad respect for SUSE. As I hinted, I was simplifying. It is hard to talk about this stuff both accurately and concisely.
SUSE is certainly not a Fedora “fork” as Fedora Core was not even conceived until considerably later. Neither was OpenSUSE really. So you cannot take my first comment too literally.
Let’s remember how early SUSE was in the Linux timeline. Back then, everybody was downloading their software from the same FTP sites. A huge component of what made a Linux distribution different from an FTP repo was the package manager and those came from Red Hat or Debian.
The provenance of SUSE is also a bit complicated as the first versions were explicitly based on Slackware. Starting with 4.2 ( a made up version number meant as a nod to Douglas Adam’s I think ), SUSE became Jurix + RPM. So it is a Jurix fork in that sense. However, I cannot imagine more than a handful of people ever used Jurix. I would be interested to know the numbers. In contrast, in terms of both users and industry awareness, Red Hat was THE Linux distro back then.
Red Hat was certainly an influence on SUSE beyond the source code. Red Hat and SUSE were not just communities or collections of code. Red Hat and SUSE were two of the earliest company backed distros. Both had clear commercial ambition. It is no accident that they both evolved into explicitly “enterprise” subscription products flanked by explicitly community distros. SUSE and Red Hat were more like each other than they were like other Linux players ( especially in the days before Ubuntu ). It is not far wrong I think to think of SUSE as the Red Hat of Europe with Red Hat attracting American infrastructure giants like Oracle and SUSE becoming the platform for big European players like SAP.
SUSE is not a fork in the sense that we are going to find an import into the source code version control system from Red Hat ( other than RPM itself of course ). Again though, we should note that this is not how stuff worked back then ( see comment about FTP sites ).
RPM could have been a purely technical choice for SUSE but, in my view, they had a clear desire to use Red Hat as a template more broadly. That is what I meant by saying SUSE could be seen as a fork while also acknowledging that the statement is not quite fair ( or perhaps more that it is not technically accurate in the strictest sense of what the work fork means even if it instructive as a historical perspective ).
At first I was not very impressed. Then I read that that 4004 does not have any AND, OR, or XOR instructions. Yikes.
If it is “full Linux” then the answer is clearly yes. Not very fast I suppose.
Part of me wants to write off the Russian settlers comment as mindless FUD. Then I remember that Donald Trump was getting cozy with Putin while throwing tariffs at Canada, pulling out of NATO, and getting upset at the press that Trudeau had a better handshake or that Ivanka was checking him out a dinner parties.
You can never say 100% who your friends will be in the future.
I hope both Russia and Trump suffer horrible defeats this winter. Then I can go back to laughing at how stupid the settlers comment is.
Nope. Both pamac and octopi work fine with EndeavourOS. In fact, they work better because the packages are not delayed like they are in Manjaro.
OpenSUSE itself could be seen as a fork of Fedora though it is from long enough ago that perhaps that is not fair.
In the beginning there was Slackware ( well, maybe SLS but it is gone now ). Slackware has no packaging system. Most distros want one. Debian is not really a Slackware fork but it was a response to it.
The first two distributions to bring true package management were Debian and Fedora ( well pre enterprise Red Hat really - before Fedora ). So Fedora and Debian are the classic bases for other distros.
Red Hat created the first, and most successful, “enterprise” distribution so lots of people want to clone that.
Ubuntu was the first distro to really succeed at a “mainstream” desktop experience. Ubuntu is itself a fork of Debian but, because of its early success, there are probably more forks of Ubuntu than anything else.
Arch was the next really successful attempt at a new packaging system and a distro for more technical users ( that still wanted a binary package distribution system ). There are forks of Arch but, as the repos are Arch’s biggest strength, few of them deviate too much beyond the installer and default configuration.
If you are going to create a distro based off another one, it is typical to start with the base distro that is how to the package format of your choice.
There are now other distros with their own packaging systems ( eg. Alpine and Void ) but they have not been around as long.
Importantly I think, OpenSUSE is European base and, for a lot of the history of Linux, it was largely an American phenomenon ( yes, I know it was invented in Finland — how long did Linus stay there? ).
Finally, “forking” is often a little more sophisticated now. In the past, you started with some other distro that you liked and changed a few small things that you didn’t. A lot of that is taken care of with repos and spins these days so you so fewer unique distros start life this way. The exception is maybe init systems.
As an example, you could consider Chimera Linux as a successor to Void but it is not really a fork. It uses a different package manager, userland, and init system for example.
OpenSUSE itself has multiple versions. One of them is likely to be close enough for fans that they do not need to splinter off.
Fair enough. Of course, you know that the exact same graphical installer is also available on EOS right? It is not installed by default but it is in the repos.
The loudest and most negative voices are always consumers, not contributors. They just saw the word “request”.