intro: split intro slides up into multiple files

[chrbeckm]

implement first changes from Klausurtagung

• s. 7 Roadmap @aknierim
• s. 8 adapt plan to proposed changes in order
• s. 16 list advantages of using Linux, explanation why it looks different on every of our laptops
• s. 20 + 21: If the data literacy class takes place remove, otherwise need to shorten it
• s. 22 add screenshots
• s. 23 Vim or nVim?
• s.25 dir structure tikz picture from @aknierim
• short list of mkdir, touch, ls (cheat sheet spoiler)

[aknierim]

Roadmap added in af421f8, d2f62ff, and dd10b62.

[aknierim]

* s. 23 Vim or nVim?

Personally speaking, I would be in favor of Neovim, especially since plugin managers such as lazy.nvim make it very easy to add plugins and customize the editor to your liking/needs.

[SepplL]

Personally speaking, I would be in favor of Neovim, especially since plugin managers such as lazy.nvim make it very easy to add plugins and customize the editor to your liking/needs.

On the other hand Vim has the bigger history and our claim of being available on most systems holds more for vim than nvim

But I can totally see the reasoning of "updating" the slides to keep them more towards what more and more people use nowadays.

[SepplL]

Also I added some first ideas for slides 16 and 22 (now 23 with added slide for previous s.16)
Def. open to discussion and improvements as

• use another script
• make better/bigger images
• more reasons on why linux
• changing from vim to nvim

[chrbeckm]

On the other hand Vim has the bigger history and our claim of being available on most systems holds more for vim than nvim

But I can totally see the reasoning of "updating" the slides to keep them more towards what more and more people use nowadays.

I would argue for that too, with regard to compatibility we would need to think about vi as well

[SepplL]

Do we still want to add a Code/VSCode Screenshot for comparison?

[SepplL]

I would argue for that too, with regard to compatibility we would need to think about vi as well

vim is available pretty much everywhere, where vi exists too.
If you want that type of backwards-compatibility, we might as well make a dive into sed and all lisp-based editors as well.
I don't think it is necessary to go back in time that far. Tbh, all modern systems ship Neovim without any issue as well. And given the appimage available in the Neovim repo, it is very straight forward to get it working on most remote systems as well.

Tl;dr: I'm in favor of mentioning vim as the starting point (albeit historically not accurate), but vi is maybe a bit too much.

[chrbeckm]

Do we still want to add a Code/VSCode Screenshot for comparison?

I would say no, and maybe have a nvim screenshot with one of the python explanation boxes in it, to show even more features.

[aknierim]

Directory structure tikz graphics are now reworked

[SepplL]

Looks good!
Any preferences on showing the structure in a tree command at a later stage?

[aknierim]

Any preferences on showing the structure in a tree command at a later stage?

That thought had crossed my mind, too... I'm still undecided whether it's better to include an image in the slides or just show the "real deal" using the terminal during the presentation. But I guess I'm leaning more towards the latter.

[SepplL]

Do we want to leave out Neovim entirely for the screenshot comparison?

[chrbeckm]

I wouldn't overload it, and two screenshots should be enough. Additionally, we let them install VSCode/Codium and I thought it would be good to show that it has all the features.
We could do a second slide with more screenshots, or use nVim in the demonstration on how to exit and show it there.

[SepplL]

Good point.
Then I would move it to the demonstration to not overload the intro as a whole.
The benefit of showing it live is greater than the slide, I guess.

[aknierim]

The benefit of showing it live is greater than the slide, I guess.

I second that.

[SepplL]

So, all in all, we are close to being done with the intro?
What is missing currently?

[SepplL]

I wouldn't overload it, and two screenshots should be enough. Additionally, we let them install VSCode/Codium and I thought it would be good to show that it has all the features.

Also given the main point in the slide is to show, what a bad editor can look like, presenting their install is more useful.

[chrbeckm]

So, all in all, we are close to being done with the intro?
What is missing currently?

Definitely the answers from this years questionnaire. I can't think of other points right now.