pretty-gist feedback
Feedback on the approaches to pretty-gist, as described here. All questions are optional. The point of this is to make it easier for people to give feedback, so if you want to give feedback but this isn't the easiest way for you to do so, some other way is fine too.
Sign in to Google to save your progress. Learn more
Are you a Haskell user, broadly speaking?
If you're not, I don't know why you're filling this in, but feel free to anyway I guess
Clear selection
How cool do you think each version is?
Lame
Meh
Kinda neat
Cool
Classless
One-class
Two-class
Clear selection
And which do you think is coolest?
Clear selection
How likely are you to use each version?
Assuming it gets released as a decent-quality library
Unlikely
Maybe
Probably
Almost definitely
Classless
One-class
Two-class
Clear selection
And which are you most likely to use?
Clear selection
How annoyed would you be if you felt obligated to implement support?
E.g. suppose you maintain an unrelated library and you have users who want pretty-gist support
Not annoyed
Kinda annoyed
Very annoyed
Classless
One-class
Two-class
Clear selection
And which would be least annoying?
Clear selection
What would you want to use pretty-gist for?
Do you see ways to improve any of them without significant costs?
Do any of them have significant advantages or disadvantages I missed?
Can you think of other approaches that might work?
Anything else you feel like saying?
Submit
Clear form
Never submit passwords through Google Forms.
This content is neither created nor endorsed by Google. - Terms of Service - Privacy Policy

Does this form look suspicious? Report

Google Forms