Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft Office migration from Source Depot to Git

danielsada.tech

Post reply on HN
Print view View original

151–160 of 290 posts

Re: Microsoft Office migration from Source Depot to Git

#151

Post by kccqzy »

noitpmeder wrote: post #150
2d8a875f-39a2-4 wrote: post #117

Always nice to read a new retelling of this old story. TFA throws some shade at how "a single get of the office repo took some hours" then elides the fact that such an operation was practically impossible to do on git at all without creating a new file system (VFS). Perforce let users check out just the parts of a repo that they needed, so I assume most SD users did that instead of getting every app in the Office sui…

My firm still uses perforce and I can't say anyone likes it at this point. You can almost see the light leaves the eyes of new hires when you tell them we don't use git like the rest of the world.

I cannot believe that new hires would be upset by the choice of version control software. They joined a new company after so many hoops and it's on them for having an open mind towards processes and tools in the new company.

Re: Microsoft Office migration from Source Depot to Git

#152

Post by axus »

kccqzy wrote: post #151
noitpmeder wrote: post #150

Earlier quoted context omitted.

My firm still uses perforce and I can't say anyone likes it at this point. You can almost see the light leaves the eyes of new hires when you tell them we don't use git like the rest of the world.

I cannot believe that new hires would be upset by the choice of version control software. They joined a new company after so many hoops and it's on them for having an open mind towards processes and tools in the new company.

If companies don't cater to the whims of the youth, they'd have to hire... old people

Re: Microsoft Office migration from Source Depot to Git

#153

Post by kmoser »

sofixa wrote: post #103
dshacker wrote: post #42

Earlier quoted context omitted.

Even with this, there were many surprised people. I'm still amazed at all of the people that can ignore everything and just open their IDE and code (and maybe never see teams or email)

Alternatively, communications fatigue. How many emails does the average employee get with nonsense that doesn't apply to them? Oh cool, we have a new VP. Oh cool, that department had a charity drive. Oh cool, system I've never heard of is getting replaced by a new one, favourite of this guy I've never heard of. Add in the various spam (be it attacks or just random vendors trying to sell something). At some point, peo…

Everybody gets important emails, and it's literally part of their job to filter the wheat from the chaff. One of my benchmarks for someone's competency is their ability to manage information. With a combination of email filters and mental discipline, even the most busy inbox can be manageable. But this is an acquired skill, akin to not getting lost in social media, and some people are far better at it than others.

Re: Microsoft Office migration from Source Depot to Git

#154

Post by DanielHB »

kccqzy wrote: post #151
noitpmeder wrote: post #150

Earlier quoted context omitted.

My firm still uses perforce and I can't say anyone likes it at this point. You can almost see the light leaves the eyes of new hires when you tell them we don't use git like the rest of the world.

I cannot believe that new hires would be upset by the choice of version control software. They joined a new company after so many hoops and it's on them for having an open mind towards processes and tools in the new company.

I almost cried of happiness when we moved to git from SVN on my first job after being there for 6 months

They might not be upset on the first few weeks but after a month or so they will be familiar with the pain.

Re: Microsoft Office migration from Source Depot to Git

#155

Post by marcosdumay »

tamlin wrote: post #139
0points wrote: post #130

Having used vss in the 90s myself, it surprised me it wasn't even mentioned. VSS (Visual SourceSafe) being Microsoft's own source versioning protocol, unlike Source Depot which was licensed from Perforce.

Yes, I used VSS as a solo developer in the 90s. It was a revelation at the time. I met other VCS systems at grad school (RCS, CVS). I started a job at MSFT in 2004 and I recall someone explaining that VSS was unsafe and prone to corruption. No idea if that was true, or just lore, but it wasn't an option for work anyway.

> No idea if that was true

It's an absurd understatement. The only people that seriously used VSS and didn't see any corruption were the people that didn't look at their code history.

Re: Microsoft Office migration from Source Depot to Git

#156

Post by xeromal »

axus wrote: post #152
kccqzy wrote: post #151

Earlier quoted context omitted.

I cannot believe that new hires would be upset by the choice of version control software. They joined a new company after so many hoops and it's on them for having an open mind towards processes and tools in the new company.

If companies don't cater to the whims of the youth, they'd have to hire... old people

e-gad!

Re: Microsoft Office migration from Source Depot to Git

#157

Post by skipkey »

mmastrac wrote: post #142
tamlin wrote: post #139

Earlier quoted context omitted.

Yes, I used VSS as a solo developer in the 90s. It was a revelation at the time. I met other VCS systems at grad school (RCS, CVS). I started a job at MSFT in 2004 and I recall someone explaining that VSS was unsafe and prone to corruption. No idea if that was true, or just lore, but it wasn't an option for work anyway.

We used to call it Visual Source Unsafe because it was corrupting repos all the time.

As I recall, one problem was you got silent corruption if you ran out of disk space during certain operations, and there were things that took significantly more disk space while in flight than when finished, so you wouldn’t even know.

When I was at Microsoft, Source Depot was the nicer of the two version control systems I had to use. The other, Source Library Manager, was much worse.

Re: Microsoft Office migration from Source Depot to Git

#158

Post by larrywright »

0points wrote: post #130

Having used vss in the 90s myself, it surprised me it wasn't even mentioned. VSS (Visual SourceSafe) being Microsoft's own source versioning protocol, unlike Source Depot which was licensed from Perforce.

I used VSS in the 90s as well, it was a nightmare when working in a team. As I recall, Microsoft themselves did not use VSS internally, at least not for the majority of things.

Re: Microsoft Office migration from Source Depot to Git

#159

Post by mattl »

kccqzy wrote: post #151
noitpmeder wrote: post #150

Earlier quoted context omitted.

My firm still uses perforce and I can't say anyone likes it at this point. You can almost see the light leaves the eyes of new hires when you tell them we don't use git like the rest of the world.

I cannot believe that new hires would be upset by the choice of version control software. They joined a new company after so many hoops and it's on them for having an open mind towards processes and tools in the new company.

I worked with someone who was surprised the company didn’t use Bitbucket and Discord. They were unhappy about both.

Re: Microsoft Office migration from Source Depot to Git

#160

Post by MBCook »

israrkhan wrote: post #34
MBCook wrote: post #31

Could someone explain the ideas of forward integration and reverse integration in Source Depot? I’d never heard of Source Depot before today.

source depot is (was?) essentially a fork of perforce.

The article mentioned something along those lines, but I’ve never used it either.

I’ve only ever really used CVS, SVN, and Git.

Post reply on HN