Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bower: A package manager for the web, from Twitter

twitter.github.com

Post reply on HN
Print view View original

41–45 of 45 posts

Re: Bower: A package manager for the web, from Twitter

#41

Post by benatkin »

dreamdu5t wrote: post #35
kahlil wrote: post #22

Earlier quoted context omitted.

The difference is that the component project depends on Github. Bower is much more low-level and unopinionated. All you need is a Git path.

That's because without using GitHub, Bower's packages aren't namespaced. This was something discussed at length on the component spec github. It sure feels like Twitter is avoiding giving credit where credit is due. No links to the component.json spec or any mention of TJ Holowaychuk's component feels smarmy to me.

His name is listed in the README. I think the next level of recognition would have been for him to contribute code, and for whatever reason, that didn't happen. It could be because TJ is busy doing other things, because development was closed, or because they disagreed on things, or a combination of reasons.

I looked at the source and found that the initial public commit contains 79 files.

Re: Bower: A package manager for the web, from Twitter

#42

Post by wilmoore »

necenzurat wrote: post #31

at least building failed http://travis-ci.org/#!/twitter/bower

The build is failing because there are a lot of moving parts at this early stage regarding the internals; however, the basics from a usage standpoint work just fine right now.

In other words, the build failing is not ideal; but don't get too hung up on it right now.

Re: Bower: A package manager for the web, from Twitter

#43

Post by tjholowaychuk »

dreamdu5t wrote: post #35
kahlil wrote: post #22

Earlier quoted context omitted.

The difference is that the component project depends on Github. Bower is much more low-level and unopinionated. All you need is a Git path.

That's because without using GitHub, Bower's packages aren't namespaced. This was something discussed at length on the component spec github. It sure feels like Twitter is avoiding giving credit where credit is due. No links to the component.json spec or any mention of TJ Holowaychuk's component feels smarmy to me.

I had a bit of a different thing in mind, my implementation is here https://github.com/component/component, it's certainly more opinionated, more of a framework almost, but solves more problems (of mine at least)

Re: Bower: A package manager for the web, from Twitter

#44

Post by tjholowaychuk »

MatthewPhillips wrote: post #32

NPM already provides this functionality and Isaacs has said that people should use NPM for client-side packages.

I'd definitely defend bower here, there's no reason to use npm for this, it just makes things confusing and ambiguous, and leads to stupid suffices or prefixes like the several "-component" modules I have

Re: Bower: A package manager for the web, from Twitter

#45

Post by vicapow »

substack wrote: post #13
streptomycin wrote: post #3

Does anyone think this can finally be the tool to bring sane package management to client side JavaScript development? I'm hesitant to use any of the existing tools because none of them support all the libraries I use, so I'd end up doing stuff manually anyway, and I don't have any confidence that any of them will keep working in the long term.

No. If anything, it will probably just get even more fragmented before the situation gets better. As we understand the features and architectures of package management systems better it becomes even easier to write package managers. This is a good thing long-term because we can more thoroughly explore the solution space before settling on a few "winners". However, at the same time package repositories are fundamental…

but dep management in the browser is still so different then the npm workflow. it's not just code you have to worry about, it's css/html/static resources
Post reply on HN