4 ms·

For my money, VS Code has the best node debugging experience. As Chrome continues to blur the lines between browser/IDE it makes me think that eventually there

For my money, VS Code has the best node debugging experience. As Chrome continues to blur the lines between browser/IDE it makes me think that eventually there will exist a Chrome "lite", which lacks a lot of features to save on memory/ easier on batteries, etc.

Klathmon 10y ago
Unless I'm horribly wrong, the only thing a chrome lite would save is disk space. These features only activate when you open dev tools. So any overhead to using them won't apply unless they are open. And most browsers work this way. It also makes it a pain sometimes to debug performance issues. One specific time I was having issues with some CPU-heavy JS code in edge. It was taking 45 seconds to process an image, but only like 5 in other browsers. When I opened the edge dev tools, it would take 5 MINUTES to complete!
deleted 10y ago
[deleted]
coldtea 10y ago
>As Chrome continues to blur the lines between browser/IDE it makes me think that eventually there will exist a Chrome "lite", which lacks a lot of features to save on memory/ easier on batteries, etc. That's not how code loading works... Features like those are loaded on demand ("when used"). A lot of people make the same mistake conflating various program features that are orthogonal (and even the pages are loaded on demand, when needed) with increased memory usage and "bloat" in general.