11–20 of 46 posts
What he writes about version control and svn. > its fully centralized design is largely considered obsolete > ...it is still widely used, maintained, and appropriate for a few use cases, such as for folks who require centralization and/or increased security controls for one reason or another. Statements like this sour the whole book for me and makes me feel it's written by one whose experience is lacking.
What he writes about version control and svn. > its fully centralized design is largely considered obsolete > ...it is still widely used, maintained, and appropriate for a few use cases, such as for folks who require centralization and/or increased security controls for one reason or another. Statements like this sour the whole book for me and makes me feel it's written by one whose experience is lacking.
What he writes about version control and svn. > its fully centralized design is largely considered obsolete > ...it is still widely used, maintained, and appropriate for a few use cases, such as for folks who require centralization and/or increased security controls for one reason or another. Statements like this sour the whole book for me and makes me feel it's written by one whose experience is lacking.
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.
>2010s: Workplace domination by “lumber-sexuals” What
A not-so-manly man dressing like a lumberjack (although a lot more refined) and sporting a beard that has the volume of a lumberjacks beard and the groom of a hipster, cashing in on the "rugged, outdoor stereotype" Most of these guys aren't very good with their hands and only want to seem so because God forbid you would get those soft lotion treated hands dirty. Lumberjacks are typically known for their strength and…
Earlier quoted context omitted.
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.
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.
How many percentage of new projects use svn instead of git? That it a much better metric for how obsolete something is.
What he writes about version control and svn. > its fully centralized design is largely considered obsolete > ...it is still widely used, maintained, and appropriate for a few use cases, such as for folks who require centralization and/or increased security controls for one reason or another. Statements like this sour the whole book for me and makes me feel it's written by one whose experience is lacking.
"A few use cases" and "for one reason or another" both do sound dismissive, I agree.
What he writes about version control and svn. > its fully centralized design is largely considered obsolete > ...it is still widely used, maintained, and appropriate for a few use cases, such as for folks who require centralization and/or increased security controls for one reason or another. Statements like this sour the whole book for me and makes me feel it's written by one whose experience is lacking.
Fully centralized design is in fact largely obsolete. Centralized operations are still very relevant and important, but I doubt we will ever see a new version control system designed without distributed facilities. "A few use cases" and "for one reason or another" both do sound dismissive, I agree.
For the rest most companies are using git in a way very similar to svn, but now Github/Gitlab/Bitkeeper whatever provides the role of a single authorative central server.
Would love to see this in PDF. Is there a way to get it?