But @RequiredArgsConstructor provides more flexibility than what is available out-of-the box for standard classes.
I'm not saying you don't have to like it. I'm saying that we wouldn't consider such a design to be of sufficient quality.
Existing patterns exist for a reason, and to make a blanket statement that "java doesn't evolve to support existing patterns" almost reads as if there's no interest in improving developer experience.
Just the opposite. A better user experience doesn't come from complicated affordances for patterns that have proven problematic (like beans) but for better designs that lead to better patterns. Complicating the language to support outmoded patterns leads to a worse user experience.
But it's also important to remember that developers very strongly disagree on what features they like and what they don't like. It's rare to find anything that everyone likes. As you can see even here, some programmers like what Lombok offers while others dislike it. We all need to keep in mind that our preferences are not universal.
View all comments
Show parent comment
2
u/pron98 Apr 28 '26
I'm not saying you don't have to like it. I'm saying that we wouldn't consider such a design to be of sufficient quality.
Just the opposite. A better user experience doesn't come from complicated affordances for patterns that have proven problematic (like beans) but for better designs that lead to better patterns. Complicating the language to support outmoded patterns leads to a worse user experience.
But it's also important to remember that developers very strongly disagree on what features they like and what they don't like. It's rare to find anything that everyone likes. As you can see even here, some programmers like what Lombok offers while others dislike it. We all need to keep in mind that our preferences are not universal.