You think the lead developer of sqlite may not be cut out for software development?

Also, what does 2023 have to do with it?

git has been around since 2005. It's ubiquitous. And yes, I think it's a short-sighted and not-great decision to build your own version control system. Whether you're the lead developer of the unix kernel or just some guy writing your own scripts, it's not a good decision. Your title doesn't have much to do with that.

Who should have written git and fossil?

Both were written by people who had problems to solve. Should they have waited around for someone to solve their problems?

> It’s easy one of the most powerful, flexible,

Probably, yeah.

> and if you take the time to learn it, SIMPLE models for version control.

... And there it all falls apart. In practice, git requires a massive amount of learning to use competently, to the point that using something else just to avoid the learning curve is fairly reasonable.

As someone who has learned the ins and outs of git, I struggle to think of a better model for revision control. I never have issues with it anymore, and it took maybe a day to learn how it works under the hood. There's a great article on git internals directly in the git manpages.

I forced myself to learn it as a junior dev. Was it tough? Sure. But my point is that if it's too daunting and frustrating—software development holds nothing but pain for you.