[dba-VS] [AccessD] Visual Studio and source control
Jim Lawrence
accessd at shaw.ca
Sun Nov 29 19:27:54 CST 2015
As for the Cloud there are some things that just can not be done any other way.
Huge files and incredible high processing speed come to mind.
One article, that discussed this comes to mind. In the old days a movie would easily fit on one of two rolls of "Nitrocellulose"...yes, it is as explosive as it sounds. Today that technology is all but gone. Movies are now digitized, are super high resolution, up to 64 frames a second but they take up a lot of drive space...and the media must be absolutely perfect...no data drops, not even a single pixel. Where else would anyone store the complete movie like "Gravity", that is 26 Pentabytes?
Then the new super computers. They use to be something like a single Cray but today a Cloud farm of thousands of interconnected CPUs running as a single computer, running at over 33.86 petaFLOPS (per second).
There is nothing that the Cloud couldn't do when it comes to bigger, faster and more reliable.
This technology is not just limited to big players at extraordinary costs. The prices are continuing coming down, if someone wants to go commercial and any enthusiast (Geek) can set up a small Cloud system in their basement, using off the shelf computers and software.
Jim
----- Original Message -----
From: "John Colby" <jwcolby at gmail.com>
To: "Development in Visual Studio" <dba-vs at databaseadvisors.com>
Sent: Saturday, November 14, 2015 1:31:49 PM
Subject: Re: [dba-VS] [AccessD] Visual Studio and source control
I suppose I just don't see the allure of doing my business development
on the cloud. I have had my private source control since I began using
C# many years ago. It has run like clockwork. It is completely inside
of my servers. Why would I go do it out on a public server all of a
sudden? This is not a public development effort. All I am really doing
is looking at moving from SVN to GitHub, and that only because VS now
has a GitHub connector. I have two largish servers that "belong" to the
client that this code is for. Everything else of the client's is on
those servers. There is simply no point in not keeping his stuff on his
servers.
At this point all of my development is on my own VMs running on these
servers (that I hand built ages ago) and the source control is on them
as well.
You have spent a great deal of effort questioning why I do this but no
effort explaining why I should not.
On 11/14/2015 4:08 PM, Salakhetdinov Shamil wrote:
> John --
>
> Even if your private bitbucket.org account will be hacked and locked down you'll still have a copy of your sources on your local system disks and in your local system backups, - if that is not safe enough IYO then you could also have backups on a few "cloud" sites.
>
> -- Shamil
>
--
John W. Colby
_______________________________________________
dba-VS mailing list
dba-VS at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-vs
http://www.databaseadvisors.com
More information about the dba-VS
mailing list