Divergent manifest standards
jackmoore opened this issue · comments
Has there been any talk with the Twitter Bower guys for standardizing package manifests? Since Bower and jQuery plugins seem to have very similar requirements for packages, it seems like a opportunity for a cooperation.
We started our public manifest discussions in December 2011. Bower wasn't announced until September 2012. Even today, Bower doesn't support all of our use cases, such as hosting a suite of plugins in a single repository. This just isn't going to happen.
Think of the children. 👧 👦
I realize the timelines are way diverged, but there's a huge question mark of how developers are going to cater multiple package vendors in the future. Ideally, we could work towards a standard that allows for flexibility for vendors, as well as practicality for the developer community. This could happen! 👼
@desandro 100% agree, I can't live in a world where Java has one file that does it all (defines the package, the build, the dependencies, the assets, components, the tasks and what not, named pom.xml) and JavaScript doesn't even have an agreed package format to rule them all.
yes I know, maven is xml and it's Java after all. but I can't live with the fact that a JavaScript project (browser more than server mostly) is more complex to structure than a Java one. It's great to have many standards and initiatives but it has to converge to some agreed version, developers need to choose between too many things, CommonJS (with browserify) vs AMD, npm vs component vs bower (that uses the same component.json filename but is not compatible) vs volo, ender, jam, grunt, brunch yeoman and what not.
I guess it's a good sign, lot's of smart people trying to make the world right, but I think that if JavaScript is the future, it doesn't make sense that it's more complex to manage a JavaScript browser project than a Java one.
This really could happen 👼 hope the community join forces
It's great to have many standards and initiatives...
Let's be clear. There are no standards bodies that have put out a specification for a module system. There is one in the works for future ECMAScript, but CommonJS/AMD/whatever is not a standard and there is no official spec for anyone to be following right now.
CommonJS (with browserify) vs AMD, npm vs component vs bower (that uses the same component.json filename but is not compatible) vs volo, ender, jam, grunt, brunch yeoman and what not.
Some of these things started before the plugins site, some after. Some have nothing to do with this discussion or are actually duplicative.
This really could happen hope the community join forces
Keep waiting. Nobody agrees on anything. You'll need a standard and then a few years on top of that.