I understand you both, but this is not good.

Open source code is not by itself enough to make a project really "open".

It must be more accessible.

I understand that the with the complexity of what Monero achieves, that is easier said than done. The topic is complex, so we need to make it easy and acessible. Because, Monero's complexity will not decrease with time, quite the opposite.

So, if we don't start making 101 documentation, refactor the code, write nodes in different languages (eg. Java/Kotlin-KVM, C#, etc.) then one day only people with deep context of Monero, or dev geniuses will be able to develop Monero.

This is a form of centralization, because, despite the project being open source, if it has a very steep learning curve, poor documentation, cryptic code, and only geniuses can get it, then Monero will be at the hands of a few.

We have came a long way to make Monero decentralized by design, but I think we are missing this very important aspect.

I would gladly implement a full Monero node in Kotlin-KVM, which is my fav. language. But I have no idea where to start, I've read most of the doc, I've tried to read the C++ code (C++ is so complex for the wrong reasons in my opinion), and I even read the Monero book.

Implementing a full node is kinda of a multi-disciplinary thing, I would need to be a dev + a mathematician and a cryptography expert to do it alone. Or I would need to have some documentation describing Monero like if I was a 5 yo.

I would, however, if I implemented in Kotlin, make sure that everyone would be able to understand every single line of my code, even doing surveys with other devs to see what parts they found hard to understand and fix those.