3 ms·
That's hilarious. Users of Maven and CPAN represent a "critical mass of small-scale developers"? Holy shit. A similar idea was voiced a few days ago, specifica
by cemerick 16y ago
That's hilarious. Users of Maven and CPAN represent a "critical mass of small-scale developers"? Holy shit.
A similar idea was voiced a few days ago, specifically regarding Java libraries (http://fnords.wordpress.com/2010/09/24/the-real-problem-with-java-in-linux-distros/ http://fnords.wordpress.com/2010/09/24/the-real-problem-with...).
My response remains the same: Debian (or what-have-you) is but one distro among many, and those of us that treat such things as important but fundamentally commodity deployment platforms have no wish to spend our lives babysitting whatever package manager happens to be on the operating system we're using that month/year/whatever. Further, plenty of people have plenty of good reasons for deploying on Windows and OS X, so using tools that work well there make sense.
The priorities of the various linux distros aren't everyone else's priorities – which somehow seems to come as a galloping shock to some.
- billswift 16y agoThat is why I use Slackware. Installing new software by hand from tarballs is a bit tedious compared to package managers, but it is transparent, and when I am done I can be pretty sure it is going to work. I have tried other distros, even Debian once (for some reason the Debian wouldn't let me sign in as root, I never did figure out why), but I keep coming back to Slackware - for its transparency.
- koenigdavidmj 16y agoAnd Slackware's packaging is light enough that it is fairly simple to write wrappers around gems/CPAN modules/Python eggs. The latter two have prewritten SlackBuilds that you can use, assuming that the setup.py is not doing anything too shady.