4 ms·
The downside of using a code converter is that when something does break, the browser is going to show you the generated code and you have to map that back into
by jandrese 7y ago
The downside of using a code converter is that when something does break, the browser is going to show you the generated code and you have to map that back into your original code. If the generated code is ugly (hint: it's always ugly) then this can be a real problem.
The generators can also do things in really dumb ways that make it slow or resource intensive and you'll have no clue why your elegant solution is running like a dog unless you go through and read the horrible generated code to see what it is actually doing.
- the-pigeon 7y agoSource maps help a ton with this. Have never had an issue figuring out where the heck an exception came from when I've had source maps setup correctly.
- alkonaut 7y agoSo that's one source of complexity/difficulty: our "debugger" is a bloody web browser. And there may be transpilers between what we write and what the debugger sees as the source.