Live data from Hacker News

GitHub Package Registry

github.com

351–360 of 389 posts

Re: GitHub Package Registry

#351

Earlier quoted context omitted.

Please don't put support questions in issues!

Please have an alternative then!

If I post code to a GitHub, I'm happy for you to use it, and I'm happy to learn about bugs in the code. But what obligates me to facilitate support, or respond to support requests? People should grow up.

Re: GitHub Package Registry

#352

Earlier quoted context omitted.

True. I think people are pretty well accustomed to that though. Dockerhub, AWS ECR, Google Cloud, etc.

Yes and no. It affects software that's installed via things like Kubernetes pod definitions. You need to "relocate" images to the correct registry in that case. This is a sufficient hassle that one of my colleagues maintains an entire tool devoted entirely to this purpose: https://github.com/pivotal/image-relocation

Point being that Github doesn't really add any problem that doesn't exist in spades.

Re: GitHub Package Registry

#354
post #31

This is really outstanding. It will mean the death of Maven Central, about which I have mixed feelings. On the one hand, Sonatype deserves enormous thanks for what they have done for the open source world, as does mvnrepository.org. Their central repository has been free and maintained for a long time. Thank you, Sonatype. On the other hand, it took me three days to release a new version of one of my artifacts the ot…

Have you tried Bintray? [1] It's made by JFrog (makers of Artifactory), it's been around for while, it supports lots of formats including harder ones like apt, and it makes package distribution about as easy as it can be. [1] https://bintray.com/

While publishing to Maven Central may be onerous, there are good reasons for it, e.g. https://twitter.com/JakeWharton/status/1073102730443526144

Re: GitHub Package Registry

#355
post #330

Earlier quoted context omitted.

rad project allows you to create, checkout, manage, and publish a project, comprised of issues, patch proposals, and a git repo. Well hot dog. And it uses LISP for scripting? Nice. Interesting approach to saving state, too.: One only needs the address of the latest input, the "head", to be able to recover the whole log. The owner of a machine uses an IPNS link to point to the head of the list, and the name of this li…

It looks the business but it lacks the single most important feature for popularity: a GUI. GitHub made Git dominant by building a friendly GUI on top of it. Before, it was just another player in a relatively crowded field of CLI DVCSs. Obviously it is not essential to get stuff done, but anything with any ambition of generating network effects definitely needs a GUI. The other thing that seems to be lacking, from a…

> It looks the business but it lacks the single most important feature for popularity: a GUI.

It's a matter of perspective. My first thought when reading the docs was, "All someone needs to do is slap a GUI on this baby. Good thing the designers made a simple CLI that it could interface with."

They've already done most of the heavy lifting. At this point a GUI is trivial to add. "Terminal–first" doesn't imply "terminal-only". In fact, quite the opposite. I wouldn't be so quick to assume that they don't envision a GUI at some point-- Why not contribute to the project and get the ball rolling?

The patch command [0] has a propose subcommand that describes what you're talking about. It generates a patch from a commit (on any branch, I presume). This can be applied however you see fit. And the checkout subcommand even lets you generate branches from patches similar to GH. What seems to be missing?

[0] https://radicle.xyz/docs/#rad-cli-reference

Re: GitHub Package Registry

#356
post #143

Earlier quoted context omitted.

> the two major search engines What's the second major search engine? I'm genuinely asking, not meaning to poke if it's Bing - I use DDG but just don't have a feel at all for what's most popular after the obvious one. Wikipedia has just 7% market share left for the second, and the rest - thinking about it's probably one that's popular in China and unheard of elsewhere?

What is the first search engine? Baidu in China. Yandex in Russia. Google in the US. Not sure for India and Latin America. The poster was probably thinking of Bing though, which is ironic because it's maybe less used than these.

I was assuming a global perspective, for which Google is obviously first. (And I quoted Wikipedia confirming that at a shade under 93% market share.)

Re: GitHub Package Registry

#357
post #330

Earlier quoted context omitted.

It looks the business but it lacks the single most important feature for popularity: a GUI. GitHub made Git dominant by building a friendly GUI on top of it. Before, it was just another player in a relatively crowded field of CLI DVCSs. Obviously it is not essential to get stuff done, but anything with any ambition of generating network effects definitely needs a GUI. The other thing that seems to be lacking, from a…

> It looks the business but it lacks the single most important feature for popularity: a GUI. It's a matter of perspective. My first thought when reading the docs was, "All someone needs to do is slap a GUI on this baby. Good thing the designers made a simple CLI that it could interface with." They've already done most of the heavy lifting. At this point a GUI is trivial to add. "Terminal–first" doesn't imply "termin…

I agree that the GUI situation is a glass-half-full sort of thing, I'm just saying it needs that as a priority if they want any network effect.

> The patch command [0] has a propose subcommand that describes what you're talking about.

Yeah but in the tutorial it says it will fail to work if you are on a different branch from master - I took it to mean that the patch command can only target the same branch it was generated on. If that's the case, obviously the maintainer can then do the manual merge-and-delete routine; I'm just saying that on github it's a one-click operation.

Re: GitHub Package Registry

#358
post #356

Earlier quoted context omitted.

What is the first search engine? Baidu in China. Yandex in Russia. Google in the US. Not sure for India and Latin America. The poster was probably thinking of Bing though, which is ironic because it's maybe less used than these.

I was assuming a global perspective, for which Google is obviously first. (And I quoted Wikipedia confirming that at a shade under 93% market share.)

Funny thing, you're describing exactly why you're not assuming a global perspective. Forget about a first, the world is fragmented. To be global is precisely to cater to individual locations around the world.

If we are to believe these stats, Google is at 3% market share in China. It's basically non existent. http://gs.statcounter.com/search-engine-market-share/all/chi...

Microsoft has developers everywhere in the world, who need docs. There are major search engines besides Google and Bing.

Re: GitHub Package Registry

#360

Earlier quoted context omitted.

What if they clash (eh user/package exist both on npmjs.com and GitHub)? Does it go through each of the configured repositories in sequence looking for a match?

You configure the NPM client on what your primary registry is. I think this github repo will mirror everything on NPM (?).

That will cause crashes between username scopes on npmjs and GitHub
Post reply on HN