2 ms·

In the JavaScript world, debugging is almost a bad word. It’s almost impossible to maintain a sane debuggable trace though a “modern” JavaScript application. I

In the JavaScript world, debugging is almost a bad word. It’s almost impossible to maintain a sane debuggable trace though a “modern” JavaScript application. I find I have to ignore basically all of the standard frameworks and transpiration pipelines and just write old school PHP-like code in Node. I say all of this because I feel that my community has lost control of the debugging pipeline and I applaud Be and Haiku for making that a priority. I find the benefits of committing to an always-running, always-traceable-in-production execution thread is an EXTRAORDINARY productivity gain (vs console.logs and connecting to IDEs manually via various witchcraft)

porker 8y ago
> In the JavaScript world, debugging is almost a bad word. It’s almost impossible to maintain a sane debuggable trace though a “modern” JavaScript application. I felt this last week as I tried Webpack 4 on a new project. The source maps weren't correct, and instead of debugging my app I had to debug multiple Webpack plugins and work out which one was breaking the source maps. Never did find out, but I fixed my app by debugging it mentally. It sure made me wish for a developer-first language.