Add chapters

[?]
May 20, 2019, 7:27 PM
4AZS4L6BP7TTCR5RUB36TG5PTEEIMSTGKB5IVB5QNHJVMRF7LMZQC

Dependencies

Change contents

  • file addition: browser-shares-2007-2018.jpg (----------)
    [3.1221]
  • file addition: pijul.jpg (----------)
    [3.1221]
  • file addition: the-browser-wars-2005.png (----------)
    [3.1221]
  • file addition: usb-sticks.jpg (----------)
    [3.1221]
  • edit in index.html at line 43
    [3.29503286][3.29503286:29503916](),[3.29503916][2.2035189:2037299](),[3.973653][3.29503946:29503977](),[2.2037299][3.29503946:29503977](),[3.29503946][3.29503946:29503977](),[3.29503977][3.10636:10651]()
    <section>
    <section>
    <h2>Will Git Be Around</h2>
    <h1>Forever?</h1>
    <h4>A List Of Possible Successors</h4>
    <table>
    <tr>
    <td style="vertical-align: middle;">Hanno Embregts</td>
    <td style="text-align: right;"><img width="20%" data-src="img/icons/twitter-white.png" class="no-background"/></td>
    <td style="vertical-align: middle; padding: 0 0 0 0"><a href="https://www.twitter.com/hannotify">@hannotify</a></td>
    </tr>
    </table>
    <img data-src="img/logos/voxxed-days-athens.png" width="40%" class="no-background"/>
    <br/>
    <aside class="notes">
    <p>
    <strong>Time Elapsed:</strong> 0 min.
    </p>
    <p>
    Hi, my name is Hanno.
    I'm from the Netherlands, where I work at Info Support as an IT consultant.
    Besides doing consultancy work, I also teach a few courses.
    Now at Info Support we offer a wide range of courses, which exist mainly to get our junior colleagues up to speed with important concepts or products they'll need for their daily work.
    </p>
    <p>
    One of the courses I teach is called 'Git for Developers'.
    It's a one-day course where we teach the students how to use Git as a developer (none of that GUI stuff of course; command-line For The Win!).
    Besides doing the practical stuff we also discuss the pros and cons of distributed version control systems and how they compare to the earlier VCS's, like CVS and Subversion.
    Now the other day a student came to me after attending the course and said: "Git is great and all that, but what is gonna be the next big thing?"
    </p>
    <p>
    Which was a great question, because I couldn't really answer it.
    I was quite sure distributed version control systems like Git and Mercurial would be around for a while longer, so that's what I told him.
    And he replied: "Surely Git won't be around forever?!"
    Now I really hated the fact that I couldn't tell him more on the subject, so I decided to research the matter a bit further.
    And what started out as finding the answer to a simple question turned into giving a conference talk.
    Which is the one you're attending right now!
    </p>
    <p>
    So, welcome to you all.
    I'm gonna assume that you are all more or less like the student I told you about.
    He just couldn't believe that everything in version control land would stay the same for a long period of time.
    And I hope you're also a little bit like me, when you also can't stand not being able to know the answer to a question.
    So, let's see if we can find the answer together, shall we?
    </p>
    </aside>
    </section>
    </section>
  • replacement in index.html at line 59
    [3.11118][3.11118:11195]()
    <section data-markdown="sections/4-the-three-version-control-systems.md"
    [3.11118]
    [3.11195]
    <section data-markdown="sections/4-new-kids-on-the-block.md"
  • file deletion: 4-the-three-version-control-systems.md (----------)
    [3.11836][3.12038:12100](),[3.12100][3.12019:12019]()
    # The Three VCS's
    note:
    **Time Elapsed:** 20 min.
  • edit in sections/1-preface.md at line 1
    [3.11858]
    [3.95343]
    <h2>Will Git Be Around</h2>
    <h1>Forever?</h1>
    <h4>A List Of Possible Successors</h4>
    <table>
    <tr>
    <td style="vertical-align: middle;">Hanno Embregts</td>
    <td style="text-align: right;"><img width="20%" data-src="img/icons/twitter-white.png" class="no-background"/></td>
    <td style="vertical-align: middle; padding: 0 0 0 0"><a href="https://www.twitter.com/hannotify">@hannotify</a></td>
    </tr>
    </table>
    <img data-src="img/logos/voxxed-days-athens.png" width="40%" class="no-background"/>
    <br/>
    <aside class="notes">
    <p>
    <strong>Time Elapsed:</strong> 0 min.
    </p>
    <p>
    Hi, my name is Hanno.
    I'm from the Netherlands, where I work at Info Support as an IT consultant.
    Besides doing consultancy work, I also teach a few courses.
    Now at Info Support we offer a wide range of courses, which exist mainly to get our junior colleagues up to speed with important concepts or products they'll need for their daily work.
    </p>
    <p>
    One of the courses I teach is called 'Git for Developers'.
    It's a one-day course where we teach the students how to use Git as a developer (none of that GUI stuff of course; command-line For The Win!).
    Besides doing the practical stuff we also discuss the pros and cons of distributed version control systems and how they compare to the earlier VCS's, like CVS and Subversion.
    Now the other day a student came to me after attending the course and said: "Git is great and all that, but what is gonna be the next big thing?"
    </p>
    <p>
    Which was a great question, because I couldn't really answer it.
    I was quite sure distributed version control systems like Git and Mercurial would be around for a while longer, so that's what I told him.
    And he replied: "Surely Git won't be around forever?!"
    Now I really hated the fact that I couldn't tell him more on the subject, so I decided to research the matter a bit further.
    And what started out as finding the answer to a simple question turned into giving a conference talk.
    Which is the one you're attending right now!
    </p>
    <p>
    So, welcome to you all.
    I'm going to assume that you are all more or less like the student I told you about.
    He just couldn't believe that everything in version control land would stay the same for a long period of time.
    And I hope you're also a little bit like me, because you probably also can't stand not being able to know the answer to a question.
    So, let's see if we can find the answer together, shall we?
    </p>
    </aside>
    ---
  • replacement in sections/1-preface.md at line 59
    [2.2037328][2.2037328:2037464]()
    Now, any time if I hear somebody say that [insert-product-name-here] "will probably be around forever", it immediately reminds me of...
    [2.2037328]
    [3.973996]
    So, whenever I hear somebody say that [insert-product-name-here] "will probably be around forever", it immediately reminds me of...
  • replacement in sections/1-preface.md at line 61
    [3.974004][3.974004:974014]()
    ...this.
    [3.974004]
    [3.95656]
    ...this quote.
  • replacement in sections/1-preface.md at line 63
    [3.95657][2.2037465:2037555]()
    If working in software development for over 11 years has taught me anything, it's that...
    [3.95657]
    [3.974101]
    If working in software development for almost 12 years has taught me anything, it's that...
  • replacement in sections/1-preface.md at line 83
    [2.2037868][2.2037868:2037905]()
    Because change is the only constant.
    [2.2037868]
    [2.2037905]
    Because change is the only constant, and has been for a long time.
  • edit in sections/1-preface.md at line 92
    [2.2038144]
    [2.2038144]
    Now if "Change is the only constant" is valid in our industry, then so is "What goes up, must come down".
  • replacement in sections/1-preface.md at line 96
    [2.2038281][2.2038281:2038298]()
    * Bitcoin price;
    [2.2038281]
    [2.2038298]
    * Bitcoin prices;
  • replacement in sections/1-preface.md at line 98
    [2.2038323][2.2038323:2038363]()
    * version control system market shares.
    [2.2038323]
    [2.2038363]
    * and maybe even version control system market shares.
    TODO: overweeg om hier extra plaatjes te gebruiken.
  • edit in sections/1-preface.md at line 107
    [2.2038536]
    [2.2038536]
    Because it was also about predictions.
  • edit in sections/1-preface.md at line 109
    [2.2038632]
    [2.2038632]
    Now in the year I did this talk the hurricane Katrina struck the southern coast of the USA.
    Also in this year a video sharing website called "YouTube" is founded.
    And lastly, in this year cyclist Lance Armstrong won his seventh consecutive Tour de France.
    (although he was 'stripped' of his titles, because of drug allegations)
    So what do you think the year was?
  • replacement in sections/1-preface.md at line 118
    [2.2038652][2.2038652:2038737]()
    TODO: random feitje uit 2005, om het jaartal wat 'dramatischer' te kunnen onthullen.
    [2.2038652]
    [2.2038737]
    ---
  • replacement in sections/1-preface.md at line 120
    [2.2038738][2.2038738:2038742]()
    ---
    [2.2038738]
    [2.2038742]
    <!-- .slide: data-background="img/background/the-browser-wars-2005.png" --->
  • replacement in sections/1-preface.md at line 124
    [2.2038793][2.2038793:2038822]()
    This was fourteen years ago!
    [2.2038793]
    [2.2038822]
    This was fourteen years ago, and it shows.
    It looks RETRO, doesn't it?
    I mean, the obnoxious headers and footers.
    The background gradient.
    The page number at the bottom.
    Fantastic stuff.
    The slide also shows that the Internet Explorer browser family was VERY dominant in 2005.
    Almost 90% of all Internet users used an IE browser.
    In this talk I predicted three things, of which two REALLY HAPPENED IN THE END.
    ---
    ## In ten years time...
  • replacement in sections/1-preface.md at line 140
    [2.2038823][2.2038823:2038846]()
    TODO: add retro slide.
    [2.2038823]
    [2.2038846]
    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.
    note:
    Just the last prediction didn't happen, the other two did!
  • edit in sections/1-preface.md at line 149
    [2.2038852]
    [2.2038852]
    <!-- .slide: data-background="img/background/browser-shares-2007-2018.jpg" data-background-size="contain" data-background-color="white" --->
    [https://www.bbntimes.com/en/global-economy/market-shares-for-browsers-and-platforms](https://www.bbntimes.com/en/global-economy/market-shares-for-browsers-and-platforms) <!-- .element: class="attribution" -->
  • replacement in sections/1-preface.md at line 154
    [2.2038858][2.2038858:2039260]()
    Now 'the browser wars' are a VERY good example of Newton's statement.
    Because in the beginning, there was the Mosaic text-based browser.
    Until it came down and the top browser became Netscape Navigator.
    Until it came down and the top browser became Microsoft Internet Explorer.
    Until it came down and the top browser became Mozilla Firefox.
    Until it came down and the top browser became Google Chrome.
    [2.2038858]
    [2.2039260]
    I didn't count on Google Chrome - a new browser - to take the top spot.
    But see!
    Internet Explorer WAS surpassed within ten years time.
    And Firefox DID surpass IE for a few months in 2016.
    OK, technically that did take 11 years, not 10.
  • replacement in sections/1-preface.md at line 167
    [2.2039394][2.2039394:2039409]()
    TODO: afmaken.
    [2.2039394]
    [2.2039409]
    TODO: samenvoegen met wat hierboven staat.
  • edit in sections/1-preface.md at line 176
    [2.2039710]
    [2.2039710]
    Mosaic was replaced by Netscape, which was replaced by Internet Explorer.
    Which was replaced by Internet Explorer, which was replaced by Mozilla Firefox, which was replaced by Google Chrome.
  • replacement in sections/1-preface.md at line 183
    [2.2039793][2.2039793:2039867]()
    So let's see how these things have happened in the version control world!
    [2.2039793]
    So let's see how these things have happened until now in the version control world!
  • edit in sections/2-git.md at line 1
    [3.11907]
    [3.974383]
    <!-- .slide: data-background="img/background/usb-sticks.jpg" data-background-color="black" data-background-opacity="0.3"-->
  • edit in sections/2-git.md at line 4
    [3.974389]
    [3.974389]
    [https://pxhere.com/en/photo/652221](https://pxhere.com/en/photo/652221) <!-- .element: class="attribution" -->
    note:
    **Time Elapsed:** 10 min.
  • edit in sections/2-git.md at line 10
    [3.974390]
    [3.974390]
    ## Version Control 'By USB Stick'
  • edit in sections/2-git.md at line 13
    [3.974408]
    [3.974408]
    # Some surprising facts on Git
    ---
    * "First Linux, now Git"
    [https://www.infoworld.com/article/2669670/after-controversy--torvalds-begins-work-on--git-.html](https://www.infoworld.com/article/2669670/after-controversy--torvalds-begins-work-on--git-.html) <!-- .element: class="attribution" -->
  • replacement in sections/2-git.md at line 22
    [3.974409][3.974409:974442]()
    ## Why has it become so popular?
    [3.974409]
    [2.2039869]
    note:
    When asked why he called the new software, "git," British slang meaning "a rotten person," he said. "I'm an egotistical bastard, so I name all my projects after myself. First Linux, now git."
    ---
    * WWCVSND?
    [https://twobithistory.org/2018/07/07/cvs.html](https://twobithistory.org/2018/07/07/cvs.html)
    note:
    When Linus Torvalds was developing Git, one of his guiding principles was WWCVSND, or “What Would CVS Not Do.” Take CVS as an example of what not to do; if in doubt, make the exact opposite decision.
    ---
    # Why has Git become so popular?
  • replacement in sections/2-git.md at line 38
    [2.2039870][2.2039870:2039903]()
    note:
    **Time Elapsed:** 10 min.
    [2.2039870]
    [2.2039903]
    note:
    In Stack Overflow’s 2015 developer survey, 69.3% of respondents used Git, almost twice as many as used the second-most-popular version control system, Subversion.1 After 2015, Stack Overflow stopped asking developers about the version control systems they use, perhaps because Git had become so popular that the question was uninteresting.
  • replacement in sections/2-git.md at line 43
    [2.2039909][2.2039909:2039979]()
    <!-- TODO: test deze slide op de resolutie die ze bij VDA hebben. -->
    [2.2039909]
    [2.2039979]
    <!-- TODO: test deze slide op een 16:9-resolutie. -->
  • edit in sections/3-back-to-the-future.md at line 1
    [3.11948]
    [2.2040735]
    <!-- .slide: data-background="img/background/usb-sticks.jpg" data-background-color="black" data-background-opacity="0.3"-->
  • edit in sections/3-back-to-the-future.md at line 4
    [2.2040756]
    [2.2040756]
    [https://pxhere.com/en/photo/652221](https://pxhere.com/en/photo/652221) <!-- .element: class="attribution" -->
  • replacement in sections/3-back-to-the-future.md at line 11
    [2.2040868][2.2040868:2040957]()
    En probeer nog wat meer parallellen te vinden tussen de Browser Wars-presentatie en deze.
    [2.2040868]
    Altijd goed om dan ook al wat keuze te bieden.
    De Pijul-website staat aardig vol met kritiek op Git - handig om inspiratie op te doen.
    Let wel: dit onderdeel kan wat mij betreft als eerste vervallen; mochten we in tijdnood komen.
    ---
  • file addition: 4-new-kids-on-the-block.md (----------)
    [3.11836]
    <!-- .slide: data-background="img/background/usb-sticks.jpg" data-background-color="black" data-background-opacity="0.3"-->
    # New Kids On The Block
    [https://pxhere.com/en/photo/652221](https://pxhere.com/en/photo/652221) <!-- .element: class="attribution" -->
    ---
    * Fossil (2006)
    * Plastic (2006)
    * Veracity (2010)
    * Pijul (2015)
    note:
    **Time Elapsed:** 20 min.
    These four Version Control Systems have been published after the large Distributed Version Control wave in March/April 2005.
  • edit in sections/5-veracity.md at line 1
    [3.12194]
    [3.974482]
    <!-- .slide: data-background="img/background/usb-sticks.jpg" data-background-color="black" data-background-opacity="0.3"-->
  • edit in sections/5-veracity.md at line 4
    [3.974493]
    [3.974493]
    [https://pxhere.com/en/photo/652221](https://pxhere.com/en/photo/652221) <!-- .element: class="attribution" -->
  • edit in sections/5-veracity.md at line 9
    [2.2041046]
    ---
  • edit in sections/6-pijul.md at line 1
    [3.12149]
    [2.2041048]
    <!-- .slide: data-background="img/background/usb-sticks.jpg" data-background-color="black" data-background-opacity="0.3"-->
  • edit in sections/6-pijul.md at line 5
    [2.2041057]
    [2.2041057]
    [https://pxhere.com/en/photo/652221](https://pxhere.com/en/photo/652221) <!-- .element: class="attribution" -->
  • replacement in sections/6-pijul.md at line 8
    [2.2041064][2.2041064:2041089]()
    **Time Elapsed:** 26 min.
    [2.2041064]
    **Time Elapsed:** 26 min.
    ---
    <!-- .slide: data-background="img/background/pijul.jpg" data-background-color="black" data-background-opacity="0.8"-->
    ## pi · jul <!-- .element: class="stroke" -->
    <blockquote class="explanation">
    or <em>crotophaga sulcirostris</em>, a bird known to do collaborative nest building.
    </blockquote>
    [https://commons.wikimedia.org/wiki/File:Museo_de_la_Naturaleza_de_Cantabria_(208).jpg](https://commons.wikimedia.org/wiki/File:Museo_de_la_Naturaleza_de_Cantabria_(208).jpg) <!-- .element: class="attribution" -->
  • edit in sections/7-fossil.md at line 1
    [3.12102]
    [2.2041091]
    <!-- .slide: data-background="img/background/usb-sticks.jpg" data-background-color="black" data-background-opacity="0.3"-->
  • edit in sections/7-fossil.md at line 5
    [2.2041101]
    [2.2041101]
    [https://pxhere.com/en/photo/652221](https://pxhere.com/en/photo/652221) <!-- .element: class="attribution" -->
  • replacement in sections/7-fossil.md at line 8
    [2.2041108][2.2041108:2041133]()
    **Time Elapsed:** 36 min.
    [2.2041108]
    **Time Elapsed:** 36 min.
    ---
  • edit in sections/8-predictions.md at line 1
    [3.12245]
    [3.12246]
    <!-- .slide: data-background="img/background/usb-sticks.jpg" data-background-color="black" data-background-opacity="0.3"-->
  • edit in sections/8-predictions.md at line 4
    [3.12260]
    [2.2041135]
    [https://pxhere.com/en/photo/652221](https://pxhere.com/en/photo/652221) <!-- .element: class="attribution" -->
  • replacement in sections/8-predictions.md at line 8
    [2.2041143][2.2041143:2041168]()
    **Time Elapsed:** 42 min.
    [2.2041143]
    **Time Elapsed:** 42 min.
    ---