Why
Currently, Monero only has one node written in C/C++, many would see this as an issue. Having only one implementation makes us more vulnerable to implementation bugs, having another node will help us to spot and fix these issues.
monerod’s code is also a bit of a mess, as many devs who have worked on it would agree. Cuprate is a fresh start and is built with modularity in mind which will lead to a cleaner and easier to understand codebase.
Having a consensus rules document will make it easier for developers to build software to interact with Monero. It will also make it easier to spot potential issues with consensus rules.
The above message was cross posted on Reddit by koalabearhugs. My reply on this message seems to get tricked by Reddit (not visible?), so I reply here as well.
" Can’t agree with you more. I am very surprised it got to funding this way. This is a very bad decision for Monero as a whole, and the aggressive way the licensing decision got pushed makes you wonder. It is very hard to crack Monero in a technical sense, this push for permissive (=corporate) licensing is opening Monero widely to be brought down in the future via another angle. For some reason the community doesn’t care. It behaves as an ignorant bunch of people that won’t even investigate the risks and consequences. Goldbacks might be a better route after all. "
In the same thread on Reddit kayabaNerve pointed out some technical advantages of the rewrite in Rust. My reply to this message: “All the supposed technical advantages are of no use if permissive (=corporate) licensing is used. Dangerous development it is.”
Sorry for the crossposts.
Choosing the wrong licensing-model could be disastrous for Monero, so I hope people reconsider.
@RealPappenheimer This issue was discussed at length in monero-community matrix room when proposal was submitted. I guess it’s too late to reverse the decision. Even the person who wrote AGPL-licensed modules appears to support the change, although I don’t know why they suddenly changed their mind.