I'm struggling to understand how Github's new pricing has gotten so untethered from the value curve. Curse of the Monopolist?
-
-
Replying to @wycats
Blame node and "small modules." Value per repo now wildly divergent between communities.
2 replies 0 retweets 5 likes -
Maybe they didn't get it right, but per-user captures value better IMO.
1 reply 0 retweets 6 likes -
Replying to @tomdale
strong disagree. value-per-user curve is high for the first few and lower and lower as you go on.
1 reply 0 retweets 2 likes -
this means you are unlikely to add low'ish value users, which brings down the total quality of the service.
2 replies 0 retweets 7 likes -
it also means that people will do things like 'maybe everyone can share a single push token' and 'maybe X is better than GH issues'
1 reply 3 retweets 0 likes -
which also reduces the value of the service
5 replies 0 retweets 1 like -
but that's based on traditional customers that are companies. Harder to reconcile with FOSS orgs, loose communities, etc.
1 reply 0 retweets 0 likes -
I added the Rust core team to
@skylight so they could look at it and help me. I wouldn't do that with the new model.2 replies 0 retweets 0 likes
and I think that makes GitHub a worse service, full stop.
-
-
it also means that people will be looking for other services for these cases ("let's use gitlab for casual users")
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.