Yeah, Pernosco may not be a great fit when you have to do that. That's not just due to the pricing model --- which we can change! --- but the entire debugging a

Yeah, Pernosco may not be a great fit when you have to do that. That's not just due to the pricing model --- which we can change! --- but the entire debugging approach, where we do a lot of analysis up front, speeding the debugging experience but adding latency to the workflow. Now, sometimes people are doing that because to track down a bug they have to go through many cycles of adding instrumentation or logging to their code. In many cases Pernosco can just make those cycles go away, e.g. using https://pernos.co/about/expressions https://pernos.co/about/expressions. However, if you develop new code using cycles of "add new code, compile, debug", and each of those debugging sessions are short, Pernosco isn't a great fit for that currently.