Interesting claim: to what extent does OO promote setters simply to avoid unwanted/accidental mutation? From
miniblog.
Related Posts
Watching https://youtu.be/KWB-gDVuy_I and I'm struck by how weird constructors are as an API.
* They promote total functions, making it hard to do validation.
* They're hard to split up, because they have special access to unfinished data.
* They're like a framework: you get called.
Do you think language/API docs websites should support comments?
Pros: Adds context, familiar format, engages community
Cons: Can disincentivise contributions, comments might promote bad practices
I've only seen PHP and clojuredocs offer this.
It's interesting that Twitter sets limits on content size, but not distribution.
What if the number of retweets/comments on a tweet was rate limited, or had a cap for new users Would it promote slower or thoughtful conversation?
C.f. Stack Overflow limiting new user abilities.
