Java has it's problems, but I think they're mostly on the implementation side (e.g. lipservice to OOP while having a load of AbstractFooHelperFactories or leaki

Java has it's problems, but I think they're mostly on the implementation side (e.g. lipservice to OOP while having a load of AbstractFooHelperFactories or leaking all your inner workings through Getters and doing "Ask, Don't Tell" rather than vice versa) but I don't get why people rail against the "boilerplate" so much. It's just signposting, you can learn to look past it so soon it makes no difference. I play music and don't need the treble clef on the stave to tell me what notes to play — you could call that boilerplate and get rid of it, but I don't think it would make it easier to play or read