sudo aptitude install rails only applies to Ubuntu/Debian-like distros. On a team of developers, if you have a developer using Gentoo what can he do? With this binary distribution he doesn't have to reinstall his machine to have a development environment like the other developer's running Ubuntu. Also if Ubuntu decides to upgrade to MySQL X+1, I can still keep my development environment using MySQL X. Of course this applies to the rest of the software packages with LinRails. When you have a team using an RAD/Agile Development the last thing you want to worry about is having incompatibilities in software tools between your team.
"We decided to this so that we can share the same development environment with all the team. If programmers have a different Linux distro/version, they will still share the same development environment. This prevents programmers to say "well, it works on mine" when there is a problem. Also if you have a Linux distro package, versions may change when a new Linux distro is released. Also if you want to upgrade to the latest and greatest you are at the mercy of the Linux distribution. We will try to always have the latest versions of each tool. This helps to solve those problems."
This helps have a standard development environment between programmers in a team. This prevents stuff like "well it works on my MySQL/Rails machine" in addition to just downloading and unzip a file to get started.
Slashdot Mirror
sudo aptitude install rails only applies to Ubuntu/Debian-like distros. On a team of developers, if you have a developer using Gentoo what can he do? With this binary distribution he doesn't have to reinstall his machine to have a development environment like the other developer's running Ubuntu. Also if Ubuntu decides to upgrade to MySQL X+1, I can still keep my development environment using MySQL X. Of course this applies to the rest of the software packages with LinRails. When you have a team using an RAD/Agile Development the last thing you want to worry about is having incompatibilities in software tools between your team.
From their blog:
"We decided to this so that we can share the same development environment with all the team. If programmers have a different Linux distro/version, they will still share the same development environment. This prevents programmers to say "well, it works on mine" when there is a problem. Also if you have a Linux distro package, versions may change when a new Linux distro is released. Also if you want to upgrade to the latest and greatest you are at the mercy of the Linux distribution. We will try to always have the latest versions of each tool. This helps to solve those problems."
Mongrel people dont recomment Lighttpd here. So here is the debate:
* mongrel with nginx
* lighttpd with fastcgi
* apache
This helps have a standard development environment between programmers in a team. This prevents stuff like "well it works on my MySQL/Rails machine" in addition to just downloading and unzip a file to get started.