-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should this working group be responsible for Debugging or should it have it's own WG #51
Comments
The Tracing WG already deals with some debugging initiatives, such as AsyncWrap which can be used for both debugging and profiling. Having the "Chrome" Debugger in this working group would be logical, however it also has a lot of public interrest which may diverge our resources. I think if a debugging working group is created, it has to be very specific for example "standardizing the debugging protocol". Otherwise it will unclear which working group is responsible for what. There is already confusion about what the post-mortem WG is responsible for and the Tracing WG is about. |
This topic is on the agenda for this week's call - "Expanding scope to Diagnostics WG" |
See also #46 and #47 where I've started implementing what a Diagnostics WG might focus on and look like. I think a single Diagnostics WG with teams focused on different domains (e.g. tracing, post-mortem, protocol/API, step debugging) will lead to good results and experience for Node, for contributors, and for users; help us share and collaborate better; and avoid redundancy and overlap. |
In any case, I'd like to help. |
Closing. Discussion to continue in #46 |
From nodejs/node#7072
There are a bunch of hanging questions regarding the debugger and it would prove helpful to a working group to focus on it. It is likely that there is an overlap in interest between tracing + debugging... but enough of a difference that it might make sense to spin up a new WG.
Would be very interested to hear the thoughts of @nodejs/tracing
The text was updated successfully, but these errors were encountered: