5 ms·
This comment is *not* an explanation of why the feature was problematic in its current form, and portraying it that way makes the JDK team look far more politic
by pgwhalen 2y ago
This comment is *not* an explanation of why the feature was problematic in its current form, and portraying it that way makes the JDK team look far more political than they actually are. The comment is just explaining why feedback from usage is better than comments just looking at syntax.
A sibling comment links to the actual technical discussion and reasoning.
- AhtiK 2y ago"We discovered, unfortunately quite late in the game, that the design was flawed."
- favorited 2y agoThat's an explanation of why the feature was pulled, not of why it was problematic in its current form.
- unlikelytomato 2y agoI understand where you are coming from, but it is a very good signal for the team. The easiest way to get the desired feedback would probably be to adequately address to the current community concern.
- pgwhalen 2y agoIt is very well addressed, in the right forum (on the OpenJDK mailing list). It's a bit uncharitable to cherry pick a reddit comment on a specific thing and portray that as the public messaging on the technical decision. I want Brian et al. to comment more on reddit threads, not less, but this sort of interpretation is a reason for him not to.
- unlikelytomato 2y agoI'm not taking a particular stance on the JEP. I am not sure what is being cherry picked. The comment explicitly called out the customers for creating antihelpful noise. In my eyes, that tells me there is deep value misalignment between the involved parties, which is worth reflecting on.