Odd title; confusing for those of us who haven't used TextMate and unnecessarily specific since the feature in question isn't specific to TextMate at all. Surely the title should be "'Go-to-file' and 'Go-to-symbol' shortcuts in Google Chrome Dev Tools...".
Not a while ago, I used to switch to Firefox whenever I was working on any webapp or website because Firebug seemed so much more intuitive than Chrome Dev Tools; but for a few weeks now I don't feel the need to do it. In fact Chrome Dev Tools do provide some features that are not available on Firebug that I think are nice and should be ported soon:<p>1. Computed Style.<p>2. Timeline - It helps to know what triggers are fired when, without putting log statements.
Absolutely Awesome! One more thing is needed, however. The ability to be able to save the modified sources to the server (with appropriate security of course, dev-env only). Also the ability to fetch the server sources from the server, if e.g. I'm running a Node.js and I want to debug and edit the JS in Chrome - <i>along</i> with the client side JS, side by side.<p>The close we programmers are to the "living code", the better. The file-watching, auto-reloading and re-executing BDD's (or TDD's, etc.) like vows (<a href="http://vowsjs.org/" rel="nofollow">http://vowsjs.org/</a>) get pretty close to it, but it's not the same.<p>When I'm coding a function, I want to be able to run it anytime (when the syntax is OK of course), and in the environment of my program.<p>Great stuff. Also similar in-client code editing efforts, Firefox: <a href="https://github.com/Gozala/sky-edit" rel="nofollow">https://github.com/Gozala/sky-edit</a>, general: <a href="https://github.com/ajaxorg/ace" rel="nofollow">https://github.com/ajaxorg/ace</a>