News for hackers. Stuff that matters.
Re:Why I Fell in Love with Arch Linux (2015) by int_19h on Thursday September 14, 2017 @06:31AM (#15246536)
For me, the biggest point in favor of Arch is that it is a binary distro that seems to be closest to "vanilla" - meaning that packages are generally built directly from upstream, without heavy distro-specific patchsets applied by maintainers. There's still plenty of patches, mind you, but they're usually there to ensure that it builds and installs correctly in Arch environment, not to change functionality.

I also find Pacman to be noticeably faster than all other binary package managers. I just did a full package upgrade on a laptop that hasn't been upgraded since the beginning of this year, and yet it was able to compute a (fairly lengthy) list of packages to upgrade faster than I could blink.

Re:Why I Fell in Love with Arch Linux (2015) by jwilk on Thursday September 14, 2017 @09:15AM (#15247618)
Making /usr/bin/python point to Python 3 doesn't sound very vanilla to me.
Re:Why I Fell in Love with Arch Linux (2015) by bartkmq on Thursday September 14, 2017 @10:29AM (#15248354)
He defines 'vanilla' to mean 'build from upstream with little distro-specific changes'. So what does this have to do with making Python 3 the default python interpreter? I bet this symlink is not even part of the python source code; it's always a choice made by the distro maintainers.

Arch is known to be always cutting edge even if this sometimes means breaking stuff so this decision is not exactly surprising.

Re:Why I Fell in Love with Arch Linux (2015) by jwilk on Thursday September 14, 2017 @11:01AM (#15248695)
Removing an API that vast majority of Python programs were using (at that time), and replacing it with something incompatible is not a "little distro-specific change".
Re:Why I Fell in Love with Arch Linux (2015) by int_19h on Thursday September 14, 2017 @04:34PM (#15252271)
At the point where that was done, there was no formalized convention on it. Arch maintainers decided that it's preferable to default to the latest and greatest (which seems to be the general policy, and it meshes well with a bleeding-edge rolling release IMO). It was a mistake for Python specifically because of idiosyncrasies of Python 2 vs 3 story, and they have since corrected that mistake.