Slashdot Mirror
The Future of Google Chrome
TRNick writes "Lars Bak, who heads up development of Google Chrome's cornerstone javascript engine, talks about why Google is so focused on in-browser javascript performance, the role Chrome has played in driving up javascript performance in other browsers, and why it's taking so long to introduce support for third-party extensions. 'The web is becoming an integral part of the computer and the basic distinction between the OS and the browser doesn't matter very much any more,' he says."
Call me ignorant, or rash, or just living on the edge, but I actually use it on a daily basis for *almost everything. I haven't installed FF on this (brand new) machine and don't plan on it simply due to its bloat and slowness - things it didn't have when it was introduced.
Chrome introduced features which IE and FF either have since included as well or are planned for future releases. I am certainly aware that Chrome is quite limited in some areas, but in the end its speed, flexibility, small memory footprint, and physical layout (minimal intrusion into the web page display area) make it my first choice despite its drawbacks. Feel free to correct me where I may be ignorant (seriously, no sarcasm intended).
*Every now and then I find a web app that's just not well coded (mostly due to funky CSS that's poorly formed) that works or at least displays properly in IE but not Chrome. C'est la vie.
For conscience is the wound, and there's naught to staunch it
The problem is people still fail to grasp the difference between Javascript and DOM and CSS manipulation....
All Javascript engines have been ECMA compliant for 5 years now. Javascript incomparability is not the problem, it is the DOM and CSS incompatabilities.
I'd suggest you check out IntelliJ's IDEA 8.0. I've been developing interfaces for the web for ten years now, and I've come across nothing with such comprehensive and accurate support for js coding. Both your complaints about code completion and syntax checking are handled by IDEA accurately.
Some other developers in my group swear by MyEclipse's js handling, but I haven't had any personal experience with it in the past couple of years. My last impression of it was that its color-coding wasn't as detailed as IDEA's. Still, MyEclipse is open-source, so check it out first and see if it takes care of your needs.
For debugging, Firebug is still your best bet, though I believe IE's debugger has been making huge strides lately, and is better than Firebug for automatically handling breakpoints--in Firebug, you have to search through your .js files in order to manually place a breakpoint, and then that can get weird if you have iframes to deal with.
Too late. Google Docs is already here, a JavaScript word processor with real-time collaboration features.
http://pixelcort.com/
Maybe I have been blind, but I have yet to come across a decent IDE for javascript development. All the nice features like code completion and even syntax checking are now no longer a given.
I felt like this for a long time. Finally I discovered , which is Google's own solution to this problem.
I now code my dynamic web components in java in my regular (eclipse) IDE, debug it in Eclipse, then deploy (compile) to Javascript. It's robust, full featured, maintainable, and easily debugged.
- Vincit qui patitur.