Re:The new MacBook Pros with T2 chips do indeed kernel panic...
by alrs on Saturday August 18, 2018 @09:52PM
(#17792071)
You're never going to run Arch in production, so developing against "current" software means "hire a team of sysadmins to package all of these future-versions in to the conservative distro that we have in prod".
With luck it will be less than $1M/yr.
This is why people don't use homebrew anymore, either. If you're running a Mac you dev in a Docker container that reflects your production environment.
Re:The new MacBook Pros with T2 chips do indeed kernel panic...
by rl3 on Sunday August 19, 2018 @02:43AM
(#17792943)
I think you're making assumptions here. GP said that Arch allows them to be current in the code they run.
That doesn't mean they're developing against Arch.
Re:The new MacBook Pros with T2 chips do indeed kernel panic...
by icebraining on Saturday August 18, 2018 @07:10PM
(#17791371)
My Debian Unstable laptop installation is over ten years old (and on its third laptop), and the packages are pretty recent, since Unstable is a rolling version.
And despite the name, it's pretty solid, I don't remember the last issue I had with it.
Don't get me wrong, technically you can make Ubuntu just as flexible but you have to try to configure it that way. All the conveniences they brought into these distros for simple package management actually sets you up for failure when you are doing larger upgrades. Not to mention that the packages in their repos are often out of date.
I never had my Arch box fail me across upgrades, allowing me to actually be current in the code I run.
It's a healthy middle between Gentoo and CentOS if you don't want to build it all from source but yet still be current.
Even opkg and some IPAs are better than the package manager experience I had with apt-get or yum/dnf.