News for hackers. Stuff that matters.

A comment on Using Code Snippets in Chrome Developer Tools. Parent comment

Re:Using Code Snippets in Chrome Developer Tools by dingaling on Saturday July 30, 2016 @07:34AM (#12192547)
The dev tools built into browsers also tend to be rather bloated and sluggish; opening Firefox's debugger on my 2010 Core2 Duo laptop pegs the firefox process at 40% CPU just idling. Scrolling is painful.

Passable for making a quick change to test an idea but I wouldn't use it as an introduction to an IDE.

Then again I suppose I should be grateful it runs at all; Servo browser won't start because it requires a certain level of OpenGL support from the chipset. That makes me worry about the future hardware requirements of browsers and is another reason for splitting dev tools off from the client UI.

[ Parent | on HN ]
Re:Using Code Snippets in Chrome Developer Tools by chias on Saturday July 30, 2016 @12:14PM (#12193553)
> The dev tools built into browsers also tend to be rather bloated and sluggish

> Scrolling is painful.

> Passable for making a quick change to test an idea but I wouldn't use it as an introduction to an IDE.

I have the same experience, albeit in Chrome. Using it on "about: blank" and restricting yourself entirely to the console helps (e.g. no debugger, not using the feature described in OP, etc). But at that point it's just a REPL, not an IDE.

[ Parent | on HN ]