That’s great, and my point is that I’m not sure if this comes clearly across. If I knew from the start that this is all it’s used for, it would have been much easier to estimate the implications of what I do there, and thus easier to handle.
I do store my OH config using Git - and although there are a few “annoyances” (like changing timestamps that trigger diffs that really isn’t a change), it works well all in all. I would never put it on GitHub though, I store it in a private repository that I host myself - and which is backed up to tape.
@ErikDB Yes, that’s fine, but it don’t find that when searching for “changelog”, and I don’t remember that I must use “special rules” to find that changes for OH.
Absolutely, I wasn’t saying that what I described was the only reason for this “dynamics”, and resistance to change when it means loss of time and effort already invested is a human trait which we all probably share to a large extent. But, I still think it’s probable that there is a “filtering effect” on new users, where you never hear anything from those that try and give up realtivly quickly.