would be great to think about refactoring this into a module -- it could accept a parameter for speed. We may want to start thinking about a type of module that is an "export module" which produces an output which is not assumed to be chainable. Like, a GIF maybe could be chained but it raises some questions... but say, modules to export to PDF, or SVG, or perhaps to display an interactive graph... these aren't super common, but they do break the rule that modules should return a data-url raster image. But they still might benefit from standardization as a kind of module, you know? For example, accepting input parameters as in this case. What do you think? What if we tried refactoring the GIF code to be a kind of "export module" - a module which terminates the sequence? Then sort of learn from the experience to think about a standard type of "export module"?