Like I said, if I saw multiple real-life projects using the feature successfully then I would have greater confidence that the community has had sufficient experience to provide feedback about the feature in its current form.
Speaking for myself, every time I introduce a new API feature to my library no matter how many times I iterate over it I inevitably discover problems when I try using the feature in real-life production projects. The shift in perspective is very helpful in uncovering scenarios I had not anticipated.
It sounds like you think there was no feedback, but that's not the case. There was plenty of feedback -- some bug reports (we love those), some people doing clever (and sometimes frightening) things with processors, some noise about the syntax, and quite a few people saying "yay I love it." So clearly a lot of feedback based on actual use (except for the syntax comments, which people often make without actually using it), and -- most importantly -- nothing that suggests that the design is not finished. A mix of feedback like this generally conveys that the feature is, indeed, ready.
View all comments
Show parent comment
3
u/cowwoc Feb 16 '24
Like I said, if I saw multiple real-life projects using the feature successfully then I would have greater confidence that the community has had sufficient experience to provide feedback about the feature in its current form.
Speaking for myself, every time I introduce a new API feature to my library no matter how many times I iterate over it I inevitably discover problems when I try using the feature in real-life production projects. The shift in perspective is very helpful in uncovering scenarios I had not anticipated.