LOTS of progress

[?]

Jun 4, 2019, 1:07 PM

5LKTNB6ODFPX45VJBT5H34WZFJBVWWYSCS2HRMKKJPPO3M2M75NAC

Dependencies

[2] QEKU5M3O Preface
[3] WYULWETJ Reorganize
[4] ARAFRHKU Create the outline of the talk
[5] UH3YXOLF Start the slide deck
[6] PMBAMPBI Finish the title slide
[7] 4AZS4L6B Add chapters
[8] NYFLNSVV Add some contents
[9] JSFDZRYK Add the famous Bill Gates quote
[10] S55XICBM Fix speaker notes
[11] KPHR32IR Progress
[*] 6IUUMFCC Initial commit

Change contents

edit in .gitignore at line 2

[3.12]

.vscode
file addition: bitkeeper-goes-commercial.png (----------)

[3.1221]
file addition: chess-champion.jpg (----------)

[3.1221]
file addition: crystal-ball.jpg (----------)

[3.1221]
file addition: implementation-decision.jpg (----------)

[3.1221]
file addition: problem-encountered.jpg (----------)

[3.1221]
edit in index.html at line 89

[3.29504539]

[3.29504539]

<section>
<h2>Further reading</h2>
<ul>

<li>"Beyond Git" (by Paweł Świątkowski)
<br/><small><a href="http://katafrakt.me/2017/05/27/beyond-git/">http://katafrakt.me/2017/05/27/beyond-git/</a></small>
</li>
<li>"Merging, patches and Pijul" (by Joe Neeman)
<br/><small><a href="https://jneem.github.io/pijul/">https://jneem.github.io/pijul/</a></small>
</li>
</ul>
</section>
replacement in index.html at line 116

[3.29505185]→[3.29505185:29505255](∅→∅)

<td style="vertical-align: middle;"><a href="#">TODO</a></td>

[3.29505185]

[3.29505255]

<td style="vertical-align: middle;"><a href="#">FINAL:</a></td>
file addition: misc (d--r------)

[13.2]
file addition: MyRandom.java (----------)

[0.4217140]

package misc;

import java.util.Random;

public class MyRandom {
static Random random = new Random();

public static void main(String... args) {
System.out.println(randomClass());
}

private static int randomDice() {
// Chosen by fair dice roll; guaranteed to be random!
return 4;
}

private static int randomMath() {
return (int) (Math.random() * 6);
}

private static int randomClass() {
return random.nextInt(7);
}
}
replacement in sections/0-welcome.md at line 21

[3.135]→[3.135:404](∅→∅)

Now, everything you've heard about my country is probably true.
When we go to work in the morning, we wear our wooden clogs.
We never drive cars to work; no, we ride our bikes.
Or we ice-skate in the winter.
On our daily commute we easily pass ten different windmills.

[3.135]

[3.1514]

Now, everything you've heard about my country is probably true:
replacement in sections/0-welcome.md at line 23

[3.1515]→[2.118434:118507](∅→∅),[2.118507]→[3.456:521](∅→∅),[3.456]→[3.456:521](∅→∅)

And when it's lunch time, the office cafeteria serves stroopwafels ONLY.
I actually brought some with me, because we have plenty of them.

[3.1515]

[3.521]

* Before we go to work in the morning, we put on our wooden clogs.
* We never drive cars to work; no, we ride our bikes.
* Or if it's winter, we ice-skate.
* On our daily commute we easily pass ten different windmills.
* And when it's lunch time, the office cafeteria serves stroopwafels ONLY.

I actually brought some with me, because in my country we have plenty of them.
replacement in sections/0-welcome.md at line 32

[3.600]→[2.118508:118597](∅→∅)

I didn't say WHEN you get bored, mind you, I said IF you get bored!
There's a difference!

[3.600]

I didn't say WHEN you get bored, mind you!
I said IF you get bored!
There's a difference!
replacement in sections/1-preface.md at line 5

[3.2018]→[3.2018:2130](∅→∅)

[https://pxhere.com/en/photo/652221](https://pxhere.com/en/photo/652221) 

[3.2018]

[3.2130]

<https://pxhere.com/en/photo/652221> 
replacement in sections/1-preface.md at line 21

[2.118917]→[2.118917:119089](∅→∅)

[http://blog.plasticscm.com/2010/11/version-control-timeline.html](http://blog.plasticscm.com/2010/11/version-control-timeline.html) 

[2.118917]

[2.119089]

<http://blog.plasticscm.com/2010/11/version-control-timeline.html> 
replacement in sections/1-preface.md at line 25

[2.119139]→[2.119139:119385](∅→∅)

And it shows which version control systems have emerged in the past and when they became available.
It tries to put the publication date of each version control system in perspective by comparing them to the most modern phone known at that time.

[2.119139]

[2.119385]

It displays which version control systems have emerged until now, and when they became available.
It also tries to put the publication date of each version control system in perspective by comparing them to the most modern phone known at that time.
edit in sections/1-preface.md at line 30

[2.119501]

[2.119501]

Both are obviously **ancient**.
replacement in sections/1-preface.md at line 32

[2.119502]→[2.119502:119762](∅→∅)

Now, when I talk about this slide during the Git course, I tend to focus on the events of the year 2005.
Because to me, 2005 REALLY stands out in version control history.
I mean, FIVE new version control systems were published in that year.
In a single year.

[2.119502]

[2.119762]

Now, when I talk about this slide during the Git course, I tend to focus on the events of the year 2005. (*point*)
Because to me, 2005 **really** stands out in version control history.
I mean, **five** new version control systems were published in that year.
In a **single** year.
replacement in sections/1-preface.md at line 37

[2.119763]→[2.119763:119987](∅→∅)

To put this number in context, before 2005, it had taken NINE years for five version control systems to emerge.
Starting with VSS in 1994, and ending with BitKeeper in 2003.
And in 2005, it all happened within a few months.

[2.119763]

[2.119987]

To put things in perspective, before 2005, it had taken **nine** years for five version control systems to emerge.
(Starting with VSS in 1994, and ending with BitKeeper in 2003.)
And in 2005, it all happened within a few months!
replacement in sections/1-preface.md at line 41

[2.119988]→[2.119988:120029](∅→∅)

So, who knows why it happened like this?

[2.119988]

[2.120029]

So, does anyone know why things happened like this?

---


replacement in sections/1-preface.md at line 47

[2.120030]→[2.120030:120035](∅→∅)

---

[2.120030]

[2.120035]

<http://web.archive.org/web/20050408062838/http://www.bitkeeper.com/press/2005-04-05.html> 
replacement in sections/1-preface.md at line 50

[2.120042]→[2.120042:120067](∅→∅)

The answer is BitKeeper!

[2.120042]

[2.120067]

Well, BitKeeper happened.
They went from open-source to proprietary just like **that**.
The open-source world - Linus Torvalds in front - was not amused.
He had been using BitKeeper for the Linux kernel, but was now in need of a new system.

And becasue BitKeeper was the only distributed version control system at the time, which was now no longer freely available, a lot of similar products were developed in a short amount of time.
Including Mr. Torvalds' own rendition of distributed version control, which later became Git.
replacement in sections/1-preface.md at line 62

[2.120214]→[2.120214:120386](∅→∅)

[http://blog.plasticscm.com/2010/11/version-control-timeline.html](http://blog.plasticscm.com/2010/11/version-control-timeline.html) 

[2.120214]

[2.120386]

<http://blog.plasticscm.com/2010/11/version-control-timeline.html> 
replacement in sections/1-preface.md at line 66

[2.120524]→[2.120524:120781](∅→∅)

In fact, at the end of the course day a student came to me with a question.
And his question proved that he had noticed an entirely different thing than I had noticed.
Moreover, his 'discovery' - if you will - proved to be a LOT more interesting than mine.

[2.120524]

[2.120781]

In fact, at the end of one particular course day a student came to me with a question.
And his question proved that he had noticed an **entirely** different thing than I had noticed.
Moreover, his 'discovery' - if you will - proved to be a **lot** more interesting than mine.
replacement in sections/1-preface.md at line 70

[2.120782]→[2.120782:120881](∅→∅)

He came over to me and said: "Git is great and all that, but what is gonna be the next big thing?"

[2.120782]

[2.120881]

He came up to me and said: "Git is great and all that, but what's gonna be the **next** big thing?"
replacement in sections/1-preface.md at line 72

[2.121007]→[2.121007:121058](∅→∅)

But to be honest, I didn't really know the answer.

[2.121007]

[2.121058]

But this wasn't a good answer, really.
Because **I didn't know** what was gonna be the next big thing.
replacement in sections/1-preface.md at line 77

[2.121150]→[2.121150:121418](∅→∅)

Because if you look at the chart and you look beyond what you've already seen (the year 2005), then it becomes painfully obvious
In version control land, nothing seems to have happened after 2006.
This is one of those things that, once you see it, you can't UNSEE it.

[2.121150]

[2.121418]

Because if you look at the chart and you look beyond what you've already seen (the year 2005), then it becomes painfully obvious...
That in version control land, nothing seems to have happened after 2006.
This is one of those things that, once you see it, you can't **unsee** it.
replacement in sections/1-preface.md at line 81

[2.121419]→[2.121419:121423](∅→∅)

---

[2.121419]

[2.121423]

FIXME: het volgende verhaaltje vloeiender, natuurlijker laten lopen.
En het kan ook best wat korter.
replacement in sections/1-preface.md at line 84

[2.121424]→[2.121424:121430](∅→∅),[2.121430]→[3.3193:3420](∅→∅),[3.3193]→[3.3193:3420](∅→∅)

note:
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.

[2.121424]

[3.3420]

Now I kind of felt bad that I had dodged my student's question a bit by telling him distributed version control was the present **and** the future.
I had effectively told him that "Git will probably be around forever", even if I didn't phrase it exactly like that.
And 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 an investigation.
And the investigation turned into a conference talk.
replacement in sections/1-preface.md at line 91

[3.3466]→[3.3466:3490](∅→∅)

So, welcome to you all.

[3.3466]

[3.3490]

So, welcome to you all! (*open arms*)
edit in sections/1-preface.md at line 108

[3.973894]→[3.2037302:2037328](∅→∅)

**Time Elapsed:** 3 min.
replacement in sections/1-preface.md at line 132

[3.2037868]→[3.7966950:7967017](∅→∅)

Because change is the only constant, and has been for a long time.

[3.2037868]

[3.2037905]

Because in our industry, change is the only constant
And it has been like that for a long time.
replacement in sections/1-preface.md at line 150

[3.7967200]→[3.7967200:7967252](∅→∅)

TODO: overweeg om hier extra plaatjes te gebruiken.

[3.7967200]

[3.2]

FINAL: wanneer voorbereidingstijd over, gebruik hier dan meer slides met plaatjes van de voorbeelden.
replacement in sections/1-preface.md at line 152

[3.3]→[3.3:211](∅→∅)

Throughout this talk, we'll discover several ideas that I will use as input variables for the prediction at the end of the talk. The idea of "What's goes up..." is actually the first variable that we'll use.

[3.3]

[3.211]

---
replacement in sections/1-preface.md at line 154

[3.212]→[3.212:346](∅→∅)

TODO: maak een plaatje voor 'Prediction variable', dat bij elk nieuw geïntroduceerd idee als een fragment op de slide gegooid wordt.

[3.212]



## What goes up must come down.

<blockquote class="explanation">
<code>prediction variable</code>
</blockquote>

<https://www.pexels.com/photo/photo-displays-person-holding-ball-with-reflection-of-horizon-940880> 

note:
FIXME: leg het idee van 'prediction variable' wat beter uit.

Throughout this talk, we will discover several ideas that I will use as input variables for the final prediction.
At the moment we're far from it.
But we'll get there in the end, by identifying more prediction variables.
The idea of "What's goes up..." is actually the first variable that we'll use.
Because...? FIXME
replacement in sections/2-git.md at line 8

[3.7969587]→[3.7969587:7969613](∅→∅)

**Time Elapsed:** 10 min.

[3.7969587]

[2.121731]

**Time Elapsed:** 11 min.

So, it's great that now we know 'what goes up, must come down'.
But it's not enough to make a sound prediction.

FIXME: regel wat meer aansluiting met vorige onderwerp.
edit in sections/2-git.md at line 17

[2.122006]

[2.122006]

---

## Features of Git

* Distributed
* Free & open-source
* Fast
* Optimized for branching

note:
FIXME: leg wat verder uit waarom deze features - of liever gezegd: deze combinatie van features - baanbrekend waren in die tijd.

* **Distributed**
* Like BitKeeper. Commit often, push once.
* **Free & open-source**
* **Unlike** BitKeeper
* **Fast**
* Linus said "everything you ever do on a daily basis should take less than a second".
* **Optimized for branching**
* In the Subversion age, developers 'were afraid of branching', so they didn't do it!
* Which was a very bad thing in a time where Continuous Delivery did not yet exist like we know it today.

---

## Some surprising facts on Git

> "First Linux, now Git"

<https://www.infoworld.com/article/2669670/after-controversy--torvalds-begins-work-on--git-.html> 

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?

<blockquote class="explanation">
If in doubt, make the exact opposite decision.
</blockquote>

<https://pxhere.com/en/photo/704019> 

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.

---



## Killer features.

<blockquote class="explanation">
<code>prediction variable</code>
</blockquote>
edit in sections/2-git.md at line 76

[2.122007]

[2.122007]

<https://www.pexels.com/photo/photo-displays-person-holding-ball-with-reflection-of-horizon-940880> 

note:
FIXME: Introduceer deze variable wat beter.

Killer features are new features (that have never been seen) or different features (where a similar feature has been implemented in a radically different way, to distinguish it from the competitors).

* Surprising name
* Opposite of CVS in many aspects
* ...
edit in sections/2-git.md at line 95

[2.122408]

[2.122408]

There's a lot of significant information in this chart: (*point*)
* Git's growth increased rapidly after it was supported by Github (2008), Bitbucket (2012) and Gitlab (2013).
* Subversion's popularity peaked in 2009
* 4 years after Git and Mercurial were released;
* also: after Github was launched.
* Mercurial started declining **only** after Bitbucket added Git support.
* The numbers we see here are based on *relative search volume*. It is not the **actual** usage of the products. Version control system popularity is actually quite hard to measure! (more on this later)

FIXME: meer verhaaltje hier.

---

## Influence of source code hosting on popularity

<https://en.wikipedia.org/wiki/Comparison_of_source-code-hosting_facilities#Version_control_systems>
edit in sections/2-git.md at line 113

[3.664]

[3.974389]


replacement in sections/2-git.md at line 116

[3.974390]→[3.7969614:7969648](∅→∅)

## Version Control 'By USB Stick'

[3.974390]

[3.665]

## Hosting platform support.

<blockquote class="explanation">
<code>prediction variable</code>
</blockquote>

<https://www.pexels.com/photo/photo-displays-person-holding-ball-with-reflection-of-horizon-940880> 

note:
FIXME: Introduceer deze variable.
replacement in sections/2-git.md at line 129

[3.7969649]→[3.974390:974408](∅→∅),[3.974390]→[3.974390:974408](∅→∅)

## Basic features

[3.7969649]

[3.671]



[https://blog.gitprime.com/git-didnt-beat-svn-github-did/](https://blog.gitprime.com/git-didnt-beat-svn-github-did/) 

note:
Let's return to this chart one more time and allow me to address a final point:
edit in sections/2-git.md at line 136

[3.672]

[3.672]

* The numbers we see here are based on *relative search volume*. It is not the **actual** usage of the products. Version control system popularity is actually quite hard to measure! (more on this later)
replacement in sections/2-git.md at line 140

[3.7969651]→[3.7969651:7969682](∅→∅)

# Some surprising facts on Git

[3.7969651]

[3.7969682]

## Measuring Version Control System Popularity

* This is very hard.

note:
FIXME: dit verhaaltje kan beter.
En schrijf wat naar het Google Trends-voorbeeld toe.

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. After 2015, Stack Overflow stopped asking developers about the version control systems they use, perhaps because Git had become so popular that the question had become uninteresting.
replacement in sections/2-git.md at line 152

[3.7969688]→[3.677:702](∅→∅)

> "First Linux, now Git"

[3.7969688]

[3.7969713]

<https://trends.google.nl/trends/explore?date=today%205-y&q=git,subversion,mercurial> 

---


replacement in sections/2-git.md at line 158

[3.7969714]→[3.7969714:7969949](∅→∅)

[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) 

[3.7969714]

[3.974408]

<https://www.globalapptesting.com/blog/picking-apart-stackoverflow-what-bugs-developers-the-most> 
replacement in sections/2-git.md at line 161

[3.7969956]→[3.7969956:7970148](∅→∅)

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."

[3.7969956]

[3.7970148]

FIXME: leg uit waarom dit niet de metriek is die je wilt. :-)

Wat betekent het als er veel vragen worden gesteld?
* veel gebruikers van de taal?
* veel onervaren gebruikers?
* de taal is moeilijk te leren / niet intuïtief?
replacement in sections/2-git.md at line 170

[3.7970154]→[3.7970154:7970165](∅→∅)

* WWCVSND?

[3.7970154]

[3.7970165]


replacement in sections/2-git.md at line 172

[3.7970166]→[3.7970166:7970261](∅→∅)

[https://twobithistory.org/2018/07/07/cvs.html](https://twobithistory.org/2018/07/07/cvs.html)

[3.7970166]

[3.7970261]

<https://bingeprints.com/products/there-are-two-types-of-people-those-who-can-extrapolate-from-incomplete-data-mug-funny-statistics-math-coffee-cup-1> 
replacement in sections/2-git.md at line 175

[3.7970268]→[3.7970268:7970472](∅→∅)

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.

[3.7970268]

[3.7970472]

Of course, this shouldn't stop us from making a first prediction!
After all, we all know there are only two types of people in the world.
1. Those who can extrapolate from incomplete data.

FIXME: meer verhaaltje.
edit in sections/2-git.md at line 182

[3.7970477]

[3.7970477]

## First Prediction
replacement in sections/2-git.md at line 185

[3.7970478]→[3.7970478:7970511](∅→∅)

# Why has Git become so popular?

[3.7970478]

[3.2039869]

<table>
<thead>
<tr>
<th/>
<th>2009</th>
<th class="fragment" data-fragment-index="1">2019</th>
<th class="fragment" data-fragment-index="2">2029</th>
</tr>
</thead>
<tbody>
<tr>
<th align="right">Subversion</th>
<td align="right">45%</td>
<td align="right" class="fragment" data-fragment-index="1">8%</td>
<td align="right" class="fragment" data-fragment-index="2">4%</td>
</tr>
<tr>
<th align="right">Git</th>
<td align="right">20%</td>
<td align="right" class="fragment" data-fragment-index="1">73%</td>
<td align="right" class="fragment" data-fragment-index="2">80%</td>
</tr>
<tr>
<th align="right">Mercurial</th>
<td align="right">17%</td>
<td align="right" class="fragment" data-fragment-index="1">12%</td>
<td align="right" class="fragment" data-fragment-index="2">9%</td>
</tr>
<tr>
<th align="right">TFS</th>
<td align="right">11%</td>
<td align="right" class="fragment" data-fragment-index="1">7%</td>
<td align="right" class="fragment" data-fragment-index="2">7%</td>
</tr>
<tr>
<th align="right">CVS</th>
<td align="right">7%</td>
<td align="right" class="fragment" data-fragment-index="1"><1%</td>
<td align="right" class="fragment" data-fragment-index="2"><1%</td>
</tr>
</tbody>
</table>
replacement in sections/2-git.md at line 229

[3.7970518]→[3.348:697](∅→∅)

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 had become uninteresting.

[3.7970518]

[3.2039903]

FIXME: leg deze voorspellingen uit aan de hand van de populariteitsgrafiek.

FIXME: vind een manier om hier snel te kunnen wisselen naar de populariteitsgrafiek, *zonder dat de fragment state verandert*.
Een optie: open het plaatje als voorbereiding en zet deze direct op het tweede scherm neer.
Dan moet ik die voorbereiding wel ergens vastleggen (bij voorkeur op de titelslide in de notities).
replacement in sections/2-git.md at line 237

[3.2039909]→[3.703:750](∅→∅)

## Measuring Version Control System Popularity

[3.2039909]

[3.744]


replacement in sections/2-git.md at line 239

[3.745]→[3.745:863](∅→∅),[3.863]→[3.7970861:7970915](∅→∅),[3.2039909]→[3.7970861:7970915](∅→∅)




[3.745]

[3.755]

## One problem though.

<blockquote class="explanation">
We haven't included <em>any</em> new products!
</blockquote>

<https://www.pexels.com/photo/man-in-black-shirt-and-gray-denim-pants-sitting-on-gray-padded-bench-1134204> 

note:
This 'first prediction' is based entirely on existing products.
But a lot can happen in ten years!
What if a brand-new, feature-packed version control system appears and takes the market by storm?
replacement in sections/2-git.md at line 254

[3.2040278]→[3.2040278:2040392](∅→∅)



[3.2040278]

[3.2040392]



## Version Control 'By USB Stick'

<https://pxhere.com/en/photo/652221> 
replacement in sections/2-git.md at line 260

[3.2040393]→[3.2040393:2040733](∅→∅)

[https://bingeprints.com/products/there-are-two-types-of-people-those-who-can-extrapolate-from-incomplete-data-mug-funny-statistics-math-coffee-cup-1](https://bingeprints.com/products/there-are-two-types-of-people-those-who-can-extrapolate-from-incomplete-data-mug-funny-statistics-math-coffee-cup-1) 

[3.2040393]

note:
The next big thing could be 'Version Control By USB Stick', for example.
Haven't you been wondering why some of my slides have had USB sticks in the background?
It's a great story.

FIXME: dit verhaaltje uitwerken.

I can assure you that we don't need to worry about 'Version Control By USB Stick'.
It will not get popular, for obvious reasons.
replacement in sections/3-the-browser-wars.md at line 1

[3.3908]→[3.3909:4033](∅→∅)



[3.3908]

[3.4033]


replacement in sections/3-the-browser-wars.md at line 5

[3.4054]→[3.4054:4166](∅→∅)

[https://pxhere.com/en/photo/652221](https://pxhere.com/en/photo/652221) 

[3.4054]

[3.4166]

<https://pxhere.com/en/photo/652221> 
replacement in sections/3-the-browser-wars.md at line 8

[3.4173]→[3.4173:4199](∅→∅)

**Time Elapsed:** 15 min.

[3.4173]

[3.4199]

**Time Elapsed:** 25 min.
replacement in sections/3-the-browser-wars.md at line 10

[3.4200]→[3.4200:4411](∅→∅)

---

note:
Speaking of browser market shares, when I was in college I did a talk on 'the browser wars'.
The talk was actually quite similar to the one I'm doing right now.
Because it was also about predictions.

[3.4200]

[3.4411]

This is not the first time I'm speaking on popularity of a software product.
When I was in college I did a talk on 'the browser wars'.
edit in sections/3-the-browser-wars.md at line 13

[3.4507]→[3.4507:4891](∅→∅)

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?

The year was 2005.
replacement in sections/3-the-browser-wars.md at line 20

[3.5025]→[3.5025:5096](∅→∅)

This was fourteen years ago, and it shows.
It looks RETRO, doesn't it?

[3.5025]

[3.5096]

Now notice the date, in the bottom left corner.
This slide deck was created fourteen years ago, and it shows.
It's a RETRO slide deck.
edit in sections/3-the-browser-wars.md at line 28

[3.5213]

[3.5213]

If you would just wait for fifteen years, it would be fashionable again.
replacement in sections/3-the-browser-wars.md at line 32

[3.5357]→[3.5357:5437](∅→∅)

In this talk I predicted three things, of which two REALLY HAPPENED IN THE END.

[3.5357]

[3.5437]

Now in this talk I predicted three things, of which two **actually really happened**.
These were my predictions:
replacement in sections/3-the-browser-wars.md at line 61

[3.6315]→[3.6315:6346](∅→∅)

## Key question: was I right?

[3.6315]

[3.6346]



<https://tenor.com/view/youright-right-point-gif-9467383> 
replacement in sections/3-the-browser-wars.md at line 66

[3.6353]→[3.6353:6486](∅→∅)

So, was I right with the browser prediction?
What *was* the most popular browser in 2015?
TODO: samenvoegen met wat hierboven staat.

[3.6353]

[3.6486]

Still, I was right!
Sort of.
I correctly predicted that Internet Explorer would be surpassed by a new browser.
edit in sections/3-the-browser-wars.md at line 71

[3.6491]

[3.6491]



## The disadvantage of the dominant product

<blockquote class="explanation">
You will get a lot of attention.
</blockquote>

<https://www.pexels.com/photo/battle-black-blur-board-game-260024> 
replacement in sections/3-the-browser-wars.md at line 83

[3.6498]→[3.6498:6589](∅→∅)

Now who in their right mind would dare to claim that Google Chrome will be around forever?

[3.6498]

[3.6589]

Now I was quite confident this would happen, because of a mechanism I like to call:
"The disadvantage of the dominant product"

FIXME: leg dit mechanisme beter uit. Wat er zeker in moet voorkomen:
* een dominant product trekt meer aandacht, zowel positief als negatief:
* vatbaarder voor maliciousness - zie virussen op Windows vs. Linux
* meer mensen kennen je product en kunnen in theorie iets nieuws verzinnen dat je product nog niet heeft.

---



## The disadvantage of the dominant product

<blockquote class="explanation">
<code>prediction variable</code>
</blockquote>

<https://www.pexels.com/photo/photo-displays-person-holding-ball-with-reflection-of-horizon-940880> 

note:
FIXME: Introduceer deze variable. Voeg waar mogelijk samen met het verhaal hieronder.

Because who in their right mind would dare to claim that Google Chrome will be around forever?
replacement in sections/3-the-browser-wars.md at line 114

[3.7050]→[3.7050:7054](∅→∅)

---

[3.7050]

[3.7054]

FIXME: bedenk een verbindende zin naar het volgende onderwerp.
En hopelijk iets beters dan wat er nu staat.
edit in sections/3-the-browser-wars.md at line 117

[3.7055]→[3.7055:7061](∅→∅)

note:
replacement in sections/4-four-new-kids-on-the-block.md at line 5

[3.7971546]→[3.7971546:7971659](∅→∅)

[https://pxhere.com/en/photo/652221](https://pxhere.com/en/photo/652221) 

[3.7971546]

[3.7971659]

<https://pxhere.com/en/photo/652221> 

note:
**Time Elapsed:** 30 min.
replacement in sections/4-four-new-kids-on-the-block.md at line 18

[3.7971739]→[3.7971739:7971765](∅→∅)

**Time Elapsed:** 20 min.

[3.7971739]

[3.7971765]

These four Version Control Systems have been published after the large Distributed Version Control wave in March/April 2005.

TODO: neem hier wat inhoud uit https://www.plasticscm.com/documents/version-control-history/version-control-history-poster-A3.pdf in op.

FIXME: wat meer verhaaltje.

---

# Plastic



---
replacement in sections/4-four-new-kids-on-the-block.md at line 32

[3.7971766]→[3.7971766:7971892](∅→∅)

These four Version Control Systems have been published after the large Distributed Version Control wave in March/April 2005.

[3.7971766]

[3.7283]

# Veracity
replacement in sections/4-four-new-kids-on-the-block.md at line 34

[3.7284]→[3.7284:7416](∅→∅)

TODO: neem hier inhoud uit https://www.plasticscm.com/documents/version-control-history/version-control-history-poster-A3.pdf in op.

[3.7284]



note:
TODO: opnemen:
* Development status: web site appears unmaintained; latest release March 25, 2013
* http://veracity-scm.com/compare/
* onveracity.com (offline :()
replacement in sections/5-fossil.md at line 5

[3.2041101]→[3.7973115:7973228](∅→∅)

[https://pxhere.com/en/photo/652221](https://pxhere.com/en/photo/652221) 

[3.2041101]

[3.7973228]

<https://pxhere.com/en/photo/652221> 
replacement in sections/5-fossil.md at line 8

[3.2041108]→[3.7454:7479](∅→∅)

**Time Elapsed:** x min.

[3.2041108]

[3.7973256]

**Time Elapsed:** 35 min.

FIXME: link opnemen in slides:
* https://www.fossil-scm.org/index.html/dir?ci=tip

---

## Features that Fossil promises

* TODO
* **feature** elaboration

---

## Quick facts

* TODO

---



---

## Quick demo


* Resolving conflicts

note:
TODO: demo voorbereiden

Inhoud van de demo:
* Schrijf een klasse die een random nummer genereert.
* Eerste implementatie: gooi een dobbelsteen.
* Tweede implementatie: (int) Math.random() * 6
* deze implementatie moet een conflict veroorzaken.
replacement in sections/5-fossil.md at line 51

[3.7973262]→[3.1747:1877](∅→∅)

[https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki](https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki)

[3.7973262]

<https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki>
replacement in sections/6-pijul.md at line 5

[3.2041057]→[3.7972320:7972433](∅→∅)

[https://pxhere.com/en/photo/652221](https://pxhere.com/en/photo/652221) 

[3.2041057]

[3.7972433]

<https://pxhere.com/en/photo/652221> 
replacement in sections/6-pijul.md at line 8

[3.2041064]→[3.7972435:7972461](∅→∅)

**Time Elapsed:** 26 min.

[3.2041064]

[3.7972461]

**Time Elapsed:** 42 min.
replacement in sections/6-pijul.md at line 19

[3.7972771]→[3.7972771:7972985](∅→∅)

[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) 

[3.7972771]

[3.865]

<https://commons.wikimedia.org/wiki/File:Museo_de_la_Naturaleza_de_Cantabria_(208).jpg> 
edit in sections/6-pijul.md at line 22

[3.872]

[3.872]

FIXME: link over Pijul toevoegen:
* https://www.pijul.com/
edit in sections/6-pijul.md at line 25

[3.873]→[3.873:874](∅→∅)
replacement in sections/6-pijul.md at line 27

[3.879]→[3.879:911](∅→∅)

## Features That Pijul Promises

[3.879]

[3.911]

## Features that Pijul promises
replacement in sections/6-pijul.md at line 35

[3.1082]→[3.1082:1097](∅→∅)

## Quick Facts

[3.1082]

[3.1097]

## Quick facts
edit in sections/6-pijul.md at line 51

[3.1427]

[3.1427]


replacement in sections/6-pijul.md at line 63

[3.1528]→[3.1528:1561](∅→∅)

* (but maybe we don't need them)

[3.1528]

[3.1561]

* (but maybe we don't need them)
* Resolving Conflicts
edit in sections/6-pijul.md at line 69

[3.1593]

[3.1593]

Inhoud van de demo:
* Schrijf een klasse die een random nummer genereert.
* Eerste implementatie: gooi een dobbelsteen.
* Tweede implementatie: (int) Math.random() * 6
* deze implementatie moet een conflict veroorzaken.
* Derde implementatie: java.util.Random.nextInt(7).
* deze implementatie moet een conflict veroorzaken.

Zie `misc/MyRandom.java` voor als je de details vergeet.
replacement in sections/6-pijul.md at line 83

[3.7972987]→[3.1622:1719](∅→∅)

[https://nest.pijul.com/tae/pijul-for-git-users](https://nest.pijul.com/tae/pijul-for-git-users)

[3.7972987]

<https://nest.pijul.com/tae/pijul-for-git-users>
replacement in sections/7-predictions.md at line 5

[3.7973391]→[3.7973391:7973504](∅→∅)

[https://pxhere.com/en/photo/652221](https://pxhere.com/en/photo/652221) 

[3.7973391]

[3.2041135]

<https://pxhere.com/en/photo/652221> 
replacement in sections/7-predictions.md at line 8

[3.2041143]→[3.7973505:7973531](∅→∅)

**Time Elapsed:** 42 min.

[3.2041143]

[3.7973531]

**Time Elapsed:** 49 min.
edit in sections/7-predictions.md at line 13

[3.1904]

[3.1904]


replacement in sections/7-predictions.md at line 17

[3.1937]→[3.1937:2061](∅→∅)

* Killer features
* Hosting platform support
* Bundled with operating system
* The disadvantage of the most popular product

[3.1937]

[3.2061]

* Killer features.
* Hosting platform support.
* The disadvantage of the dominant product.
edit in sections/7-predictions.md at line 21

[3.2062]→[3.2062:2063](∅→∅)
edit in sections/7-predictions.md at line 24

[3.2116]

[3.2116]

* **Hosting platform support**
TODO: gebruik https://en.wikipedia.org/wiki/Comparison_of_source-code-hosting_facilities#Version_control_systems voor een evt. overzicht op een slide.
* FIXME: afmaken
replacement in sections/7-predictions.md at line 28

[3.2117]→[3.2117:2120](∅→∅)

---

[3.2117]

---

## The scores



---

## Prediction matrix 2.0



<table>
<thead>
<tr>
<th/>
<th>2009</th>
<th class="fragment" data-fragment-index="1">2019</th>
<th class="fragment" data-fragment-index="2">2029</th>
</tr>
</thead>
<tbody>
<tr>
<th align="right">Subversion</th>
<td align="right">45%</td>
<td align="right" class="fragment" data-fragment-index="1">8%</td>
<td align="right" class="fragment" data-fragment-index="2">4%</td>
</tr>
<tr>
<th align="right">Git</th>
<td align="right">20%</td>
<td align="right" class="fragment" data-fragment-index="1">73%</td>
<td align="right" class="fragment" data-fragment-index="2">80%</td>
</tr>
<tr>
<th align="right">Mercurial</th>
<td align="right">17%</td>
<td align="right" class="fragment" data-fragment-index="1">12%</td>
<td align="right" class="fragment" data-fragment-index="2">9%</td>
</tr>
<tr>
<th align="right">TFS</th>
<td align="right">11%</td>
<td align="right" class="fragment" data-fragment-index="1">7%</td>
<td align="right" class="fragment" data-fragment-index="2">7%</td>
</tr>
<tr>
<th align="right">CVS</th>
<td align="right">7%</td>
<td align="right" class="fragment" data-fragment-index="1"><1%</td>
<td align="right" class="fragment" data-fragment-index="2"><1%</td>
</tr>
</tbody>
</table>

---

## Prediction chart



note:
FIXME: schrijf hier een conclusie die men kan onthouden.
file addition: video (d--r------)

[13.2]
file addition: i-was-right.mp4 (----------)

[0.4239636]
file addition: programming-language-popularity-stack-overflow.mp4 (----------)

[0.4239636]