5 ms·

Those statements are mostly true. One of those few use cases where centralized version control still has a lot traction is game dev. Because of large files and

Those statements are mostly true. One of those few use cases where centralized version control still has a lot traction is game dev. Because of large files and a need to manage them efficiently on relatively limited local disks.

sureaboutthis 8y ago
FreeBSD uses it for the operating system. While he complains that svn is obsolete, he then goes on to say it's widely used, and so far, it seems pretty important when games and operating systems--and more--are using it.
- dtech 8y ago
  obsolete ≠ unimportant. I think most would agree that COBOL is an obsolete programming language, yet half the worlds financial systems still run on it. How many percentage of new projects use svn instead of git? That it a much better metric for how obsolete something is.
  - sontek 8y ago
    Obsolete means to no longer be produced or used... These things are not obsolete. They aren't cool / widely used but definitely not obsolete if half the worlds financial systems still run on them.
    - dtech 8y ago
      From merriam webster: 1a : no longer in use or no longer useful // an obsolete word b : of a kind or style no longer current : old-fashioned // an obsolete technology A good example is a satellite, lots of older (obsolete model) satellites are still in orbit and performing well, and replacing them is not worth the cost. But if a new satellite is needed the newest model will be send up, not the obsolete model.
- yaccz 8y ago
  iirc FreeBSD is sticking with svn because git is GNU licensed
koonsolo 8y ago
You also have to ask the question if the "distributed" functionality is really necessary. Even if companies use git or mercurial or whatever, most have a central repository anyway. They basically offer no extra value over Subversion on that specific (but most prominent) feature in practice.
- maxxxxx 8y ago
  A lot of the young guys I work with don't even really know about the distributed characteristics. For them git is Bitbucket or Github. that's all they know.
  - sanderjd 8y ago
    They'll learn. Things like cheap branching didn't become useful to me until I had a bunch of stuff going on at once, which didn't happen until I graduated to more senior roles.
- IggleSniggle 8y ago
  One great side effect of distributed is that even if your use case is generally centralized, you de facto have a lot of valid backup states available if something in the central repo gets borked in some destructive way.

sureaboutthis 8y ago

FreeBSD uses it for the operating system. While he complains that svn is obsolete, he then goes on to say it's widely used, and so far, it seems pretty important when games and operating systems--and more--are using it.

dtech 8y ago
obsolete ≠ unimportant. I think most would agree that COBOL is an obsolete programming language, yet half the worlds financial systems still run on it. How many percentage of new projects use svn instead of git? That it a much better metric for how obsolete something is.
- sontek 8y ago
  Obsolete means to no longer be produced or used... These things are not obsolete. They aren't cool / widely used but definitely not obsolete if half the worlds financial systems still run on them.
  - dtech 8y ago
    From merriam webster: 1a : no longer in use or no longer useful // an obsolete word b : of a kind or style no longer current : old-fashioned // an obsolete technology A good example is a satellite, lots of older (obsolete model) satellites are still in orbit and performing well, and replacing them is not worth the cost. But if a new satellite is needed the newest model will be send up, not the obsolete model.
yaccz 8y ago
iirc FreeBSD is sticking with svn because git is GNU licensed

koonsolo 8y ago

You also have to ask the question if the "distributed" functionality is really necessary. Even if companies use git or mercurial or whatever, most have a central repository anyway. They basically offer no extra value over Subversion on that specific (but most prominent) feature in practice.

maxxxxx 8y ago
A lot of the young guys I work with don't even really know about the distributed characteristics. For them git is Bitbucket or Github. that's all they know.
- sanderjd 8y ago
  They'll learn. Things like cheap branching didn't become useful to me until I had a bunch of stuff going on at once, which didn't happen until I graduated to more senior roles.
IggleSniggle 8y ago
One great side effect of distributed is that even if your use case is generally centralized, you de facto have a lot of valid backup states available if something in the central repo gets borked in some destructive way.