The slide deck for my conference talk "Entering the Fourth Dimension of OCR with Tesseract".

The slide deck for my conference talk "Will Git Be Around Forever? A List of Possible Successors".

* UtrechtJUG 2021
* JCON 2021

        return (int) (Math.random() * 6);

        return 1 + (int) (Math.random() * 6);

        return random.nextInt(7);

        return 1 + random.nextInt(6);
    }
    private static int randomThreadLocalRandom() {
        return ThreadLocalRandom.current().nextInt(1, 7);

    <em>"640K ought to be enough for anybody."</em>

    <em>"640K ought to be enough for anybody</em>
    <em class="fragment">for now..."</em>

Boy, was he wrong!

Which he probably didn't say exactly like this, it is very plausible that he added
[slide]
"for now" to that claim.

If working in software development for over 14 years has taught me anything, it's that...

And I think he added the "for now", because mr. Gates knows very well that in the computer industry...

Eventually, there will be a successor.

It might be around "for now", but eventually there will be a successor.

And lastly: TFS is now Azure DevOps Server, and the version control system part is now called TFVC (Team Foundation Version Control).
---
<!-- .slide: data-background-color="#fff" data-background="img/azure-devops-git-or-tfvc.png" data-background-size="60%" --->
note:
You can still pick it when you create a repository in Azure DevOps.

            <th>2009</th>

            <th>2010</th>

            <th align="right">TFS</th>

            <th align="right">TFVC</th>

            <th>2009</th>
            <th>2019</th>

            <th>2010</th>
            <th>2020</th>

            <th align="right">TFS</th>

            <th align="right">TFVC</th>

            <th>2009</th>
            <th>2019</th>
            <th>2029</th>

            <th>2010</th>
            <th>2020</th>
            <th>2030</th>

            <th align="right">TFS</th>

            <th align="right">TFVC</th>

## The disadvantage of the dominant product

## The handicap of a head start

<small>Jan Romein, "The dialectics of progress", 1937</small>

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

Now I was quite confident this would happen, because of a mechanism that is called
"the law of the handicap of a head start".
(or in Dutch "de wet van de remmende voorsprong").
This term was coined by Dutch historian Jan Romein in his essay "The dialectics of progress" in 1937.

The dominant product will get a lot of attention. 
Both positive *and* negative.
Your product - or the users of your product - could be popular victims of malicious software
(This is the reason why there are so many viruses on Windows, compared to Linux for example)
Also, if more people know your product, then in theory there are more people that can come up with fresh new ideas that your product doesn't have.

The law suggests that individuals or groups that start out ahead eventually are overtaken by others. 
In the terminology of the law, the head start, which is an advantage at first, subsequently becomes a handicap.
This phenomenon occurs when a society dedicates itself to certain standards and those standards change. 
Then it becomes harder for the leading group to adapt.
This is exactly what happened during the browser wars!
Society demanded tabbed browsing and Microsoft had a hard time adapting to that, which resulted in Firefox and Chrome taking over.

## The disadvantage of the dominant product

## The handicap of a head start

It is hard to stay on top, hence "the disadvantage of the dominant product".

It is hard to stay on top, hence "the handicap of a head start".

So let's return to the version control world antd see which products we need to investigate as aspiring successors of Git!

So let's return to the version control world and see which products we need to investigate as aspiring successors of Git!

    <li class="fragment fade-in-then-semi-out">autosync mode</li>

    <li class="fragment fade-in-then-semi-out">both autosync and manual merge mode</li>

* **autosync mode** - pushes automatically after each check-in

* integrated project management (bug tracking, wiki, forum and technotes)
* built-in web interface - the Fossil website actually runs on the same web interface
* **autosync mode** - performs an automatic push after each commit
* **manual merge mode** - like Git and Hg

  * SourceForge - <http://fossilrepos.sourceforge.net> 

* Or simply host it yourself using an SQLite database and a web server

Though the SourceForge implementation is a bit unorthodox.
Because Fossil needs just an SQLite database to generate static HTML.

It was even written specifically to support development of SQLite.
Fossil needs just an SQLite database to generate static HTML.

    fossil changes

    fossil changes

    fossil descendants [hash]

    fossil branch new feature current
    public class Sample {}
    fossil add .
    fossil commit -m "change Sample"
    fossil ui

It was also in the VCS popularity graph that I showed you earlier.

        return (int)(Math.random() * 6);

        return 1 + new java.util.Random().nextInt(6);

        return new java.util.Random().nextInt(7);

        return ThreadLocalRandom.current().nextInt(1, 7);

* The disadvantage of the dominant product. <!-- .element: class="fragment fade-in-then-semi-out" -->

* The handicap of a head start. <!-- .element: class="fragment fade-in-then-semi-out" -->

* **The disadvantage of the dominant product.**

* **The handicap of a head start.**

            <th>TFS</th>

            <th>TFVC</th>

TFS only has 1 - which is Azure DevOps.

TFVC only has 1 - which is Azure DevOps.

TFS just doesn't.

TFVC just doesn't.

Being the dominant products, Git and Hg suffer the most from the "disadvantage of the dominant product".

Being the dominant products, Git and Hg suffer the most from the "handicap of a head start".

            <th>2029</th>

            <th>2030</th>

            <th align="right">TFS</th>

            <th align="right">TFVC</th>

            <th><del>2029</del></th>
            <th>2029</th>

            <th><del>2030</del></th>
            <th>2030</th>

            <th align="right">TFS</th>

            <th align="right">TFVC</th>

I think Git will gain a few users who now use TFS.
(In my Git course I meet a lot of TFS users who are switching to Git)

I think Git will gain a few users who now use TFVC.
(In my Git course I meet a lot of TFVC users who are switching to Git)

So Pijul will be the third version control system in 2029!

So Pijul will be the third version control system in 2030!