We’ve been seeing the performance issue for a couple of months, and when in Live Chat, it wasn’t easy getting the right sort of technical information from our users, and it was tedious for them to collect. However, it took us just a few hours to add the right diagnostic tools to our release, and if had done this earlier, we’d have found and fixed this issue much sooner.
Being a small company, we don’t have large QA teams, and while we tried hard, we were unable to reproduce the core performance issue. What we should have done was increase the number and variety of our stress tests, testing CodeMix on a system under higher load for a longer period of time, which would have increased the likelihood of us being able to replicate this internally, making it much easier to diagnose and fix.
We’re introducing tests that do a better job of simulating real-world conditions under which CodeMix may be used, like alongside a browser that has gone AWOL, or Windows Defender deciding it’s a great time to run a full-system scan in the middle of your work day. Our augmented diagnostics are already in the product, and we’re continuing to stay vigilant about performance issues, from Eclipse, the Code engine, or wayward extensions.
CodeMix is the fastest it has ever been, and if you’re looking for an IDE that allows you to enjoy the best of both the enterprise and the modern-web development spaces, you need look no further – try CodeMix today, for a truly superlative dev experience.