With the latest version 2.3 update I included automatic crash reports, and it’s been going very well. I’ve received a number of reports through the automated process and fortunately the majority of the bugs won’t affect you in every day use.
It’s more or less impossible to have software without bugs, but I’d like to make an attempt at bringing the amount of bugs in Mizuu down to a minimum. Obviously, stability is one of the key factors when dealing with software and it’s something that I want to work for. Based on the automatic crash reports I’ve seen a lot of very strange crashes that really shouldn’t be possible, but somehow crashed regardless. I need to find out why it’s happening and fix it.
For the next few months I’d like to focus on stability in Mizuu. I think the performance is quite good now and it’s got a lot of the requested features – not all of them, I know, but a lot. Stability and good software structure is key to future development and adding more features. The code needs to scale well and much of the current code doesn’t really handle that very well. I’ve been re-writing Mizuu for quite some time now, and it’s gotten a lot better, but there’s still work left to be done, as the project is getting fairly extensive.
So… Please consider the next few updates as the foundation of what’s to come. In order to build a nice construction, you’ll have to build a great foundation and that’s what I’ll mainly be doing with the next few updates, so there’ll be fewer new features, but more stability and room for awesomeness to come.