1. 7

    I remember playing with Slackware around 20 years ago - it was so nice fast distribution with dead simple package management. Non-standard software you had to compile yourself with all the dependencies resolved on your own :) Oh fond memories…

    1. 2

      I started off with Slackware in 1996. I got a six-pack (I believe) of Linux distros on cdrom. It shipped Red Hat, Debian and Slackware.

      My friend told me Slackware is the hardest-core so I decided to jump in the deep end immediately.

      Zero regrets!

      1. 3

        Same for me but two years later, 1998. Using Slackware was likely one the biggest contribution to my career. The fact that it forced me to really understand what was going on taught me so much about operating systems, software development and open source. I haven’t used Slack in a looong time, but I hold it dear in my memories!

        1. 2

          Exactly! And these were times before Google, even, so everything had to be learned the hard way. Like patching Joliet support into the kernel for cdroms.

          LFS was another big thing. I ran that for quite a while too, think with Debian packaging.

          The switch to Debian, after forays into Red Hat and Mandrake, felt like a nice retirement from that, like something I’d earned through self-education.

      2. 2
        1. 1

          Nowadays the package management is as simple as ever, but the collection of binary packages is huge and very up to date (much more so than ubuntu). For example, there are only a few days between a new release of gcc or clang and their official slackware packages, so you always run a really modern system.

        1. 3

          For sending email, you really should be using a email service such as Sendgrid, MailChimp or Amazon’s SES. Sending automated email though an normal email account will likely get you flagged as spam, or get blocked by the provider.

          1. 8

            Someone can correct me if I’m wrong but Ruby used to be interpreted up to 1.8.x, then 1.9 introduced a bytecode and internal VM.

            Rails was created while 1.8 was still the stable version, and that remained true for a couple of years, so many Rails application were running in production with a pure interpreted language.