K. Gadd wrote:
The accuracy of this aside, history shows that most of my users are
not satisfied by 'just debug the JS, it's fairly readable'. Maybe
emscripten, gwt, etc. users are more fluent in JS and don't mind
debugging it, but based on what I've seen, maybe not...
I do think it's important
The accuracy of this aside, history shows that most of my users are
not satisfied by 'just debug the JS, it's fairly readable'. Maybe
emscripten, gwt, etc. users are more fluent in JS and don't mind
debugging it, but based on what I've seen, maybe not...
I do think it's important that source maps
On 3/14/14 at 3:02 PM, fitz...@gmail.com (Nick Fitzgerald) wrote:
I feel very strongly that users debugging their sources that were
compiled to js should be able to set watch expressions and conditional
breakpoints in their source language.
My experience with debuggers says the while the vast
I'm not married to the AST format I proposed.
I do feel very strongly that each language targeting JS shouldn't have
to write a browser devtools extension for every browser its users want
to debug.
I feel very strongly that users debugging their sources that were
compiled to js should be able to
As the maintainer of the ClojureScript compiler this doesn't sound like
much of a simplification. The sum total of source map support in
ClojureScript is < 400 lines of Clojure. To support what's being proposed
would add a significant amount of complexity for something we don't care
about at all -
On Wed, Mar 12, 2014 at 2:00 PM, Nick Fitzgerald wrote:
> If a debug format for targeting JavaScript were to be standardized, it
> should do more than simply file/line/column translation. My thoughts
> on this subject outgrew an email reply, so I have collected them here:
> http://fitzgeraldnick
I agree that the current source maps format does a poor job of
handling many translation/transpiling/js-as-compilation-target
scenarios. I do think it is worthwhile to try and build on the
existing format instead of reinvent it or significantly overhaul it,
though. The things it does, it does a pre
> 4) Browsers are still all over the place in how they report Error stack trace
> information.
We (Firefox Developer Tools) purposefully don't expose source mapped
stacks to the web because it would require adding some kind of API to
know when source maps are done being fetched or blocking(!) on
8 matches
Mail list logo