• 0 Posts
  • 1.11K Comments
Joined 1 year ago
cake
Cake day: July 16th, 2023

help-circle


  • Newer kernel matters and can actually make the distro more new user friendly for sure.

    Newer packages as well which prevents you from having to find newer versions in PPAs and other places. In my view, this makes a distro less stable and harder to maintain.

    In fact, I think Arch can be more stable than Ubuntu precisely because Arch users hardly ever have to look beyond the repos. I think Arch users really less on Flatpak for the same reason. In theory the AUR is no different than a PPA but it causes way fewer problems in practice ( especially conflicts ). There is something about APT as well that handles conflicts by removing stuff ( stuff you may really need ). Pacman and dnf do not seem to do that.



  • 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.



  • 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.




  • LeFantome@programming.devtoLinux@lemmy.mlLinux middle ground?
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    3 days ago

    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.





  • 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 ).