[Info-vax] Where to locate software

[Kerry Main]

> -----Original Message-----
> From: Info-vax [mailto:info-vax-bounces at info-vax.com] On Behalf Of
> Paul Sture via Info-vax
> Sent: 13-Jun-16 10:20 AM
> To: info-vax at info-vax.com
> Cc: Paul Sture <nospam at sture.ch>
> Subject: Re: [New Info-vax] Where to locate software
> 
> On 2016-06-13, Kerry Main <kerry.main at backtothefutureit.com> wrote:
> >> -----Original Message-----
> >> From: Info-vax [mailto:info-vax-bounces at info-vax.com] On Behalf Of
> >> lawrencedo99--- via Info-vax
> >> Sent: 12-Jun-16 8:50 PM
> >> To: info-vax at info-vax.com
> >> Cc: lawrencedo99 at gmail.com
> >> Subject: Re: [New Info-vax] Where to locate software
> >>
> >> On Monday, June 13, 2016 at 8:30:04 AM UTC+12, Kerry Main wrote:
> >
> > I can see using VCS systems like Git when you have to deal with
> external
> > code updates like the VSI folks, but when you have a closed system
> > that uses mostly custom code, I just do not see the logic.
> 
> Teleworking / working in different timezones / working offline ?
> 

Assume a Dev cluster is a 24x7x365 prod environment. The issues
you raise are due to poor practices in the past where a dev environment 
was not treated as a prod environment.

Who *really* works offline these days with no internet connection?

Ok, there are always a few small use cases, but even these are rapidly
disappearing.

> When you do a 'git clone' you get a local copy of the full source tree,
> including history; if your main server gets wiped out the full source
> tree is available on x clients.
> 
> > Certainly willing to have my eyes opened for the right reasons, but not
> > just to become politically correct in the developer world.
> 
> Try this article for starters:
> 
> <http://blog.teamtreehouse.com/why-you-should-switch-from-
> subversion-to-git>
> 

Ok, I read this article and it is incredible how 90's that thinking is.  This
author pushing his Git book obviously has little experience with modern 
day Operation environments.

As an example - 
" Imagine for a moment your SVN server having a hard drive corruption - 
when was your last backup and how many hours will it take to get to the 
point where your team can start working again?"

Holy crap - in a prod 24x7x365 environment today you have RAID and 
other HW technologies to prevent these types of things. If you need 
something more current than last night's disk-to-disk backup, or if you 
are really worried about SW corruption, then take snapshots during the 
day between daily backups.

This type of statement is not a valid argument given today's prod 
processes and technologies.

Another example -
" You can continue to use a centralized workflow, with one central server 
that everyone pushes to and pulls from."

Really? Why not have a clustered server to get around the "aah.. what
If the back end server is not available?" type arguments? Or to provide
additional back end scalability? Perhaps make it part of a multi-site
cluster if one was really worried about the dev back end server?

While I am not trying to promote one vs the other, here is a counter 
SVN vs Git article for you:
https://svnvsgit.com/ 

:-)

Regards,

Kerry Main
Kerry dot main at starkgaming dot com