this post was submitted on 23 Jul 2023
7 points (100.0% liked)
A place for the LGBTQ+ community
24 readers
1 users here now
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That second one really seemed to miss the point of non-binary and thought they could get around it by just using the gender binary multiple time.
I think the proper solution is to create an abstract gender class and leave it to the user to implement their specific gender.
That’s not very user-friendly. And impractical for >99% of users.
Users in this case would be other devs using the gender library. They should have enough technical knowledge to handle it.
You could also include common gender implementations in the library. Then we could start getting enterprise^tm^ and include a GenderClassFactory that constructs Gender classes.