3 ms·
I‘d be willing to pay for a better debugger. But if the debugger doesn’t come with source code that I can inspect and modify, that’s a big negative that will h
by comex 7y ago
I‘d be willing to pay for a better debugger.
But if the debugger doesn’t come with source code that I can inspect and modify, that’s a big negative that will have to compete with whatever advantages the debugger has. (It’s not just a hypothetical use case. I’ve grepped through the source code of GDB and LLDB on several occasions to figure out why they weren’t working properly.)
And if the debugger is SaaS, meaning it will almost certainly disappear in a few years, after I’ve gotten used to it… it would have to be some super magic unicorn stuff for me to consider touching it, even if it were free.
Pernosco is both closed-source and SaaS. Pass.
- sfink 7y agoTry out rr first. It has at least half the magical unicorn sparkles you're looking for, is open source, and runs locally. It's not hard to modify. (I've done it, though not for any core functionality changes.) Then you'll be in a far better position to evaluate the additional benefits Pernosco might provide you. I think your reasons for being leery of it are valid, but there are very legitimate scenarios where it makes sense IMO. (Recording CI jobs automatically, collaborative debugging, situations where the critical dataflow is hard to follow...) And they integrate, too - you can upload rr recordings to Pernosco when you need the extra functionality. I guess it also depends on the pricing model, which I know nothing about.
- sanxiyn 7y agoIf you aren't already using rr, which is open source, do try it. And yes, Pernosco is super magic unicorn stuff. Do read about it.