Super supportive as I really value debuggers as tools even tho they are horror shows to use! > Similarly, the following features are non-goals of the project:

Super supportive as I really value debuggers as tools even tho they are horror shows to use! > Similarly, the following features are non-goals of the project: > Supporting non-native languages (i.e. Java, Python, etc.) But I think that position is likely a mistake in terms of leaving killer features on the table and baking in architecture decisions that might continue to make these kinds of features impossible / very low-class experiences. Properly integrating with the python interpreter to be able to debug python + c/cpp extensions running in the same process is a huge missing whole in the debugger market. I don't know how other people do it but I 'solve' this problem by attaching either a python debugger or lldb to the python process -- meaning I can debug either python or the cpp but not both at the same time. The experience is very lacking. Even just seeing the python call-stack while paused at a cpp breakpoint would be huge.