There are few front-end web developers I know who actually use the Eclipse editor for development. Whether it’s the complexity of the IDE or simply resistance to change I cannot say. Working with Eclipse on enterprise apps has some serious advantages when it comes to working in multidisciplinary teams. And wrenching on a UI is no exception.
As of late HTML5 is beginning to bear the shine of a recently waxed Tesla Roadster. It’s hard not to want to jump right in and hit the gas. But wait, the HTML5 spec is still in draft. Is it safe to turn over the ignition? Well, it depends. But here are 5 Reasons Why You Can Use HTML5 Today (archive).
Last year when Eclipse Helios was released HTML5 didn’t validate within the IDE. But somewhere between that release and the latest Helios service release, support was added for actual *native* HTML5 (archive) elements in Eclipse, no plugin required! And you don’t need to be running Aptana either. Awesomesauce!
The following instructions will help Eclipse newcomers and experienced client-side developers alike get started, kinda like a big smokey burnout.