Search This Blog

Minification is not enough, you need tree shaking

In which the virtues of automated mechanical arboreal pruning are extolled over quaint manual labor, as applied to web development build processes.

The setup

Ever notice how the primary bit of marketing for many traditional web programming libraries is their download size? Why is that?

Check this out:

Why does size matter so much for these libraries? Your first instinct is probably, "because the more bytes you shuttle across the wire, the slower the app starts up." Yes, this is true. I'd also say you're wrong. The primary reason that size matters for these libraries is because traditional web development has no intelligent or automated way to prune unused code so you can ship only the code that is used over the wire.

The web is full of links, yet web dev has no linker

The web development workflow is missing a linking step. A linker's job is to combine distinct project files into a single executable. A smart linker will only include the symbols and code that are actually used by the application, thus pruning unused code. The traditional web developer does not have an intelligent linker.

It's 2013, and the job of micro-managing web development libraries is still being done by humans. Humans: the same people that brought you this little gem. Web developers need machines and tools to take care of linking and minifying so they can get back to comparing traditional web development libraries based on actual feature sets instead of how femto they are.

I want my web programming language to offer enough structure and intelligent tools to take care of pruning, minification, and more. This is why I dig Dart, because it has the structure (classes, libraries, packages, type annotations, metadata, etc) and the tools (dart2js) for a modern development workflow.

Don't just prune unused code, shake it off

Dart tools support tree shaking, a technique to "shake" off unused code, thus shrinking the size of the deployed application. I can import rich libraries chock full of useful goodness into my application, but only the functions I actually use will be included in my generated output. Awesome!

Real code example, shaken not stirred

Consider this simple Dart library, ironically named embiggen. There are two top-level functions in this library, embiggen and unembiggen.

I love embiggen, but I'm less entralled with unembiggen and will never use it. Do I have to search for nano-embiggen?! Nay! Let the linker do it's tree-shaking magic.

Run the main application through the dart2js tool, which supports tree-shaking for both JavaScript and Dart outputs. Note there is no command-line option for tree shaking, because dart2js is always tree shaking. For simplicity's sake, let's generate Dart.

dart2js --output-type=dart embiggen.dart

Gaze into the tree-shook generated output (reformatted to make it easy to read):

Both outputs have unused code eliminated, and the minified version also replaces variable names. This is exactly the kind of help I want from my tools.

Why this works

The structure of Dart programs cannot change after compilation. In other words, Dart does not support altering class structure during runtime. Dart also does not have extreme dynamism like eval(). Dart compilers and linkers can assume more about the structure of the program, and thus can be more aggressive about tree shaking and minifications.

One option to consider is Dart, with its structured language and intelligent tools, like a tree-shaking and minifying compiler. With dart2js, you can import entire libraries, regardless of size, and generate only the code that is required to run the program.

Regardless of what language you use, demand more from your tools.

Acknowledgements

Thanks to Bob Nystrom's OSCON presentation from 2012, from which I humbly embraced-and-extended the setup of this post.

Popular posts from this blog

Now, this has to have a built-in somewhere in Scala , because it just seems too common. So, how to convert an Array to a List in Scala? Why do I need this? I needed to drop to Java for some functionality, which in this case returns an Array. I wanted to get that Array into a List to practice my functional programming skillz. **Update**: I figured out how to convert Arrays to Lists the Scala way. Turns out it's a piece of cake. val myList = List.fromArray(Array("one", "two", "three")) or val myList = Array("one","two","three").elements.toList The call to elements returns an Iterator , and from there you can convert to a List via toList . Nice. Because my first version wasn't actually tail recursive, what follows is a true tail recursive solution, if I were to implement this by hand. The above, built in mechanism is much better, though. object ArrayUtil { def toList[a](array: Array[a]): List[a] = { d

In which I port a snazzy little JavaScript audio web app to Dart , discover a bug, and high-five type annotations. Here's what I learned. [As it says in the header of this blog, I'm a seasoned Dart developer. However, I certainly don't write Dart every day (I wish!). Don't interpret this post as "Hi, I'm new to Dart". Instead, interpret this post as "I'm applying what I've been documenting."] This post analyzes two versions of the same app, both the original (JavaScript) version and the Dart version. The original version is a proxy for any small JavaScript app, there's nothing particularly special about the original version, which is why it made for a good example. This post discusses the differences between the two implementations: file organization, dependencies and modules, shims, classes, type annotations, event handling, calling multiple methods, asynchronous programming, animation, and interop with JavaScript libraries. F