Fun question to stir up the channel... At what po...
# compose
c
Fun question to stir up the channel... At what point do we just use stackoverflow to make sure all of these great answers from the Android dev team (and others) are actually searchable? With compose beta, the api is now "stable" so should we start moving more questions there (and maybe post the questions here if they don't get traction?)
๐Ÿ‘ 1
a
you all have fun with that; I stopped answering questions on stackoverflow ~8 years ago or so after people with high enough karma scores started editing my answers, "for clarity" and made them subtly wrong in the process ๐Ÿ™ƒ
๐Ÿ˜ฎ 9
๐Ÿ˜ž 7
๐Ÿ‘† 2
c
No Adam Powell on SO? Alright, slack here I come!
๐Ÿ˜‚ 5
j
You mean you don't like seeing the same question multiple times a day and being forced to use a subset of the chat tools by being forced into threads?
Whoops not to mention being an information solo from, ironically, the search engine also built by the same company
c
Wouldn't something like github discussions be a good alternative ?
j
GitHub had a habit of only half implementing a feature. If you wanted threaded discussions then discourse is great. I've used it for Rust and Swift and even Kotlin has one. You can reply to months-old topics and see which are actively discussed.
๐Ÿ‘ 1