What were the issues?
Concerning the old code it's basically just outdated at this point. Initially the plan was to remove TOR to help with the current orphans issue but once in the code it really wasn't worth the work to go backwards with the code and then try to move forward with newer features.
Concerning the implementation of a new base code was moreless the lack of discussion towards the direction CON is moving. Eg. Coin-Swap or No Coin-Swap, type of POS algorithm, etc.
My wording "issues" might not have been the correct way to explain it but that should paint a better picture.
Also, to be blunt about my position is I am doing a lot of learning here as well. I've been part of Crypto for a few years now but never was a dev for a coin. Was part of the Netcoin foundation for most of my crypto experience thus far. I know quite a few programming languages; however, my weakest unfortunately is C++. What better way to learn more though right? I'm eager to learn more about coin code as well as help out a community in need. I hope this helps everyone get a better understanding of my situation.
Eh OOP is OOP, shouldn't have too hard of a struggle with c++ vs others. The struggle is probably more about the familiarity with the giant code base that the coins come from. What also doesn't help is how fragmented all the coins are with codebases.
I think a lot of the problem is that Crestington might have had partial implementations of certain featuers. And yes, adding the TOR thing was a huge mistake imo. It seemed to really cause the code to struggle, which is why I never updated my block explorer to that code.