3 ms·
You're getting a lot of hot takes, which is too bad! For my part, I've been trying to come up with something constructive to say but I'm having a rather hard t
by lolinder 3y ago
You're getting a lot of hot takes, which is too bad!
For my part, I've been trying to come up with something constructive to say but I'm having a rather hard time understanding what this project is, so I guess that's my feedback. The landing page tells me almost nothing about why I'd pay for a third-party debugger, and the docs on GitHub are only a little bit better and not super persuasive.
Maybe I'm just not the target audience, but I think you need to really capture the pain points you're solving before showing me screenshots and videos of how you've solved them. As it is all I'm seeing is a developer tools window with a slightly different layout than Firefox/Chrome.
- sesm 3y agoLooks like an alternative client for chrome://inspect and works on top of the same protocol (you need to launch with ‘—inspect’ flag).
- vmfunction 3y agoOr the debug in vscode, then again in vscode you can edit the code also. Maybe this console has VM binding. Just feel like it should just be a vscode plugin.
- solardev 3y ago> Maybe I'm just not the target audience, but I think you need to really capture the pain points you're solving before showing me screenshots and videos of how you've solved them. As it is all I'm seeing is a developer tools window with a slightly different layout than Firefox/Chrome. Same here. I watched the video and couldn't quite figure out what it's trying to show. It just looks like it's logging requests similar to the inspector or the debugger. That's cool, but how is it different or better?