Slashdot Mirror
Mozilla Teases First Browser Dedicated To Devs
hypnosec writes Mozilla has teased a browser for developers — a first of its kind — in a bid to equip developers with a set of tools at one place for better and enhanced productivity. Speaking about the perils of web development Mozilla says engineers, while building for the web, use a range of tools that don't always work well together. Because of this, they have to switch between platforms. This process of switching from one platform to another makes a developer less productive, Mozilla says. The not-for-profit organization hasn't detailed its browser for developers to a great extent, but has revealed that the browser will be available on November 10.
Isn't SeaMonkey Studio _exactly_ what the summary describes? Maybe I'm missing something, or maybe SeaMonkey is a community fork and not official Mozilla, so it's not counted as the same.
It's kind of amusing this should show up today, the same day I discovered a somewhat amusing little issue with the Firefox developer tools:
The "JavaScript error" developer console log messages (e.g., JavaScript errors) are not necessarily displayed in the same order that "JavaScript console" messages (i.e., console.log) are generated.
Meaning that if you're trying to track down what's generating a JavaScript message in some library you're calling (that is, a warning because the library "helpfully" catches the error for you and just does nothing), you: 1) can't get a stack trace of where that message was generated and 2) can't rely on "console.log" statements to help you narrow it down since "console.log" messages can be out of order of any other message type. I have no idea why this would be the case since JavaScript execution is explicitly single-threaded and having messages generated by a single thread appear out-of-order makes absolutely no sense, but - well, Firefox managed it.
I did, eventually, figure out a solution to my problem: I used Chrome instead. Not only did my app run twice as fast, Chrome messages are in order and included the property being read off the null object. (Allowing me to track down how the library managed to find a null off a non-null argument.)
So I'm glad Firefox is trying to make a "developer-centric browser," now if only their current browser tools weren't terrible.
You are in a maze of twisty little relative jumps, all alike.
I write code in the editor of my choice, then I open chrome and look at my results.
Presumably as you continue to tweak the code, you have to save and wait for the browser to notice one of the source files has changed. An IDE like browser could update live and instantly from memory, every time the source changes to something legally parsable.
And of course browsers already have built in developer tools, and/or plugins. But there's so much more that's possible.