Could Anything Make You Use IE9?

March 5th, 2010 by Brian Comments »

There's been a fair amount of publicity lately about Microsoft bringing Internet Explorer much more in-line with modern rendering engines with the upcoming release of Internet Explorer 9.0 which they plan to unveil at Mix10. There's talk of strong HTML5 support, improved CSS compliance and even some support for CSS3. Everything we're hearing is that 9.0 will do what some (naively) hoped IE 7.0 would do: bring IE in line with the "better" browsers of the world so we could earnestly look forward to the day we could stop saying, "I'll do that when it's supported in IE." All of it got me thinking: as someone who hasn't used any version of IE as my daily browser since Firefox was called Phoenix, is there anything Microsoft can do today that would make me want to use Internet Explorer?

Disregarding for the moment that my primary work and home computers are both Macs, would any version of IE be able to erase years of near torment the earlier versions have caused myself and other developers? I tweeted this question earlier today but I wanted to open it up to even broader discussion.

Suppose IE 9.0 really is all that and a bag of chips. Suppose that it's rendering engine passes Acid 1, 2, and 3 with flying colors and in the same time as Webkit and Gecko. Suppose that the Javascript engine runs circles around V8. Suppose the same set of HTML5 elements are supported out of box. Basically: suppose that IE 9.0, by every measure that we routinely use the demonstrate IE's inferiority, ranks ahead of the competition in all of these areas.

Would you use it?

Asking myself this question honestly, I don't know that MS can do anything with IE to make me forget the connotation that the previously harmless two letters have in my eyes. Even when used under different context, I can't help but cringe when I hear the letters "I and E" put together.  There are some out there that would view IE's closed-source nature as a serious hindrance and refuse to use it on ethical grounds alone. I'm far more interested in the web development community as a whole: would you really use IE if it were *gulp* better?

I hope it doesn't matter.

I truly hope that the answer to this question is moot; it will mean we've finally reached a day where users have real choice in browsers As developers, we'd no longer have to fear the extra work that will be caused by users who choose to use the default.

  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Technorati
  • Twitter
  • DZone
  • HackerNews

Pass that Interview 2: Understanding Recursion

March 1st, 2010 by Brian Comments »

Recursion is one of the most misunderstood concepts in software development. Truthfully, in modern software development it has been almost completely replaced by iterative control structures (loops). In front-end UI-layer development, it is very rarely used. However, it's very common that you'll be asked questions about recursion during an interview. Why? I compare it to airlines hiring Air Force and Navy fighter pilots. No, they're never going to need to barrel roll a commercial jet-liner but the fact that they understand and know how to do it makes them more complete pilots. Similarly, understanding concepts such as recursion opens up new ways of thinking for engineers.

In its most simple terms, a recursive function is a function which returns a call to itself. Naturally, one has to be careful with this type of construct as it's easy to create an infinite loop. A typical recursive pattern involves breaking a problem into smaller pieces (such as searching a large data set) rather than performing a process multiple times as in iteration.

A common interview question may involve implementing a factorial function using recursion. Let's take a quick look at how we could do this:

function fact(x) {
    if(x > 1) {
        return x * fact(x-1);
    } else {
        return 1;
    }
}

By including a call to itself in the return, the program builds up and subsequently tears down a call stack. Rather than looping over an operation, we're breaking the problem into smaller pieces until it's simply returnin the value we passed in.

Drawbacks of Recursion

Now that we have an understanding of how to create a basic recursive function, we need to be able to discuss the drawbacks of this approach. First, in most programming language, the loop control structures (for, while, etc.) are optimized for speed and will (in the vast majority of cases) be faster.

Second, the memory overhead for allocating all of those functions can grow massively; especially in dynamic languages like Javascript. In our above example, if a user called fact(200) we would incur the overhead of creating 200 function instances in memory. You can see that for large operations this will get very heavy.

Stand Out

For the most part in front-end development, you won't be delving deeply into recursion; but armed with this basic understanding of the topic, you'll stand out from other candidates who aren't familiar with a wide array of software engineering concepts.

  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Technorati
  • Twitter
  • DZone
  • HackerNews

Pass that Interview 1: Mimic a Class in Javascript

February 10th, 2010 by Brian Comments »

Javascript, unlike most object-oriented programming languages, does not have the concept of Classes. Instead, Javascript uses a model in which objects are created, cloned, and enhanced by creating copies of the objects (it's loosely based on the Prototype pattern). There is a lot of power in this Prototypal system and people like Douglas Crockford have shown how Prototypal inheritance can be implemented in Javascript. This type of work is really cool; unfortunately it's not generally well-known or well-understood and many developers wish to use Javascript to simulate the more familiar Classes & objects as seen in languages like Ruby and Java.

Due to this simulation being common practice, the following has become a fairly common interview question:

How do you create a class in Javascript?

The answer is a bit wonky; but pretty simple to follow:

» Read more: Pass that Interview 1: Mimic a Class in Javascript

  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Technorati
  • Twitter
  • DZone
  • HackerNews

My Impressions of Google Web Toolkit (GWT)

February 8th, 2010 by Brian Comments »

Recently I've been asked several times for my opinion on the Google Web Toolkit (GWT)  and I've given much the same response each time. Now, it's easier to consolidate my thoughts and share them with everyone via my blog.  I want to preface this post by stating, as I always do, that I have not taken a "deep-dive" look at GWT and, due to my stance below, I haven't seen a reason to do such research.  I also want to state up-front that I don't believe there's any inherent flaw in GWT that prevents me from using it; nor do I think it's "bad technology." Finally, I've done my best to not allow my general distaste for Java influence my opinion of GWT.

I do not believe that GWT offers a unique value proposition as a platform that establishes any advantage over other Web development platforms such as traditional HTML and CSS or Adobe Flex. Additionally, there are some clear areas in which GWT lags behind these counterparts. » Read more: My Impressions of Google Web Toolkit (GWT)

  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Technorati
  • Twitter
  • DZone
  • HackerNews

Hello Brightcove!

November 3rd, 2009 by Brian Comments »

Monday was my first day in my new role as Prinicipal UI Engineer for Brightcove and I'm quite excited to begin this new chapter of not only my career, but my life as well.  Brightcove is headquartered in Cambridge, MA which means the first major physical relocation in over 20 years for me.  More importantly, it's the first time I'll be living outside of Atlanta as an adult.

There were may reasons I chose to accept this opportunity and uproot my life to come here. Most notably, I believe the word "opportunity" truly applies.  I spent a good portion of my half-day interview in Cambridge in early October talking about where I want my career to go; and not just anecdotally via the typical "Where do you see yourself in 5 years?" interview question.  We talked about how my desired path can fit into the Brightcove structure and culture and we talked about how to leverage my current skill sets to make those transitions possible. While I grew tremendously in my time at ATC, I believe I'll grow much more, and much more quickly, and Brightcove.

I also saw the opportunity to come to a company that sits on the leading edge of technology on the web; and a company where initiative would be embraced from engineers rather than stifled.  And the company showed tremendous faith in me throughout the whole Interview and Negotiation process.

The fact that they use the Scrum methodology certainly didn't hurt things either.  Oh, and they have some of the world's best Flex developers for me to learn from as well.  :)

All of these things, and the general feeling of excitement I had when I walked out of that interview, made it a very easy decision for me to pack up and move to New England.  When I arrived for my first day, I found that people know who I am, are happy I'm there, and are ready to look to me for leadership in the UI Engineering discipline.

I look forward to this adventure!

  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Technorati
  • Twitter
  • DZone
  • HackerNews

Goodbye ATC

October 23rd, 2009 by Brian Comments »

Today is my last day at AutoTrader.com.  I've been here just shy of two years and it's been a fantastic experience. I've learned, grown, and met some wonderful people with whom I hope to remain friends for years.  At ATC, I was able to truly able to embrace the discipline of UI Engineering and learn so much from so many people that I'm ready to take that next step.

The first year was simply the best work experience I've had. I met people who twisted my mind in ways it'd never been twisted before. I learned about enterprise software architecture and the unique challenges faced in that type of environment as opposed to client work. I attended my first major web conference in nearly 10 years, and, of course, I made some fantastic friends along the way. I participated as a lead engineer in one of the greatest feats of enterprise web engineering ever accomplished; one that won't be talked about in engineering circles, but if you were there, you knew what we accomplished was truly incredible.

Over time, I came to the realization that despite my and others' efforts, the company would never shed it's very conservative nature.  And frankly, it's hard to argue that potentially putting off many millions of unique visitors a month by becoming more "cutting edge" is a great idea when revenues are at stake. But the inescapable fact, as famously explained by one of the executives, is that "AutoTrader.com is an advertising company," not an engineering company. As such, after a time, an engineer is going to begin to feel somewhat "stifled" in that environment. Once I began to feel as if it were sapping my motivation, I knew it was time to move on.

All that said, I did not look for a new opportunity; one fell into my lap at the right time and I've chosen to seize it.  I'll write about my new company in a separate post; and I'm very exciting about the whirlwind of change it means for my life!

Goodbye AutoTrader.com and the wonderful people I've met there along the way; you will very sincerely be missed.

  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Technorati
  • Twitter
  • DZone
  • HackerNews

How Self-Executing Anonymous Functions Work

September 24th, 2009 by Brian Comments »

In my recent post on creating a jQueryUI widget, I referenced the concept of self-executing anonymous functions. I've actually had a few questions come up at the office lately about how they work, so I figured turning it into a blog post might not be a bad idea. It's an important concept in Javascript many don't know about. Others know how to use them, but don't really understand how or why they work. Today I'll cover step-by-step how to go from a traditional function to a self-executing anonymous function; hopefully it will be clear at the end how these things work.
» Read more: How Self-Executing Anonymous Functions Work

  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Technorati
  • Twitter
  • DZone
  • HackerNews

Create a Basic jQueryUI Carousel Widget

September 17th, 2009 by Brian Comments »

One of the topics that was of great interest at #jqcon was jQueryUI and it's impressive widget library.  What didn't receive as much attention was how exactly to go about creating widgets that are compatible with jQueryUI.  In this first of a series of articles in jQueryUI development, we'll cover the basics of creating a simple jQueryUI widget.  In future articles, we'll look at how to pair widgets together using the Publisher / Subscriber (pub/sub) pattern.

This carousel is probably not quite robust enough to be deployed to production and I urge you to avoid copying and pasting this code into your live site. This basic carousel aims to teach you how to build one yourself as well as how to build a jQueryUI widget.

Create the Basic HTML Markup

To begin, we need a basic page and some photos thumbnails to work with. The thumbnails, as you'll see later, can be any size you choose and our carousel will expand to fit them. Note especially that we're only including some basic shell markup.  There are a few good reasons for this decision: First, it keeps our basic document clean and free of extraneous markup. Second, it is far less work for people implementing our widget—and fewer potential points of error in their process.

<div id="slide">
    <div>
         <img src="img/carousel/0_10.jpg" width="78" height="29" alt="" />
    </div>
    <div>
         <img src="img/carousel/0_11.jpg" width="78" height="58" alt="" />
    </div>
    <div>
         <img src="img/carousel/1_6.jpg" width="78" height="58" alt="" />
    </div>
    <div>
         <img src="img/carousel/1_4.jpg" width="78" height="58" alt="" />
    </div>
    <div>
         <img src="img/carousel/0_9.jpg" width="78" height="58" alt="" />
    </div>
</div>

For demonstration purposes, I've chosen the Cupertino theme available for download from the jQueryUI ThemeRoller application. You can choose any theme you desire—or create your own. Also, you can see I've created a reference to a  carousel.js file. We'll create this file as we continue.

Create the basic framework of a jQueryUI plugin

Now that we have our basic structure in place for the carousel, we can begin to create the javascript that will control the animation and interaction. jQueryUI provides a great construct called $.widget() that will encapsulate all of the functionality of the widget within a single namespace and construct. Let's start by creating a basic widget:

» Read more: Create a Basic jQueryUI Carousel Widget

  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Technorati
  • Twitter
  • DZone
  • HackerNews

Collected (abridged) thoughts on #jqcon

September 14th, 2009 by Brian Comments »

I spent September 11-14 in Boston for jQuery Conference 2009.  For $150, this conference was probably the best value I've seen in a conference.  Packed with great speakers on great topics, it was more than I was expecting.

I spent most of my time tweeting the event using the #jQCon tag, but I wanted to collect some thought here in a slightly more robust way than I could using Twitter.  Here it goes:

  • jQuery 1.3.3 looks really sick; John and the whole core team have done some fantastic work.  I really appreciate that these guys are really committed to making jQuery competitive in the running for "fastest" JS library.  A 3.5x speed increase overall in 1.3.3 is nothing to sneeze at.  I can't wait for the release!
  • There are a lot more implications selectors being parsed right-to-left in jQuery than you might imagine.  As always, specificity plays a big role; but not necessarily in intuitive ways.  I'll probably write a more full post on this topic as my mind really got swirling around this one.
  • People are totally stoked about jQueryUI and jQueryUI Labs.  That's a good thing as I see absolutely huge potential for jQueryUI and I've been developing some widgets that I plan to release on github relatively soon.
  • The guys from JavascriptMVC are interesting characters.  And they get huge props for handling an attendee asking them to "fast forward" their presentation in a humorous way.
  • ARIA is fantastic technology that people should really, really be looking into.  An interesting project would be to make all jQueryUI widgets ARIA-compliant.
  • People who use and preach jQuery love Event Delegation.  I was in really good company with these guys and I was happy to see it getting so much press.  jQuery's $.live() handles delegation for you which is just slick.
  • TestSwarm, as I anticipated, is going to rock. Javascript testing got a lot of press too and I'm really stoked that it did.  I was a little disappointed that there wasn't much coverage of testing frameworks (not even qunit)
  • Steve Souders is even more passionate about front-end performance than I expected him to be.  Also, big ups for doing his presentation on less sleep than I had the night before.
  • There's a lot of talk about how to organize your code with jQuery.  It seems that the fact that jQuery doesn't enforce some type of structure is both a blessing and a curse.  I've often said that for ATC, a big barrier has been that prototype's class functionality gives us something that we haven't been able to replace in jQuery.  The good news is that a lot of people are thinking about it and there are some great solutions out there.

I also have some thoughts about the social aspects of the conference

  • The question I was asked most:  "how about the ratio?"  It had to be at least 25:1; but it could have been 30:1
  • There's an iPhone version of the drinking game "Circle of Death" out there.  That made for every bit as much fun as you might imagine.
  • After enough adult beverages, John Resig's "smooth-jazz" voice does lighten a bit. :)
  • It was great to find so many people there who were truly social.  I was expecting to have a harder time getting people to open up--but there were others there that shared my mindset.
  • Off the top of my head (and if you're not on the list, it's because I simply didn't think about it very long or we only talked briefly) it was great to meet and spend time with @bobholt, @jeresig, @voodootikigod, @rmurphey, @snookca, @bitofgrace, @bpartridge, @binary42, @Cowboy, @defunkt, @dainbrain
  • I still wish I'd met even more.

Great time; more to come from me on the conference.  But that's an early round-up!

For those that weren't there, @bobholt set up a site to aggregate the slides.

  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Technorati
  • Twitter
  • DZone
  • HackerNews

Quick Javascript Tip: Pass an Options Hash

July 13th, 2009 by Brian Comments »

A quick Javascript tip that I pass along in a lot of code reviews is to make use of an options object as a hash to pass a large number of parameters to a function without writing each one individually.  For example:

function doSomething(id, someParameter, anArgument, optionC){ };

vs.

function doSomething(id, options){ };

By encapsulating the 3 additional parameters into an options object and passing them individually, you make for cleaner code.

A quick caveat is to check the options object to ensure that all of the necessary properties exist before running your function.

  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Reddit
  • StumbleUpon
  • Technorati
  • Twitter
  • DZone
  • HackerNews