I don't know if anyone from the team is reading this, but I'll tell you want I want from a Javascript debugger:<p>I want to be able to modify/add code, try it out, then rewind, and try something else. Then save my changes once they work perfectly.<p>Simply setting breakpoints and watching variables is nice, but I can do basically the same thing by echoing/console.log'ing things. If you are going to go to the effort of making a debugger, then make it do something I can't do another way.
Is this expected to be faster than the XUL based stuff? Currently "React" to me makes me think poor performance, simply due to bad experiences I've had with web applications and 'native applications' (read: web browser wrappers).<p>Surely there's going to be overhead using the remote debug protocol, it looks like it's built on JSON so every response is going to need to be deserialised? I can understand that it's nice to have the official tools using the same APIs that external tools would use, though (and supporting multiple targets is a nice benefit).<p>Further (and this is perhaps less on-topic), why do all UIs need to be written in HTML/CSS these days to be considered "modern"? More broadly speaking, is a GTK or Qt interface going to be less performant than something using a browser engine? The motivation I've seen at a lot of companies seems to be that they already have web designers who can design web pages, and so these people are put to work designing desktop applications too. That's all well and good, but it seems to often result in a poor user experience and be visually different from the rest of the OS.
Talk about the refactoring from React Rally: <a href="https://www.youtube.com/watch?v=Fk--XUEorvc&t=8542s" rel="nofollow">https://www.youtube.com/watch?v=Fk--XUEorvc&t=8542s</a> (starts at 2:22:22)
The debugger landed in Nightly today, its not quite ready for prime time yet but on by default and getting updated regularly. <a href="https://nightly.mozilla.org/" rel="nofollow">https://nightly.mozilla.org/</a>
I'm sure it's been considered already, but I'm immediately concerned about the security implications of running a node server when debugging. Perhaps that is only the case when debugging in a stand-alone setup?<p>Think if you RDP to Firefox or Chrome and forget that the server is running. Does that mean that if I browse to <a href="http://your.machine:8000" rel="nofollow">http://your.machine:8000</a> that I can control your browser?
Another feature I was trying to find was a way to see the history log of changes of a variable and the lines where it happened, between two program states.
I'd say just look at Chrome dev tools and copy them at this point. Debugging in Firefox is a mediocre experience IMHO. As for the name .html is unnecessary.