The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
No, that's stupid - TFS is run by people who are supposed to be "Cloud aware", and who certainly should know exactly what you - and I, and all 13, 718, 609 other members - want, need, and expect of a source control system. And they can't keep it up*? Not a good reflection on Azure really, considering how they see TFS as a stepping stone to Azure DevOps.
* Fnnr, fnnr - added to keep MM amused.
Sent from my Amstrad PC 1640 Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
How much are you actually saving? Are you paying for license to host your own server? Are you paying for Microsoft to provide you TFS? Either of those options seem like they would cost more than $7/mo (particularly licensing TFS, which I just looked up, ranging between $45 to $250 / month, but you can never a straight answer from Microsoft on how much something costs, given the options listed just on that page.
We're using Mercurial at my job, it's filebased, if you want it centralized you just put a repo on the fileserver and access it via VPN if needed.
But you don't even need a server, just start the builtin webserver.
Or in worst case, put the repo on a memorystick and pass it around. Not that I recommend it, mind you.
I'm sure we work in vastly different ways. I've been able to use TFS's offline mode for a few days in the past, and when going back online, it just "did the right thing" on its own to reconsolidate everything it had detected had been changed since.
The issue for us is Matthew and I are both make some extensive changes to the code in tandem and so we are constantly checking in and syncing our changes to ensure everything's dovetailing nicely. Something like this is a bit of a buzz kill because now our changes build up as commits and then when it comes back online the chances of conflicts (or worse: one of us going down the wrong path) is higher.
I think the real issue is being centralized. If Bitbucket ever went down for a few days, my coworkers and I could push back and forth to each others repos to keep in sync with each other as needed. (Or someone who enjoys the ops part of devops, could set up a temporary shared remote for us all to work off of until things got fixed.)
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt