shepilov-vladislav/wdb_server_aiohttp

state of this project

Opened this issue · 4 comments

hello! thanks for your work on this porting of wdb. is this project still maintained?

It all depends on how many people use it. I think it may already have faded into oblivion. I don't know of any scenarios where it can't be replaced by other debuggers

arkhan commented

It all depends on how many people use it. I think it may already have faded into oblivion. I don't know of any scenarios where it can't be replaced by other debuggers

What alternatives exist that offer a similar experience to this project?

Thank you for your activity on my project @fessacchiotto and @arkhan!

I would quite sincerely like to develop this project, because at one time I made a fork because the author of the original project abandoned it and it had a lot of bugs and lacked test coverage. And at that time wdb was my main debugger and covered all my needs. Then VS Code appeared and it completely buried the project, because there are no tasks that could not be realized using VS Code Debugger. At the same time VS Code buried a lot of adequate editors - for example Sublime Text 2 (I really loved it, I liked writing my plugins in Python). Now I don't see how my wdb fork can be better than VS Code Debugger and what unique features could resurrect it. WDB still needs to update the frontend part and add a display of the list of local and global variables. But unfortunately I don't have that much javascript experience yet.