Quote from: hawaii18k on September 17, 2015, 06:00:19 PM

I don't know the reason for your persistent attempt to switch over into new algo, but your credibility has been tarnished due to recent rc3 fiasco. Community will probably resist your next move.

Why not just fix the problem for now. Stick to icm qt for now and postpone the new forking until rc3 is properly fixed. No crashing. No unintended forking. Let not your hard work go to waste.

When that is done, however slow it maybe, you can dish out your new grand plan. Earn credibility, Earn respect.

Everyone makes mistakes. Difference is some learns from it. Perfection comes with price.

Thanks for your Crave efforts!!

*edit
Btw, I did like new qt when it worked. Small memory foot print and not resources heavy. Good for my old mn pc.

I think our problem was a lack of testing and an necessary rush to deploy a new version. I never understood the urgency. Coordinating a fork takes time and requires community acceptance/cooperation. Unless there is a zero day exploit, we should never rush to deploy new, untested code.

I think the Crave urge market version was a good release:
https://github.com/laptoptip/crave/releases/download/v2015.08.28/crave-urge-32.7z