Hey Folks 👋
Not sure if this is the correct channel, but I am desperately looking for feedback on how to improve the README.md of my library here:
https://github.com/sellmair/evas
e
eygraber
08/09/2024, 9:09 PM
"How to improve" meaning what are the generic steps you can take to improve any README, or how to improve the README for this specific repo?
m
MV
08/09/2024, 10:40 PM
Maybe a comparison (like pro/cons) between "competitors" like flows, channels, mutableState. I.e why would I choose this library over the "status quo"?
😃 1
s
Sebastian Sellmair [JB]
08/10/2024, 7:37 AM
Basically I am looking for some kind of advise:
I think I am failing to explain what it is and how to use it in the readme?
e.g. its not competing with coroutines, as it will happily return a flow and bind to mutableState. It competes with ViewModel instead
Sebastian Sellmair [JB]
08/10/2024, 7:37 AM
I think comparing an application written with a ViewModel vs evas is a great idea!
c
christophsturm
08/10/2024, 12:35 PM
I think the first sentence in the readme should state a problem and how evas solves that problem.