Bonus lunch Dec 28th: Javascript tools roundtable
Just can’t get enough web geeks? This month we’re having a bonus lunch! That’s right, two in the month of December! Jeremy Geerdes really wants to lead a round-table discussion about Javascript development tools such as Firebug, Chrome Developer Tools and IE 9’s F12 Developer Tools as well as some of the popular add-ons that make these tools even more powerful. Who are we to say no to such a request?
So come to Smokey Row 1910 Cottage Grove, Des Moines IA (near downtown) on Wednesday, Dec 28th at 12:00 for a round-table discussion. Jeremy has a few interesting tricks he’d like to share and wants to hear some of your favorite tools and techniques. This is a conversational format, not a presentation. If it is anything like our last round-table, it will be power packed and you very likely will want to take a few notes.
If you could please RSVP by either leaving a comment here or on our Facebook event page, that would be awesome. See you there!
6 Comments
Grab the rss feed for this post, or use the trackback link. Post your own comment.
Leave a comment
Say What?
Des Moines Web Geeks is a group of web professionals and enthusiasts looking to meet, share ideas and have some fun. Everyone is welcome to join and participate. Have an idea for a session? Tell us.
Stay connected
|
| Subscribe to dsmwebgeeks |
| Visit this group |
Chad Thompson
December 20, 2011 - 8:04 am
… I’m in. I’m mostly a Firebug user by ‘default’, so I’d love to hear some perspectives on other tools as well. Does anyone also have experience with the Safari Developer tools?
matt
December 20, 2011 - 8:06 am
I think Safari’s are mostly like Chrome’s, but I do use Safari sometimes because it has a built in user-agent switcher for emulating the iPhone.
Justin
December 20, 2011 - 8:49 am
@chad: I as well use Firebug by default. I’ve been using FireFox for so long I’m just too lazy to switch to a different browser. I only use Safari for testing websites, so my experience with their dev tools are limited. I’ve found editing HTML from the inspector a bit cumbersome in comparison to FireBug. FireBug gives you a whole new editor to modify the HTML where Safari has you edit in a small text area, but you do have the option to export the selected HTML which is nice.
Jeremy Geerdes
December 20, 2011 - 10:02 am
Safari and Chrome share the common lineage of WebKit, which is actually where the bulk of both their dev tools come from. And what’s really cool is that, since both Apple and Google are committed to the WebKit core, they (especially Google) are constantly pushing the improvements which they incorporate in Safari and Chrome, respectively, back up to WebKit so that, eventually, the improvements cross-pollinate.
That said, Firebug is a phenomenal tool. So great, in fact, that Mozilla actually supports the project directly. But Mozilla is also working on their own dev tools, which should prove to spur innovation on their end as well. The one problem that I have with Firebug is performance. Mozilla did a survey of worst-performing add-ons a couple months ago, and Firebug was at the top of the list. Sadly, there is no real way to mitigate this because it’s inherent in the way Firebug has to work. So WebKit descendants have a significant advantage when it comes to performance.
Jeremy Geerdes
December 20, 2011 - 10:33 am
I’m considering three possible routes for the discussion: basic use (e.g., DOM inspection and manipulation, error console); advanced debugging (e.g., JS breakpoints, scope inspection); performance analysis (e.g., network issues, code optimization, image spriting).
Which of these three options do we prefer?
aeischeid
December 27, 2011 - 4:00 pm
A couple of us Ames geeks are going to try to make it down.