On 23 Mar 2011, at 16:26, Jon Jensen wrote: > On Mar 23, 2011, at 4:17 PM, Wade Preston Shearer wrote: > >> What is the benefit of having your development environment be local instead >> of remote? I can think of several cons. The only pro I can think of is that >> you don't have to have an internet connection. > > 1. you don't need an internet connection > 2. it's (hopefully) faster because it's local > 3. by definition, it's truly sandboxed (i.e. other devs can't screw it up). a > shared dev environment can be a whole bag of hurt > 4. if you're using git, this is a no-brainer and makes life much easier. > everything is local, you can easily work on different branches at the same > time, etc. > > Plus if you've solved the whole > getting-a-dev-environment-set-up-anywhere-quickly problem, it becomes super > easy to spin up new ones and have more than one (e.g. you have your stable > branch and want to see how it interacts with a dev branch, so you need one of > each side-by-side). > > I don't really know of any disadvantages. If you want people to see your > stuff in a common staging/sandbox rather than on your laptop, that's where > version control and continuous deployment come in handy. >
Coda ++ I agree with Jon. I develop on my local machine. My local machine is a laptop. I can develop any where any time. Speed is great. I also agree with using a versioning system (svn, git, whatever). Even if you have a local system backup, the versioning system makes things much easier, especially when you nuke some code and then decide, oops, I needed that. _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
