Using component.js about engine

[jasonkuhrt]

I will happily send a PR to update the docs at https://github.com/the-gss/the-gss.github.io once I understand correct component integration.

[d4tocchini]

I've been a little befuddled with Component.io lately. @bergie set the component things up, and I find myself bugging him about it more than I would like to. Component is being used for GSS's internal depedencies, but when I include GSS in another project I fall back to bower. PR's are more than welcome if you can help make this better!

[jasonkuhrt]

@d4tocchini @bergie componentjs is a solid idea initially pushed greatly by @visionmedia, and now @jonathanong. Things have been bit bumpy (reasonably so) on the road to 1.0.0, but I would wager there is a lot of benefit to staying the coarse here. bower to my knowledge does not solve as many problems as componentjs such as a module and build solution. As far as I can tell componentjs supports the unix-y/npm-y modularize-everything philosophy quite well. Wrinkles remain, I'm curious what yours are.

[jasonkuhrt]

Moreover bower is just version resolution and a fat git pull (no?) whereas componentjs has a far more nuanced solution on hand.

[bergie]

@jasonkuhrt yeah, Component.io has its good and bad sides. Especially plugin support is problematic (see for example the still-unsolved componentjs/builder.js#125 which breaks all plugins). They have a rewrite of the installation and building process, but that is still not quite production-ready, and includes severe usability setbacks, like requiring GitHub authentication credentials to install anything.

Despite these, I agree that we should ensure GSS is installable via Component. Is anything else missing than some files declarations?

[tj]

yea sorry guys :( it has been in flux lately since I haven't really been working on it (I'm not doing any front-end work lately) so things are getting a little crazy. The end-game is just to be better at supporting future web components etc, since that's where the future is going, component and browserify will disappear as they are today