If Slackware disappeared tomorrow, what would you run?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
View Poll Results: What would you run if Slackware disappeared tomorrow?
Altogether Python has become very intrusive, almost as much so as systemd. In LFS, it used to relegated to BLFS, where it was needed in particular for Xorg and firefox. Now Python3 has to be built in LFS because several essential packages build with meson and ninja rather than autotools. I don't like these developments at all.
Altogether Python has become very intrusive, almost as much so as systemd. In LFS, it used to relegated to BLFS, where it was needed in particular for Xorg and firefox. Now Python3 has to be built in LFS because several essential packages build with meson and ninja rather than autotools. I don't like these developments at all.
No, because C is the foundation of Unix. As far as I can recall, Bell UNIX was the first OS to be written in a high-level language and it was written in C. C is a compiled language, so all you need to implement it is a compiler and a linker.
Python is an interpreted language that runs in its own environment. It's a very high level object-oriented language. There's nothing basic or fundamental about it. When I first started using Linux, Python was used mainly for desktop applications, where code readability was a particular advantage. It was never intended to be a fundamental part of any OS.
I do agree that it's kind of ridiculous that glibc requires Python just to build, but in general I see programming languages as tools. Some are more suited for certain jobs than others. C is definitely not the best tool for every job. If Python is "intrusive," it's more akin to how C is intrusive than how systemd is intrusive.
Last edited by montagdude; 02-09-2019 at 12:55 PM.
I think it goes without saying that most users of other distros would continue to use whatever distro they are currently using if Slackware disappeared tomorrow.
if slackware disappeared tomorrow i would run straight in to an insane asylum, just kidding, i would probably seriously consider abandoning linux while I refreshed relearn my BSD skills with a fresh install of FreeBSD, it would be a rough and rocky road but it will be a road i must travel because distros like ubuntu, fedora, arch, and now debian since systemd and has anyone tried out Debian testing lately, look in the tree in / all the directories like /bin point to /usr/bin and /sbin point to /usr/sbin and /lib to /usr/lib there is some sort of weirdless going on with debian now that i dont feel comfortable with especially since the switch to systemd, i know GNU's not unix but does it have to slowly turn in to something akin to MS_Windows? thats what systemd makes me think
I know I commented on this thread but it seems like forever - so an update:
If Slackware were ever to go *poof* , I would fall back on Devuan and I am actively exploring FreeBSD as another backup - in case Devuan were also ever to go *poof*.
Fedora. Because I want up-to-date components and I don't want to run Arch
Up until now, I would have said Ubuntu (with added PPAs, of course). That's what I voted for in the poll. But the fact that Ubuntu's going to become a 64-bit-only distro has changed that.
I'd try Void before making the final decision though.
+1 for Fedora. It's a very mature and stable distro with a great support community. I, too, previously said Ubuntu but my opinion of Ubuntu is changing recently. One reason is the lack of 32-bit support in the latest release(s), but also the way Canonical is bloating the os and the new snap package system smells like trouble to me.
I also was never a fan of the semi-annual release schedule. As much as I grow impatient waiting for the next Slackware, I would rather wait for a solid stable system than to have a bunch of new stuff thrown together with band-aids and duct tape just to have a new release on a scheduled date. Win10 copied that and look what it does for Microsoft.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.