5 ms·
It looks like GitHub Discussions is sort of filling a similar niche--I'm guessing they're banking on being able to build that out for less than $1B--since they
by throwaway894345 5y ago
It looks like GitHub Discussions is sort of filling a similar niche--I'm guessing they're banking on being able to build that out for less than $1B--since they already have GitHub, they don't benefit as much from the StackOverflow user network / brand. I think that makes sense.
- zaptrem 5y agoEasy to build out the platform, difficult to build out the knowledge base (especially since so many areas have already been covered on SO)
- gervwyk 5y agoI must agree, their reach must be insane! Although my last question was like 3 years ago, I do visit it at least twice a week for quick answers. I feel like most “often asked” questions has been answered. I very seldomly find that creating a new question is necessary as most things is covered in past awnsers. However for package related problems, GitHub issues has become the go to.
- throwaway894345 5y agoSure, GH lags SO considerably on the size of the knowledge base, but I don't think that's very important since, due to the rapid pace of tech, content rapidly loses value with age (consider all of the jquery or flash content, or content pertaining to old versions of libraries or frameworks). What matters more is the rate at which content is generated, and I think GH has a pretty competitive story considering that people naturally want to ask the project maintainers/community questions directly (as evidenced by all of the GitHub Issues which are formulated as questions) and considering GitHub's significant share of those maintainers/communities. I posit that new content will increasingly appear on GH Discussions. Please don't mistake this for some exaggerated "GH is going to kill SO" argument--SO will do fine, but there is a compelling story for why MS wouldn't spend $1bn on SO.
- palijer 5y agoI'd say a lot of that stuff increases with value to an individual over time, but has less demand. Some of those SO discussions are the only references to ancient legacy code that is useful, when asking any questions about it today would not get any answers. So, depending on how we calculate value, if we ignore demand, it can be more valuable.
- travisjungroth 5y ago> Sure, GH lags SO considerably on the size of the knowledge base, but I don't think that's very important since, due to the rapid pace of tech, content rapidly loses value with age (consider all of the jquery or flash content, or content pertaining to old versions of libraries or frameworks). This is a weakness of SO and really the whole knowledge base business model (Q&A or not). You think you're building up this network-effect moat. "We have the best question-askers, answer-givers and answered questions. So everyone comes here!" But, knowledge goes stale. "How do you X in JS?" is different than it was 10 years ago. People don't want a historical archive of how it was 10 years ago, they want to know today! Then, like you say, GitHub brings in a whole new weird angle. Why ask on some other site when I have a spot where the maintainers and users hang out? Since my loyalty to SO is approximately zero, I'm just as likely to click on the Google result that takes me to GitHub if it looks more promising.
- throwaway894345 5y agoI think it's perhaps a little clearer to frame it this way: SO has a network effect moat, not a corpus-size moat (I don't know that SO was ever thinking the size of its corpus would stave off competitors--they probably were correctly assuming that their user-base was their moat). The network-effect moat keeps the rate-of-change of the corpus higher than competitors, which is where the value is (not the size of the corpus). This moat has held up really well apart from (maybe) GH Discussions, which seems (to me) likely to succeed because GH has a similarly large network of experts.
- travisjungroth 5y ago
- Wowfunhappy 5y agoCould they potentially integrate the existing StackExchange content, given that it’s creative commons licensed?
- shagie 5y agoFor people who read SO (rather than ask and answer), SO is useful in the places where the documentation is lacking. The way to integration that content into an existing project would be to document it better - possibly with a FAQ for development questions. That doesn't really need CC licensing (its helpful, but not essential) in that people who want to contribute documentation can already do so. Just pull up a SO tag for the library, find the top voted question, and figure out where it goes in the docs. Q&A shouldn't be used as an alternative to documentation.
- rhizome 5y agoAnd that's why this line of concern is worthless: SO already exists. GHD can refer to that all day long without having to reinvent the Library of Alexandria (which in hindsight could have used a backup, but still). Unless..."Prosus" pulls a Google+DejaNews and obscures SO's availability or paywalls it or, or, or...
- crispyambulance 5y agoSO is OK for very narrow questions that have concrete definitive answers. Unfortunately, SO's self-appointed police force will shut people down for any deviation from "the rules" (as they interpret them), or sometimes for no reason at all. Github issues, on the other hand, seems to be receptive to open-ended "why" questions which would be smacked down hard on SO. Github has a higher barrier to entry. You have to know where to go, but if you're in the right place it's a much nicer community with more classy and professional conduct. Also, it doesn't have a gamification aspect to it, unlike SO, and thus fewer irritating/persnickety types are attracted to Github because they can't really score points.
- robertlagrant 5y agoOne's about discussions; the other isn't.
- crispyambulance 5y agoSure, but BOTH about solving problems and getting answers. That's the important thing. The culture of SO become incredibly weird and IMHO will eventually sink it.
- robertlagrant 5y agoIf you zoom out far enough you can always find a shared level of abstraction, but I don't think that's helpful.
- onion2k 5y agoIn my experience probability of getting a useful answer, especially for a question about a specific library, is much higher on Github Discussions.