<section>
                    <h2>Now what?</h2>
                    <ul>
                        <li class="fragment">A lot of projects are nothing like the Linux kernel. <strong>So try Fossil for a change!</strong></li>
                        <li class="fragment">Git's snapshotting might be too technical for the average Git user. <strong>So try Pijul for a change!</strong></li>
                    </ul>
                
                    <aside class="notes">
                        <strong>Time Elapsed: 45 min.</strong>
                        OK, so now what?
                        Well, of all the things I learned by doing research on this topic, two of them really struck me as important.
                        1. Git was intended for global open-source development with thousands of contributors.
                        2. A lot of students in my "Git for developers" course are managers, test specialists, requirements engineers, Scrum Masters. And they struggle with Git's snapshot-based approach. Perhaps a patch-based approach like Pijul will suit them better.
                </section>

                                    href="https://nest.pijul.com/hannotify/will-git-be-around-forever-slides">https://nest.pijul.com/hannotify/will-git-be-around-forever-slides</a>

                                    href="https://bit.do/utrechtjug-successor-of-git">bit.do/utrechtjug-successor-of-git</a>

                                    href="https://hannotify.github.io">https://hannotify.github.io</a></td>

                                    href="https://hanno.codes">hanno.codes</a></td>

* Niet te snel praten!! Er is tijd genoeg!

## Version Control 'By USB Stick'

## Version Control 'By USB Stick' <!-- .element: class="fragment" -->

And at my first job, about 14 years ago, we did a revolutionary thing with regard to version control.

And at my first job, about 14 years ago, we did a revolutionary thing regarding version control.
I was really eager to learn it, because at college we did version control by sending each other emails with zip files in it.
Surely my employer would teach me something more sophisticated?
[slide]

And at the first job I had, we did a revolutionary thing.

At Info Support, besides doing consultancy work, I also teach a few courses.

I've gained some experience with real Version Control Systems like Subversion and Git.
Now at Info Support, besides doing consultancy work, I also teach a few courses.

So, for example, Subversion relates to the Nokia 3210. (*point*)

So, for example, Subversion relates to the Nokia 3210. (point)
Which are both *undestructable*.

Now, when I talk about this slide during the Git course, I tend to focus on the events of the year 2005. (*point*)

Now, when I talk about this slide during the Git course, I tend to focus on the events of the year 2005. (point)

Which he probably didn't say exactly like this, it is very plausible that he added

Which he probably didn't say **exactly** like this, it is very plausible that he added

<!-- .slide: data-background="img/background/problem-encountered.jpg" data-background-color="black" data-background-opacity="0.5" --->
## 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> <!-- .element: class="attribution" -->
note:
Yeah, one problem though.
We haven't included *any* new products.
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?

note:
So, there you have it - Git will stay on top.
Thanks for attending everyone, until next time.
Just kidding.
---
<!-- .slide: data-background="img/background/problem-encountered.jpg" data-background-color="black" data-background-opacity="0.5" --->
## 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> <!-- .element: class="attribution" -->
note:
Yeah, one problem though.
We haven't included *any* new products.
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?

---
# Fossil for Git users
<https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki>

Which look sa bit like the interactive rebase screen in Git.

Which looks a bit like the interactive rebase screen in Git.

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

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