3 ms·
Having worked on debuggers in JS land I can tell you that it would generate lots of bug reports. Does the developer expect a call stack? Does the developer NO
by sroussey 3y ago
Having worked on debuggers in JS land I can tell you that it would generate lots of bug reports.
Does the developer expect a call stack?
Does the developer NOT expect a call stack? Maybe they want to see if the optimization was activated.
Bug reports either way.
That said, all sorts of weird changes happen when a debugger is enabled.
The jit will eliminate various pieces of code and remove variables from scopes, but you better put them back if the debugger stops! This one I remember in Firebug. Oops!
¯\_(ツ)_/¯
- hajile 3y agoSafari has enabled proper tail calls for 8-9 years now and they haven’t caused issues despite Safari having 20% of the worldwide browser market.
- runarberg 3y agoI guess Safari doesn’t have this large a share of developers, who are the main concern here. But I guess we will truly see if this is an issue as Bun increases in popularity.
- hajile 3y agoThe major Google "objection" was automated trace loggers. When something goes wrong, they grab the stack trace and ship it off to the developers. In this particular case, devs definitely see the Safari traces when bugs pop up.
- sroussey 3y agoI feel like it could be represented in the trace or the debugger or both and eliminate everyone issues. Devs definitely don’t like surprises, but also absolutely hate their tools not telling the truth.