5 ms·
Debian is like democracy: the worst way of producing an OS, except all the others that have been tried from time to time. BeOS, AmigaOS, Solaris, most other 80
by toyg 6y ago
Debian is like democracy: the worst way of producing an OS, except all the others that have been tried from time to time.
BeOS, AmigaOS, Solaris, most other 80s OSes - they’re effectively dead. Windows and macOS have effectively died once already. The BSDs can stall for years at times. Most Linux distributions (including RedHat) are typically only as good as the fortunes of the commercial (or occasionally public) entity they have behind. In all this, Debian endures, with its slow but inexorable progress, simply because its ideological foundations - not its technical ones - are eminently superior to all the others. Debian contributors don’t do it for the money, so they will be there when money runs out; and they don’t do it for being cool either, so they will be there when OS work is not cool. People will come and go, but the ideal of the “democratic OS” will always be there - hence, Debian will be too.
- smabie 6y agoArch Linux is much superior to Debian, imo.
- rovr138 6y agoCan you at least expand on why that's your opinion?
- nsajko 6y agoUp-to-dateness, no unnecessary distro-specific patching. EDIT: My comment was ambiguous, I didn't mean that there are no Archlinux-specific patches; rather that there's more of an effort with Archlinux to let upstream be upstream.
- soraminazuki 6y agoNo "unnecessary" patching, like seriously? I see so many patches in the Arch packages repo I can't even count them all: https://github.com/archlinux/svntogit-packages/search?q=patch https://github.com/archlinux/svntogit-packages/search?q=patc... https://github.com/archlinux/svntogit-packages/search?q=sed https://github.com/archlinux/svntogit-packages/search?q=sed But putting that aside, all distros need huge amounts of patching to make each package get along with the rest of the system. Without patching, many of them won't even build in the first place.
- sam_lowry_ 6y agoYou have not seen what Debian did to exim, yet.
- Foxboron 6y agoThere are duplicate PKGBUILD files in the repository, so depending on the PKGBUILD and where it is, there might be 3 results for every 1 patch. In many cases there are two hits pr 1 patch.
- deleted 6y ago[deleted]
- idoubtit 6y ago> Up-to-dateness I've read this at least a dozen of times, mostly on HN, and mostly by Archlinux advocates. Many people seem to ignore that Debian testing and Debian unstable are continuously updated (rolling releases). Please stop propagating false claims that taint Archlinux's community reputation.
- jhardy54 6y agoHave you tried running Debian unstable (Sid)? If not, I'd suggest you try it before advocating that it's comparable to running Arch. I think the parent comment was silly, but let's not pretend that Sid is a meant to be used as a daily driver.
- rscho 6y agoTesting is usually around 2 weeks behind unstable, and I use it as my daily driver.
- sam_lowry_ 6y agoExcept the kernel, unlike in Arch.
- jhardy54 6y agoI'm not familiar with any evidence of that, but I'd like to point out that Debian unstable has a higher percentage of outdated packages than Arch. Compare "outdated projects percentage": - https://repology.org/repository/debian_unstable https://repology.org/repository/debian_unstable - https://repology.org/repository/arch https://repology.org/repository/arch
- soraminazuki 6y agoLooking at that data, Debian unstable maintains roughly 3x more packages than Arch official.
- 6y ago
- deleted 6y ago[deleted]
- scaladev 6y agoSuperior documentation and AUR. You can find almost anything in AUR, including all the proprietary crap, and install it all with one command. It's also very easy to write a PKGBUILD and upload it to AUR if you don't find what you need, because the package format is so much simpler. Here are two specific examples which other distros might struggle with: repackaging a tarball to a proper system package which is tracked by the package manager https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=dotnet-core-bin https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=dotne... building a proper system package from the source (with one command! no `configure; make; make install` lunacy): https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=sway-git https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=sway-...
- heavyset_go 6y ago> Superior documentation and AUR. You can find almost anything in AUR, including all the proprietary crap, and install it all with one command. It's also very easy to write a PKGBUILD and upload it to AUR if you don't find what you need, because the package format is so much simpler. I'm a Debian fan, but these two points are very true. Arch documentation is great, and writing PKGBUILD files is easier than packaging for distribution via Apt. I don't even use Arch, but I still release for it because it's easy.
- toyg 6y agoTechnical comparisons are not relevant to my comment. What is Arch’s charter? How are its leaders elected? How are its processes defined?
- edflsafoiewq 6y agoWhat does any of that matter if it doesn't lead to technical superiority? You use an OS for its technical qualities, not for its charter.
- wolco2 6y agoWhen did technical superiority ever matter when it came to an OS? Your living in a world where OS/2 kills windows 3.11 for workgroups. Where Sega's master system outsold Super Nintendo.
- raverbashing 6y agoYes but in neither of those cases the winner got there because of "better democracy" or governance Win 3.11 was more user friendly than OS/2. Not sure about the Sega/Nintendo issue, the Master System was comparable to the NES, the SNES to the Genesis/MegaDrive
- Foxboron 6y agoI'll start off with a hyperbole: We don't have any of that. But that isn't really true. Arch historically has always been a DIY distribution with an equally DIY contribution structure. Our leaders has been BDFLs for close to two decades until the process was formalized and we held our first project leader election this year. https://wiki.archlinux.org/index.php/DeveloperWiki:Project_Leader https://wiki.archlinux.org/index.php/DeveloperWiki:Project_L... https://www.archlinux.org/news/the-future-of-the-arch-linux-project-leader/ https://www.archlinux.org/news/the-future-of-the-arch-linux-... There isn't any RFC process, but some consensus making on the mailing list and who wants to work on stuff. The only other formalized structure is the Trusted Users which are elected in a formalized process. https://aur.archlinux.org/trusted-user/TUbylaws.html https://aur.archlinux.org/trusted-user/TUbylaws.html There is probably a lot of bad things with a less formalized process, but it allows Arch to move fairly rapidly and decide things without a lot of internal politics.
- georgyo 6y agoI'm a huge fan of Arch Linux and would say that it is the best for personal use. However I wouldn't dream of running on a fleet of several. I currently have 6 nspawn containers I run, and it's not as consistent to ensure an update won't break it. Debian is great if you are running many servers. It's slow moving rate is due to care of not breaking the world.
- nextos 6y agoI like Debian as a community, but I think it would benefit from decentralization to speed up development. The community is great, but current package management techniques and processes are the equivalent of SVN, with modern approaches like Nix or Guix being the equivalent to Git. In Debian, the whole tree of packages has to be in sync. That works well for Arch, as it is a rolling release, but IMHO that slows down Debian as it doesn't use their manpower efficiently. Longtime ago, when Nix was not popular, there was a discussion in debian-devel about adopting Nix. It was probably premature. This discussion has resurfaced a number of times. I think currently they would benefit enormously from Nix or rolling out their own tooling that implemented equivalent ideas. With such a big community and large package set, packages should be able to be decoupled from each other so that they can depend on different library versions and move at their own pace. Also, Nix-like tooling would allow to automate and test most package updates when upstream changes, or find common vulnerabilities and exposures (CVEs) automatically. Currently, there's a lot of manual intervention needed to do this. This would also be advantageous for end users, as they could mix and match packages from different channels. PPAs are an inferior solution.
- jancsika 6y agoThese are great points. You might consider bringing it up with Debian developers again. Despite some of the difficulties the author mentioned in the article, Debian has successfully spearheaded some ambitious project-wide initiatives, like reproducible builds. So I don't think it's out of the question that they could vastly improve the packaging experience for both users and developers with something like Nix or Guix. Of course the biggest question is: how does one get there from here? For example-- can the Nix packaging approach coexist and play nice with the current Debian packaging system for years to come?
- ssivark 6y agoWhile I like and use (and even recommend) Archlinux, Debian’s track record is absolutely venerable. It’s a huge accomplishment to carry so many people and an ecosystem along with you over decades, doing all the unsexy tasks (the number of packages!) and serving as a stable platform in support of user freedom, on top of which others can build nimbler and sexier offerings. The Debian project deserves our utmost respect for its effectiveness in organizing a community around a goal.
- chuckSu 6y agok
- eznzt 6y agoThe best part of not using Arch Linux is not having to deal with the Arch Linux community.
- heavyset_go 6y agoDebian is one of the only distributions releasing images for 32-bit x86, old PPC, and other less popular architectures[1]. Arch just targets 64-bit x86. [1] https://wiki.debian.org/SupportedArchitectures https://wiki.debian.org/SupportedArchitectures
- pabs3 6y agoAt this point there are no porters for i386 and it no longer has the porter waiver from the release team, so it is likely at this point that Debian bullseye will support 32-bit x86. Old PPC and many other architectures were dropped from releases many years ago. There were no replies to the roll call for porters yet, so it looks like Debian bullseye will just be amd64 too, unless people are replying privately for some reason. https://lists.debian.org/msgid-search/CAM8zJQvyaL0quk57Tyzqb4jiE74BoCdfkkfDif+jUEbr7kOd+w@mail.gmail.com/firsthit https://lists.debian.org/msgid-search/CAM8zJQvyaL0quk57Tyzqb... https://news.ycombinator.com/item?id=25166634 https://news.ycombinator.com/item?id=25166634 https://news.ycombinator.com/item?id=24974822 https://news.ycombinator.com/item?id=24974822
- toyg 6y agoI expect all replies are private. There are plenty of people working on ARM, just to mention one other arch.
- hedora 6y agoArch isn’t x64 only. Manjaro’s an Arch derivative, and is the preloaded OS on Pine Book Pro’s (they used to preload debian). The switch is disappointing for me, since I’d prefer Debian with a minimalist wm. However, manjaro + kde is good enough for light usage, and definitely easier for more mainstream users.
- basicneo 6y agoSounds like Arch is still x64 only, if you have to use a derivative to use other architectures?
- bayindirh 6y agoFor personal use, maybe. For fleet usage, production, set'n'forget servers and any critical role, no. I can provision 100+ Debian servers in any configuration I want under 15 minutes by utilizing the features of the OS itself and, forget them after setting them up. We actually lost one Debian server in a system room (in a rack of unlabeled cluster of identical servers) and, it was working flawlessly when we re-found it months later.
- Dahoon 6y agoHow do you know if someone uses Arch Linux.....
- thom 6y agoI love the idea of Arch Linux and it probably is worth everyone who's really interested in Linux trying it at least once. But it's also the only distro I have used for probably more than 10 years where I found myself having to edit my X config to try and get something to work. At that point I just backed away from the keyboard slowly and realised it wasn't worth my time. I do still have a throwaway cheap VPS with Arch, but even then I can't recommend it because the security story is largely non-existent.
- dorfsmay 6y agoWhat about Fedora? I went SLS, Slackware, Debian, then Ubuntu for something like 15 years, and now just switched to Fedora + RPM Fusion, and so far much happier with it.
- toyg 6y agoFedora will be around as long as Redhat does, since it exists primarily as the RHEL unstable branch. Considering RH is now part of IBM, that might well be forever, but still, it’s largely about commercial involvement from a given company, like Ubuntu and Canonical etc.
- deleted 6y ago[deleted]
- bayindirh 6y agoFedora is the experimentation lab for RedHat. Test on Fedora, include in RedHat enterprise, retire to CentOS. That's a similar model of Testing, Stable, OldStable of Debian. Just with a different flavor.
- an_opabinia 6y agoIt's ironic this is the top comment, since the vibe I got from the post was that people waste way too much time discussing ideological things and not fixing any of the actual problems he encountered as a maintainer. The thing that's wrong with the Debian project is that ideological stuff doesn't anymore attract talented engineers who are interested in working for free on something dry like package management.
- joana035 6y agoFrom last two month there are 6 new Debian Developer and 10 new Debian Maintainers. This information is available at https://bits.debian.org https://bits.debian.org For me, working with packaging is a joy, once I learned how it works I see it as a thin wrapper around an upstream code base that, after built with whatever upstream tooling, is copied within a package alongside it's dependencies information.
- jbj 6y agoI got a different vibe with the association to a Churchill quote[1] I moved from Ubuntu to Debian a few years back, if I need anything beyond the ordinary I can always set it up manually and I am pretty content with that. [1] https://www.goodreads.com/quotes/267224-democracy-is-the-worst-form-of-government-except-for-all https://www.goodreads.com/quotes/267224-democracy-is-the-wor...
- csb6 6y agoWindows and macOS died?
- ardy42 6y ago> macOS died Classic Mac OS died, and what they call "Mac OS" now is really NeXTSTEP.
- csb6 6y ago“Death” seems a bit dramatic in this context.
- Volt 6y agoApple would disagree https://www.youtube.com/watch?v=Cl7xQ8i3fc0 https://www.youtube.com/watch?v=Cl7xQ8i3fc0
- ardy42 6y ago> “Death” seems a bit dramatic in this context. Classic Mac OS is about as dead as software can get: it's no longer developed or developed for, there's no backwards compatibility in its successors, and they don't even make hardware that can run it anymore.
- EamonnMR 6y agoWindows NT and MacOSX are both scratch rewrites. Though the author of the comment may be referring to the fact that Android and iOS dominate the space now.
- toyg 6y agoNo no, I referred to your point precisely: both Win and Macos had to be rewritten from scratch at some point.
- twblalock 6y ago> Debian is like democracy: the worst way of producing an OS, except all the others that have been tried from time to time. How many of us would be happy working at a software company with a bug tracker from the 90s, artifact management done with FTP, little to no tooling to manage large changes and do code review, no standards around source control, etc.? Those are symptoms of a software development culture stuck in the past. It would be pretty frustrating to go home from my day job, where we have a much better development workflow, and try to make a contribution to the Debian project using Debian's tools and processes. And I'm sure I'm not the only software engineer who would feel that way. That can become a real problem for the future of Debian if it's not addressed.
- joana035 6y agoCannot say for a company, but in Debian it seems that source code control is being settled with https://salsa.debian.org https://salsa.debian.org. For upstream code it is pretty flexible and low expectations are set, a tarball is enough. It also works with git (branches and/or tags), cvs, hg, etc. There is no need for complexity in order to transfer files, that is why File Transfer Protocol works well. If you refer to public FTP services, those were deprecated 3 year ago. See https://www.debian.org/News/2017/20170425 https://www.debian.org/News/2017/20170425
- raverbashing 6y agoAnd on top of that you also have to involve yourself into endless political discussions about minor topics while dealing with "complicated" maintainers Thanks but no thanks
- toyg 6y ago> How many of us would be happy working at a software company with a bug tracker from the 90s How many of us would be happy deciding things in groups with processes defined 100 or 200 years ago? But that's what representative democracy effectively does, every day, in most of the West. People just find ways to cope and move on, since the process is just a mean to an end. > That can become a real problem for the future of Debian if it's not addressed. Yes and no. Yes, processes should be improved all the time. No, it's not a real problem in the long run - I've been hear more or less the same story basically since Debian started, but it's still arguably the biggest and most relevant Linux distribution in existence. People come and go, the ideal endures.
- gautamcgoel 6y ago> Debian contributors don’t do it for the money, so they will be there when money runs out; and they don’t do it for being cool either, so they will be there when OS work is not cool. This is a great sentence, probably one of the most important (and underrated) ideas in FOSS and engineering more generally. A lot of critical work is not lucrative or glamorous - does your project recognize and support the people who do that work?
- vbernat 6y agoDebian is well known to not be a democracy. This is a do-ocracy. Votes are very rare and, except for systemd (2 in 10 years), are quite non-technical. The second key aspect is that you can't force anyone to do anything. The third key aspect is the project is unable to reach any consensus (there is always someone to disagree and do enough noise for the discussion to go nowhere and we cannot vote). Most of the points listed by Michael derive from that. It's impossible to change something. We can only do small things for which no cooperation is needed.
- rstuart4133 6y ago> It's impossible to change something. We can only do small things for which no cooperation is needed. And yet the migration to systemd, which required lots of changes in disparate packages, happened. And the migration away from python2 will happen too, albeit perhaps not as fast as the people driving it would like. And the new source format happened. And for repeatable builds - Debian leads the world. Methinks "we can only do small things for which no cooperation is needed" might be overstating the case a smidgen. Lots of things with aren't small happen in Debian on a regular basis.
- vbernat 6y agoMigration to systemd is painful and it needed two GR and a lot of drama to move forward. We had to wait debhelper 10 for it to not be a hack in packaging (2016). Migration away from python2 is wanted by doko, the Python maintainer. If he didn't want that, nothing would move. We were stuck for a long time with Python 2.6 because he didn't want to migrate to Python 2.7. As he is also maintainer of gcc and Java, nobody wanted to vote him out. I may have missed the headlines around the new source format. Ack for repeatable builds. What about bikesheds/PPA? Many discussions a few years back but mostly blocked because FTP masters want it to be integrated into DAK and under various other non-technical constraints.