I don’t think it’s accurate to label that as a language problem. That is very squarely a people problem. It’s not as bad today - many Java juniors don’t have

I don’t think it’s accurate to label that as a language problem. That is very squarely a people problem. It’s not as bad today - many Java juniors don’t have the “bean” affliction burned into their brains so they don’t object to public fields on data carriers (today you’d just use a record) but even the bean generation (mostly people my age) can usually be won over these days by negotiating with them on cases where getters/setters can be eliminated (e.g. start with value objects, then suggest maybe DTOs then you can go for the kill - why do we need the stupid Java bean convention?)