[tsaifu]

Yeah, web IDEs have made life a lot easier but I don't think the experience works well for a minimal note taking flow. one of the most important things for me when it comes to a note-taking app is to be able to write free form and without the need for too much process - obviously this is not quite possible in markdown or really most digital formats, but also just the fact that I know git is backing my notes store creates a maintenance burden in my mind that I'm not sure I care for. I used to use jupyter notebooks way back when which felt more flexible but even that began to feel too heavy a process.

Do you use git at all in terms of committing notes and looking through history, or are you only ever adding on top and treating a commit like a save in a notepad app? This is a bit peripheral but I've been considering investing in a remarkable tablet, but using it obviously requires me to carry an additional physical device around.

[ppetty]

So for both use cases (Gitlab & Github) their web IDEs are leveraging Git (from the web GUI). So the cool aspect of all of this is that I could clone the repo locally and maybe even re-purpose for a Hugo site. But the core benefit of version control is there.

[tsaifu]

Oh yeah, I know. Let me rephrase - do you actually leverage the functionality that git (through Github/Gitlab) provides you in your note-taking? Do you go back in the history to see what you committed - do you bisect or look at meta, or commit in atomic ways so that things are more "organized" from a timeline perspective?

[ppetty]

Yes! One nice aspect of version controlled notes: change management "trail". Meaning that I don't have to note what specific changes occurred to a requirement in a project but can just change the requirement. If I need to research why something took longer than expected one of the first ways to research that is via file history from git or from Gitlab / Github's History user experiences.