I wrote a little side project recently, called CSS3 Man. It’s a fun experiment in CSS3. You should check it out, it’s fun and interactive, and will be sort of necessary to understand this blog post.
I’ve taken to AngularJS recently for most of my little side projects. It’s super fast, simple, and every time I use it I feel like my apps give off this feel of “wow, that was really well done!” Most of that vibe comes from the data-binding, but from the developer end my favorite part is definitely directives. I wrote a tutorial awhile back on how to write an AngularJS directive, but now I want to write some words of caution on why they can be dangerious.
In CSS3 Man, I have to generate styles for each of the men on the fly. The requirements were that they can’t be stored in a file, they have to be dynamic, and they have to be dynamic fast. To do this, I wrote a directive called
superStyle. The direcive is given two attributes - a selector and the content (note: it wasn’t given pure CSS for XSS reasons). It would then generate style tags, insert them into the DOM, and watch the attributes to see when they changed. The code is below.
You might be wondering why I’m not using AngularJS templates and letting Angular handle the binding. Unfortunately, AngularJS templates don’t work with
style tags - which makes sense, and I’m fine working around it.
Anyways, I created a bunch of these for each human - one for head, body, legs, head-after, etc. It worked absolutely wonderfully in the editor. It loaded up almost instantaneously, and there was no noticeable delay between changing a CSS rule and seeing it show up on the preview. This was a great solution, and I was pretty excited to share it.
Later in the project, I decided that I wanted users to be able to submit their men so they would show up in the top world. That would make CSS3 Man feel much more interactive, and I was already generating these humans in a couple places - it should just be a copy & paste. Or, even better, a human directive. I figured that if I could create a
human directive that was passed the necessary CSS attributes, and then use a bunch of
superStyles to make them look right. Here’s what the directive template looked like:
And it worked! I put a man in the database, loaded it in via the API, and it showed up. Perfect! I figured I had that done, so I moved onto styling how it would look when I had a bunch of men on the screen (you know, spacing and such). As I was testing this, though, I realized that having 20 men load onto the screen took A LONG time. I didn’t know what was going on - AngularJS is supposed to be fast, I was using well-written directives, but it was super slow. I fought with it for awhile, and then decided that it was an unbeatable problem. I caved, and updated my code to animate the men in once they had loaded, instead of having a huge delay at first-load.
Development went on, but every time I loaded up the page I cringed, because the animation felt so cheesy. It was obvious that animating them in was just a hack because I couldn’t find a smooth alternative. Finally I decided I couldn’t live with that. If I couldn’t make the site work well, then I didn’t want to release it at all.
I finally came up with the idea that maybe AngularJS was having a hard time compiling all of those direcives. I realized that I have 10
superStyles in each
human, and 20
humans on the page. That’s 200
superStyles that AngularJS had to load. Although using directives is the right way to do AngularJS, I realized that perhaps it wasn’t the most efficient way. After trying out a few tests, I confirmed this was the issue, and started work on ripping out the
superStyles. Instead, I copied the
style generation code from
superStyle and dropped it into
human, but with one large
style, rather than 10 small ones. The new
human directive is below.
It worked! I was now loading in 20
humans, and there was no noticeable wait time on first load. The valuable lesson here is that, although AngularJS directives are awesome, they don’t necessarily scale well. Certainly my generation of
style tags was a heavy operation, but I think that this probably would have happened with easier templated directives. Be careful as you’re developing in AngularJS, and recognize that you may have to choose the hard way rather than the directive way, for the sake of your users.