I honestly don't get this article. From the first looks, it seems like some CSS framework has its own build system now. Fine. (BTW, I thought SASS was a languag

I honestly don't get this article. From the first looks, it seems like some CSS framework has its own build system now. Fine. (BTW, I thought SASS was a language, not a build tool). But the second half of the story is a complete mystery to me. I read stuff like > Enter the absolute url containing your style within “external assets”. So ... are you hosting my code on your site? Why would I ever want to trust some external site to host my CSS? Or am I supposed to use the picnicss build logic to create my own concatenated CSS files? If I am supposed to do it locally, what's the advantage over using grunt/gulp and simply include the (previously downloaded) picnicss files? > 5. [optional] Set the option “fresh” if you are developing it, to keep updating the style on each call. How? When I develop, my code runs on somesite.local, so you can't possibly fetch the code from my localhost. And even if I used it on some public-facing development site, this roundtrip would dramatically slow me down. Changing the build logic to provide a single CSS file containing Picnicss is a fine thing to do, but I don't get all the future plans and stuff. And I haven't learned a single bit about why doing the CSS magic on demand via Express is a good thing, what challenges you had to overcome and what to take home from this.