By this logic, you want a complete monopoly of a single platform? Because that’s the only possible way to have “no barrier”. Unless GitHub starts federating with some kind of standardized protocol. This is a huge technological and monetary barrier for GitHub, which is why it will never happen on its own, so if users are not willing to try platform-independent workflows then the problem is frankly not the competing platforms.

I wouldn’t say “need”, but there are possible improvements to ergonomics and safety that wouldn’t make the language itself more complex or high level. I think it does its job quite well though and will be here for decades to come.

This is only true for the merge request workflow and not at all a problem for the patch workflow, which can work entirely via email (and is in my eyes simpler). Have a look at https://git-send-email.io/ if you want to learn about it. This is the true decentralized spirit of git. :)

There are many good replacements, you just need to stop using Github :)

Some examples: Forgejo/Gitea (self-host or hosted eg. codeberg.de), Gitlab (self-host or hosted), Sourcehut (self-host or hosted eg. sr.ht)

Its cross-platform support (not just for using but also for building it) is not there yet, and it is quite huge and unstandardized with only one full implementation. I’d agree the last part will change with age, but given the frequent large changes and feature additions I am afraid it will be harder and harder and it is simply too complex and fast-moving for many low-level applications. It is closer to C++ than C in my eyes. I’d be happy seeing it replace C++ though for its memory safety benefits!

C is old, ubiquitous and still does not have a good replacement for its low-level cross-platform usecases, so I’ll believe it when I see it 😄

That is answered in the original post, the author is just doing this for fun and learning. :)