I received two emails from you with a bug report/complaint 3am on Sunday night/Monday morning and then another at 3:25am. I don’t have a formal SLA for support response, but if I ever do instate one it won’t be “less than 8 hours response time on Sunday nights”. If you feel that’s inappropriate for a product that you’ve paid $100 or $200 for, I’m happy to refund your money and I wish you luck in your search for a tool provider with the SLAs you require.
I previously received one email from you at 23:16 on Friday night my time, which seems to have been for a different problem. I hadn’t responded to that one over my weekend because, like the others, it was basically a “this doesn’t work” type report. I need more information to be able to have any hope of giving you any sort of useful answer. Until now (Monday morning) I probably put about as much thought into reading your email as you did into writing it.
As far as Cursive’s stability, no-one really knows. I don’t have the feeling that it’s suddenly becoming unusable, perhaps I’m wrong. Bear in mind that a couple of dozen people tend to send mail here, tops, and Cursive has around 15k users. Very few people have written to the group saying “Cursive is totally stable, everything is fine”, but that doesn’t mean that that isn’t the case for most users.
It is true that Cursive is a large, complex product, and realistically it is too big for one person. JetBrains have a team of 15 working on PyCharm. But they also have half a million users, so they have more resources to pay for that team. Again, if this makes Cursive unsustainable for you, I’m happy to refund your money. If all you want is a text editor supporting Clojure, you could try Atom with Proto-REPL, which looks lovely. If, instead, you would just like things in Cursive to get fixed, then I encourage you to write bug reports that actually give me some hope of identifying the problem.