I have feels
-
-
Replying to @Carols10cents @withoutboats and
I'm generally against namespacing because I think they create more problems than they solve, but this sub-crate thing is interesting
2 replies 0 retweets 3 likes -
Replying to @Carols10cents @withoutboats and
i also have feels. mostly that you'd be surprised how few people will actually use it (i'm speaking from experience at npm)
1 reply 0 retweets 3 likes -
Replying to @ag_dubs @Carols10cents and
I wonder if there are ergonomics or awareness issues in the npm implementation. I feel like I would use it, but I may be wrong.
1 reply 0 retweets 1 like -
Replying to @withoutboats @Carols10cents and
i think the main thing is that between http and ag_dubs/http, http seems more official (this is purely my conjecture)
1 reply 0 retweets 4 likes -
Replying to @ag_dubs @withoutboats and
Is npm's namespacing restricted to username-roots, or can people use arbitrary package names?
1 reply 0 retweets 1 like -
Replying to @hdevalence @withoutboats and
username or org routes, many people will make a org for a package with many subpkgs, e.g. angular
1 reply 0 retweets 0 likes -
Replying to @ag_dubs @withoutboats and
How common is namespace use when weighted by package popularity?
2 replies 0 retweets 0 likes -
Replying to @hdevalence @ag_dubs and
I mean, if large projects use org namespacing to organize their packages, I would expect that namespaced packages are fairly commonly used?
1 reply 0 retweets 0 likes -
Replying to @hdevalence @withoutboats and
i'm in a meeting but would be down to talk about this in like a github issue or something! need more characters
2 replies 0 retweets 2 likes
I've been planning on writing an RFC on this for a while and would love to get these stats from you for that @ag_dubs
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.