re: GitHub Package Registry: What Does It Mean For Ruby Devs? VIEW POST

FULL DISCUSSION
 

I have concerns. Fragmentation and Privatisation

Fragmentation. Devs will ask which one should they use and before you know it there will be confusion. Not good.

Privatisation. Let's not forget Github/Microsoft are ONLY in it for the money. I'm guessing they're hoping that more devs will subscribe to paid plans - money.

 

In the same theme, I am thinking about centralization. Every service has its outages and the more that is tied into that one service, the more that is impacted when that happens.

Re: the money topic -- I'm torn on that one. If we accept the argument that they are in it only for the money, you could still say providing the best customer experience is in their monetary benefit, especially in a competitive marketplace, no?

code of conduct - report abuse