Unrelated to my previous toot, is there a reason git and github are so opaque and nerve-wracking to deal with? Is it a hazing ritual?
Conversation
Notices
-
Embed this notice
Epidiah (epidiah@dice.camp)'s status on Wednesday, 02-Oct-2024 06:08:39 JST Epidiah
-
Embed this notice
clarity flowers (clarity@xoxo.zone)'s status on Wednesday, 02-Oct-2024 06:08:37 JST clarity flowers
@Epidiah git is a cobbled-together hack built for a specific in group with specific material concerns that are not nearly as universal as people generally make them out to be. it's like, say, if a particular class of obscure and hard-to-learn wargaming was presented as the obvious and friendly default for playing make believe with your friends.
-
Embed this notice
clarity flowers (clarity@xoxo.zone)'s status on Wednesday, 02-Oct-2024 06:10:35 JST clarity flowers
@Epidiah github is an embrace-extend-extinguish attack on git attempting to enclose a huge segment of under-exploited surplus labor. it's opaque because it's built on git, but tries to "simplify it" in a way that only ends up making things more complicated because now you have "the git way" and the "github way". And github wants you to think their way is the only way but git (as an org) doesn't actually agree and has different interests/agendas
-
Embed this notice