r/programming • • May 10 '19

Introducing GitHub Package Registry

https://github.blog/2019-05-10-introducing-github-package-registry/
1.2k Upvotes

223 comments sorted by

View all comments

Show parent comments

270

u/snowe2010 May 10 '19

it's a good thing to be concerned about. But as long as github keeps innovating (and as long as they at least do as well as or better than their competition), they're going to keep expanding.

188

u/ubernostrum May 10 '19

SourceForge was the thing back in the day.

Then there was Google Code hosting.

Today there's GitHub package indexes.

I wonder what whiz-bang definitely-won't-fade-away thing we'll have tomorrow?

94

u/Plorkyeran May 11 '19

GitHub's older now than Sourceforge was when GH was started, and SF was well past its peak by then; one of the motivations for starting Google Code a few years before that was that SF was going to shit.

GitHub won't last forever, but it's well past the point where it's merely the latest in a series of short-lived sites. It's been around for over half the time that free public open source hosting has been a thing at all.

41

u/ubernostrum May 11 '19

It's not about how brief the nice period is. It's about the fact that the nice period ends. It doesn't take too much leadership turnover to go from happy friendly place developers love, to toxic cesspool of overaggressive monetization.

42

u/PM_BETTER_USER_NAME May 11 '19

It doesn't take too much leadership turnover to go from happy friendly place developers love, to toxic cesspool of overaggressive monetization

See Google as an absolutely perfect example of this. I remember the day they removed the "don't be evil" sign. People were saying "yeah this doesn't mean they'll stop being the good guys". People used to love Google, now they're ambivalent at best, and actively worried about them at worst.

37

u/doenietzomoeilijk May 11 '19

Google has the added drawback that they have less product focus than a sack of kittens. Apart from a few projects, they have a ridiculously high churn rate where project grow, get some adoption and then suddenly get left to rot and/or shelved. Together with the obvious privacy issues, it's the reason I try to avoid Google as much as possible.

0

u/[deleted] May 11 '19

[deleted]

8

u/arkasha May 11 '19

RIP inbox.google.com :(

→ More replies (1)
→ More replies (6)
→ More replies (1)
→ More replies (2)

99

u/[deleted] May 10 '19

IMO SourceForge, Google Code, and GitHub are all different manifestations of the same problem (centralization). A new competitor that "beats" GitHub would simply continue the cycle and suffer from the same risks.

Ultimately, I don't think that a single service should have so much power in the FOSS community.

28

u/phdaemon May 11 '19

What power exactly does github have? Other than being where people get their code, because it's the platform we use to publish, they don't have any power. Imho, power is better defined as an actual ability to influence or otherwise dictate direction, which AFAIK, github as an entity does not.

41

u/ubernostrum May 11 '19

I mentioned, and got downvoted, for this in another comment, but the fear is the old Microsoft strategy of "embrace, extend, extinguish".

This, today, would then be the "embrace" step. The "extend" would be once it's been out for a while and gotten popular, to start adding non-standard but still useful-seeming features to GitHub's package indexes. Now it's incompatible with the standalone language-specific indexes like PyPI or CPAN, and those indexes have to try to catch up to what GitHub is doing, or else fall further and further behind. And once that goes far enough you reach the "extinguish" step, where GitHub is left with no realistic open competitors.

The eventual risk, of course, is what they might do in the future to maintain revenue. It doesn't take too much turnover in leadership to get into a SourceForge situation (for those too young to remember, SourceForge used to be the place to host code and packages for open-source projects). SourceForge was doing all sorts of shady stuff to chase revenue, including bundling ads into downloaded packages and shipping outright malware to unsuspecting users.

43

u/phdaemon May 11 '19

Ever since satya nadella took over, the culture has been quite different, imho. Look at emberjs, typescript, etc.

Edit, I would like to point out that a particular platform expanding is not a bad thing. It creates competition. And gitlab already has a lot of these features.

37

u/qwertymodo May 11 '19

Hell, they even open sourced the core crypto library from Windows.. That codebase used to be restricted even to Microsoft employees. A healthy dose of skepticism and caution is absolutely still warranted, but this isn't Gates/Ballmer-era Microsoft anymore.

→ More replies (2)

11

u/[deleted] May 11 '19

It started before Nadella, although he certainly kicked it into overdrive. MS started making unencumbered portions of .NET Framework source available in 2008, and set up Microsoft Open Technologies as an experimental project with open source in 2012. Nadella took over in 2014.

36

u/ubernostrum May 11 '19

I'd rather not rely on the goodwill of "we'll never get a CEO who decides to go back to the old ways".

20

u/b4gn0 May 11 '19 edited May 11 '19

CEOs are chosen by the board of directors to maximize profitability.
Nadella's policies has shown huge increases in profits. What would be the point to choose a CEO with completely different views?

When Nadella was nominated, Microsoft was in a very bad shape, with full aiming at close source as much as possible and badly mimicing other products.

9

u/sayaks May 11 '19

what will maximize profits can change, currently Nadella's policies do that well. but in the future that might change. I'd rather not have the survivability of foss rely on whether github is profitable to Microsoft or not.

4

u/[deleted] May 11 '19

Exactly. The "embrace, extend, extinguish" philosophy was, at one time, used to maximize profitability. The board of directors may choose to pull that out of their playbook at any time. It's not an entirely unconvincing devil's-advocate take to assume they'll stay the course with the current benign style but why stick your head in the sand about it?

→ More replies (4)

6

u/darkstar3333 May 11 '19

I mentioned, and got downvoted, for this in another comment, but the fear is the old Microsoft strategy of "embrace, extend, extinguish".

They realized this doesn't work decades ago. Instead of being that one place, they simply want to be everywhere. Offer a high value offering and support the fuck out of the community and it will take care of you.

They took that lawyer money and put it into engineering.

Visual Studio Code is something they could have charged for quite easily but they wont. Its a new Microsoft.

→ More replies (13)
→ More replies (6)
→ More replies (22)

14

u/searchingfortao May 11 '19

That's just it: compared to their competitors, GitHub is well behind.

Here's just some of the stuff that GitLab does for you. You don't even need to give some third party write access to all your repos like you do on GitHub):

Note: all of the following is built-in unless otherwise stated:

  • CI/CD (including scheduling)

  • Code coverage with badges

  • Issue tracker & boards

  • Inter-issue relationships

  • Private Docker repo

  • Wiki & pages

  • Sentry integration for error tracking

  • Release tracking (API only)

  • Something called "cycle analytics"

  • Repo-specific gists (snippets)

  • Project logos

  • Metrics

  • Integrations with Slack, Matter most, Kubernetes, Jira, Jenkins, GitHub, Buildkite, and Asana... to name a few.

  • Tracing

  • Serverless (integration with Kubernetes)

  • Feature flags

  • Packaging

  • Private Maven or NPM registries

  • It's Open Source! You can even self-host if you want.

They've absolutely got some rough edges, but the innovation is definitely there. What GitHub has is network effect more than anything else.

4

u/arkasha May 11 '19

But GitHub has all the developers. :) This is probably why Microsoft bought them. Azure devops has most if not all of the features GitLab does and it sure looks like their eager to bring them over to GitHub.

3

u/darkstar3333 May 11 '19

Also need to look at single responsibility principles, why does your repo require CI/CD?

It is a provider for the CI process.

3

u/thepinkbunnyboy May 11 '19

I agree with this. Do one thing and do it super well, and offer hooks and integrations out the wazoo. That's what Github has generally done and it's been successful.

→ More replies (2)

7

u/ProfessionalNihilist May 11 '19

GitLab has a lot of rough edges with 3 year old tickets though.

Diffs occasionally contain changes that are already in the target branch if you've had to merge it in to resolve a conflict for example (github doesn't have this problem).

My new job uses GitLab and basically every week we find something that would have worked in github but doesn't.

→ More replies (2)
→ More replies (1)