[fpc-other] [fpc-pascal] Google Code closing down

[Florian Klämpfl]

Am 16.03.2015 um 13:53 schrieb Graeme Geldenhuys:
> Hello Martin,
> 
> On 2015-03-16 12:35, Martin Frb wrote:
>> "better product", simply means: Compared to others it scores better on 
>> more use cases.
> 
> Agreed.  :-)
> 
> 
>> Different people learn in different ways. There will be a fair share of 
>> people for whom taking their first steps into using a repository is 
>> better done with a simpler system.
> 
> I fully understand that. I think the biggest resistance to migrating to
> git is the "distributed system" principle. 

For me
1) it is usability, mainly the gui, well, and other stuff like the un-memorizable hashes.
2) too much freedom :) svn forces me basically to finish patches: if I started to modify something,
it is the easiest to finish it than to store it somehow away. git doesn't, just commit when being
disturbed, add an unfinished in front of the commit message and I can/will continue with something
else when I come back. For an "idle" time project like FPC this is really a problem for me: my
git-svn copy contains currently around 60 unfinsished branches :(

And of course in case of FPC the huge effort to switch the whole infrastructure.

> That scares people. That is
> why I introduced the developers, at my previous employment, to git by
> simplifying things. I let them use a client/server workflow model. That
> seem to have helped them a lot, and get over that fear they had.