Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Upcoming SlideShare
What to Upload to SlideShare
Next
Download to read offline and view in fullscreen.

Share

Will Git Be Around Forever? A List of Possible Successors

Download to read offline

What source control software did you use in 2008? Possibly Git, if you were an early adopter or a Linux kernel committer. But chances are you were using Subversion, as this was the product of choice for the majority of the software developers. Ten years later, Git is the most popular product. Which makes me wonder: what will we use another ten years from now?

In this talk we will think about what features we want from our source control software in 2028. More speed? Better collaboration support? No merge conflicts ever?

I’ll also discuss a few products that have been published after Git emerged, including Fossil, Veracity and Pijul. I’ll talk about the extent to which they contain the features we so dearly desire and I’ll demonstrate a few typical use cases. To conclude, I’ll try to predict which one will be ‘the top dog’ in 2028 (all information is provided “as is”, no guarantees etc. etc.).

So attend this session if you’re excited about the future of version control and if you want to have a shot at beating even (!) the early adopters. Now if it turns out I was right, remember that you heard it here first. 

Related Books

Free with a 30 day trial from Scribd

See all
  • Be the first to like this

Will Git Be Around Forever? A List of Possible Successors

  1. 1. Will Git Be AroundWill Git Be Around Forever?Forever? A List Of Possible SuccessorsA List Of Possible Successors Hanno Embregts @hannotify
  2. 2. https://tenor.com/view/stroopwafel-caramel-gif-5308327
  3. 3. Teaching aTeaching a course on Gitcourse on Git https://pxhere.com/en/photo/652221
  4. 4. http://blog.plasticscm.com/2010/11/version-control-timeline.html
  5. 5. http://web.archive.org/web/20050408062838/http://www.bitkeeper.com/press/2005-04-05.html
  6. 6. http://blog.plasticscm.com/2010/11/version-control-timeline.html
  7. 7. https://upload.wikimedia.org/wikipedia/commons/thumb/3/31/Bill_Gates_2004.jpg/1280px-Bill_Gates_2004.jpg
  8. 8. "640K ought to be enough for anybody." https://upload.wikimedia.org/wikipedia/commons/thumb/3/31/Bill_Gates_2004.jpg/1280px-Bill_Gates_2004.jpg
  9. 9. Photo credit: Ryan McGuire
  10. 10. Why did GitWhy did Git become sobecome so popular?popular? https://pxhere.com/en/photo/652221
  11. 11. Main features of GitMain features of Git Distributed Free & open-source Fast Optimized for branching
  12. 12. Some surprising factsSome surprising facts on Giton Git https://www.infoworld.com/article/2669670/after-controversy--torvalds-begins-work-on--git-.html
  13. 13. Some surprising factsSome surprising facts on Giton Git "I'm an egotistical bastard, so I name all my projects after myself. First Linux, now git." https://www.infoworld.com/article/2669670/after-controversy--torvalds-begins-work-on--git-.html
  14. 14. WWCVSND?WWCVSND? If in doubt, make the exact opposite decision. https://pxhere.com/en/photo/704019
  15. 15. Killer features.Killer features. prediction variable #1 https://www.pexels.com/photo/photo-displays-person-holding-ball-with-re ection-of-horizon-940880
  16. 16. https://blog.gitprime.com/git-didnt-beat-svn-github-did
  17. 17. Hosting platformHosting platform support.support. prediction variable #2 https://www.pexels.com/photo/photo-displays-person-holding-ball-with-re ection-of-horizon-940880
  18. 18. Open-sourceOpen-source community support.community support. prediction variable #3 https://www.pexels.com/photo/photo-displays-person-holding-ball-with-re ection-of-horizon-940880
  19. 19. https://bingeprints.com/products/there-are-two-types-of-people-those-who-can-extrapolate-from-incomplete-data-mug-funny-statistics-math-co ee-cup-1
  20. 20. https://blog.gitprime.com/git-didnt-beat-svn-github-did
  21. 21. First PredictionFirst Prediction 2009 Subversion 43% Git 19% Mercurial 16% TFS 6% CVS 5%
  22. 22. https://blog.gitprime.com/git-didnt-beat-svn-github-did
  23. 23. First PredictionFirst Prediction 2009 2019 Subversion 43% 8% Git 19% 73% Mercurial 16% 12% TFS 6% 7% CVS 5% <1%
  24. 24. https://blog.gitprime.com/git-didnt-beat-svn-github-did
  25. 25. First PredictionFirst Prediction 2009 2019 2029 Subversion 43% 8% 4% Git 19% 73% 80% Mercurial 16% 12% 9% TFS 6% 7% 7% CVS 5% <1% <1%
  26. 26. One problem though.One problem though. We haven't included any new products! https://www.pexels.com/photo/man-in-black-shirt-and-gray-denim-pants-sitting-on-gray-padded-bench-1134204
  27. 27. The BrowserThe Browser WarsWars https://pxhere.com/en/photo/652221
  28. 28. In ten years time...In ten years time... 1. ...Internet Explorer would be surpassed as the top browser family; 2. ...Mozilla Firefox would surpass Internet Explorer; 3. ...Mozilla Firefox would be the top browser.
  29. 29. In ten years time...In ten years time... 1. ...Internet Explorer would be surpassed as the top browser family; 2. ...Mozilla Firefox would surpass Internet Explorer; 3. ...Mozilla Firefox would be the top browser.
  30. 30. https://www.bbntimes.com/en/global-economy/market-shares-for-browsers-and-platforms
  31. 31. https://tenor.com/view/youright-right-point-gif-9467383
  32. 32. The disadvantage ofThe disadvantage of the dominant productthe dominant product You will get a lot of attention. https://www.pexels.com/photo/battle-black-blur-board-game-260024
  33. 33. The disadvantage ofThe disadvantage of the dominant productthe dominant product prediction variable https://www.pexels.com/photo/photo-displays-person-holding-ball-with-re ection-of-horizon-940880
  34. 34. Four New(er)Four New(er) Kids On TheKids On The BlockBlock https://pxhere.com/en/photo/652221
  35. 35. Four new(er) kinds onFour new(er) kinds on the blockthe block Fossil (2006) Plastic (2006) Veracity (2011) Pijul (2015)
  36. 36. Veracity (2011)Veracity (2011) Distributed version control Issue tracking and wiki, also distributed http://www.veracity-scm.com
  37. 37. ButBut Veracity is not going to be 'the Git killer'Veracity is not going to be 'the Git killer' Development status: web site appears unmaintained; latest release March 25, 2013 Hosting platform hasn't been online since February 4, 2015 www.onveracity.com
  38. 38. PlasticPlastic Fast branching Merge previews Both central and distributed Comes with a lot of GUI stu
  39. 39. Focus on artists andFocus on artists and designersdesigners 'Plastic Gluon' is a version control component meant for artists and designers Image di ng References on their website are exclusively from game studios
  40. 40. ButBut Plastic is not going to be 'the Git killer'Plastic is not going to be 'the Git killer' it's not open-source software Git users are not changing their VCS just for some eye candy
  41. 41. FossilFossil https://pxhere.com/en/photo/652221
  42. 42. Features that FossilFeatures that Fossil promisespromises distributed version control integrated bug tracking, wiki, forum and technotes built-in web interface autosync mode show descendants of a check-in supports operations on multiple repositories (fossil all) https://www.fossil-scm.orghttps://www.fossil-scm.org
  43. 43. Quick factsQuick facts Written in C and SQL Is the VCS of choice for the SQLite project 'Github in a box' Free code hosting at: Chisel - SourceForge - http://chiselapp.com/ http://fossilrepos.sourceforge.net
  44. 44. Uses a relationalUses a relational databasedatabase a repository is stored in a single SQLite database le contains relations between check-ins to be able to produce both ancestors and descendants of a check-in
  45. 45. 'Github in a box''Github in a box' repository UI (fossil ui) wiki, ticketing & bug tracking embedded documentation technical notes forum
  46. 46. Quick demoQuick demo Up and running Using the web interface (fossil ui) Retrieving descendants of a checkin Resolving con icts
  47. 47. The BadThe Bad Dealing with large les Dealing with large commits https://www.omiyagames.com/blog/2014/02/15/farewhttps://www.omiyagames.com/blog/2014/02/15/farew fossil-version-controlfossil-version-control
  48. 48. Fossil for Git usersFossil for Git users https://www.fossil-https://www.fossil- scm.org/home/doc/trunk/www/fossil-v-git.wikiscm.org/home/doc/trunk/www/fossil-v-git.wiki
  49. 49. PijulPijul https://pxhere.com/en/photo/652221
  50. 50. pi · julpi · julpi · julpi · julpi · jul or crotophaga sulcirostris, a bird known to do collaborative nest building. https://commons.wikimedia.org/wiki/File:Museo_de_la_Naturaleza_de_Cantabria_(208).jpg
  51. 51. Features that PijulFeatures that Pijul promisespromises distributed version control simple, because of its basis on a sound theory of patches fast, because it aims to x the Darcs performance issues interactive recording https://www.pijul.comhttps://www.pijul.com
  52. 52. Quick factsQuick facts written in Rust bootstrapped since April 2017 free code hosting at https://nest.pijul.com
  53. 53. Patch-oriented designPatch-oriented design A patch is an intuitive atomic unit of work. It focuses on changes, instead of di erences between snapshots (i.e. Git commits). Applying or unapplying a patch doesn't change its identity. The end result of applying several patches is always the same, regardless of the order in which they were applied. Pijul keeps track of 'dependent patches' No merges or rebases; applying a patch is like git cherry-pick.
  54. 54. Quick demoQuick demo Up and running Recording patches Branches Resolving Con icts Nest demo - https://nest.pijul.com/pijul_org/pijul
  55. 55. The BadThe Bad Usability needs to improve https://mivehind.net/2017/04/09/pijul- rst-thoughtshttps://mivehind.net/2017/04/09/pijul- rst-thoughts
  56. 56. Pijul for Git usersPijul for Git users https://nest.pijul.com/tae/pijul-for-git-usershttps://nest.pijul.com/tae/pijul-for-git-users
  57. 57. PredictionsPredictions https://pxhere.com/en/photo/652221
  58. 58. Prediction variablesPrediction variables Killer features. Hosting platform support. Open-source community support. The disadvantage of the dominant product.
  59. 59. Git Hg TFS Fossil Pijul Features -1 -1 -1 +1 +2
  60. 60. Git Hg TFS Fossil Pijul Features -1 -1 -1 +1 +2 Hosting +2 +1 -1 0 0
  61. 61. Git Hg TFS Fossil Pijul Features -1 -1 -1 +1 +2 Hosting +2 +1 -1 0 0 Open-source +2 +2 -2 -1 +1
  62. 62. Git Hg TFS Fossil Pijul Features -1 -1 -1 +1 +2 Hosting +2 +1 -1 0 0 Open-source +2 +2 -2 -1 +1 Dominant -2 -1 0 0 0
  63. 63. Git Hg TFS Fossil Pijul Features -1 -1 -1 +1 +2 Hosting +2 +1 -1 0 0 Open-source +2 +2 -2 -1 +1 Dominant -2 -1 0 0 0 +1 +1 -4 0 +3
  64. 64. 2029 Git 80% Mercurial 9% TFS 7% Subversion 4% CVS <1%
  65. 65. 2029 2029 Git 80% 77% Mercurial 9% 8% Pijul 5% TFS 7% 4% Subversion 4% 4% Fossil 2% CVS <1% <1%
  66. 66. FurtherFurtherFurtherFurtherFurther readingreadingreadingreadingreading https://www.pexels.com/photo/white-teddy-bear-reading-book-33196/
  67. 67. Further readingFurther reading "Beyond Git" (by Paweł Świątkowski) "Merging, patches and Pijul" (by Joe Neeman) "The Pijul Manual" http://katafrakt.me/2017/05/27/beyond-git/ https://jneem.github.io/pijul/ https://pijul.org/manual/introduction.html
  68. 68. AnyAnyAnyAnyAny questions?questions?questions?questions?questions? https://www.pexels.com/photo/monopoly-car-piece-1634213/
  69. 69. Thank you! ☺ Thank you! ☺  FINAL: https://hannotify.github.io @hannotify hanno.embregts@infosupport.com

What source control software did you use in 2008? Possibly Git, if you were an early adopter or a Linux kernel committer. But chances are you were using Subversion, as this was the product of choice for the majority of the software developers. Ten years later, Git is the most popular product. Which makes me wonder: what will we use another ten years from now? In this talk we will think about what features we want from our source control software in 2028. More speed? Better collaboration support? No merge conflicts ever? I’ll also discuss a few products that have been published after Git emerged, including Fossil, Veracity and Pijul. I’ll talk about the extent to which they contain the features we so dearly desire and I’ll demonstrate a few typical use cases. To conclude, I’ll try to predict which one will be ‘the top dog’ in 2028 (all information is provided “as is”, no guarantees etc. etc.). So attend this session if you’re excited about the future of version control and if you want to have a shot at beating even (!) the early adopters. Now if it turns out I was right, remember that you heard it here first. 

Views

Total views

898

On Slideshare

0

From embeds

0

Number of embeds

5

Actions

Downloads

3

Shares

0

Comments

0

Likes

0

×