You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Everything in Paws will have to be different from what developers are used to using, in terms of debugging. Even at the simplest level, stack traces (as an example amongst many) are no longer relevant or applicable. From there on up, everything from profilers/heatmaps to interactive debuggers (GDB or the WebKit devtools) will have to be re-thought in an asynchronous, parallel context.
I spent a little time today considering some sort of real-time, multi-dimensional map of execution nodes … but we still need something simpler than that to take the place of stack-traces.
Also, how do time-machines come into play with all of this?
The text was updated successfully, but these errors were encountered:
Everything in Paws will have to be different from what developers are used to using, in terms of debugging. Even at the simplest level, stack traces (as an example amongst many) are no longer relevant or applicable. From there on up, everything from profilers/heatmaps to interactive debuggers (GDB or the WebKit devtools) will have to be re-thought in an asynchronous, parallel context.
I spent a little time today considering some sort of real-time, multi-dimensional map of execution nodes … but we still need something simpler than that to take the place of stack-traces.
Also, how do time-machines come into play with all of this?
The text was updated successfully, but these errors were encountered: