Hello,
@seangriffin at last workshop mention the http://prioritized.net/blog/gemify-assets-for-rails/
which is nice, but I’m still curious what is the advantage for wrapping assets into the gems instead of just vendoring them under the lib directory, especially when all you need is just that script?
Thanks.
The benefit for a single project is pretty minimal. It lets you keep a third party library out of your source control, which personally I can’t stand, but that’s about it.
However, it’s extremely quick to gemify a library if one doesn’t already exist, and it’s a decent benefit to the community. It makes it a single command to install or update a gem, rather than downloading and copying a file, makes it much easier to specify a version (again, rather than searching for a version archive), and also allows you to specify dependencies (e.g. backbone-on-rails with underscore and eco).