Wouldn't call assembly programming "highly verbose". If anything it's opposite - very little boilerplate, if at all.
Do we have different ideas of what boilerplate is? Almost everything in assembly is boilerplate because there are no advanced, built in features. (Sure, modern x86 assembly is a complex language with many advanced builtins but they are generally meant to express solutions in the x86 domain, not the business domain.)
I stick to traditional definition.
> In computer programming, boilerplate code or boilerplate refers to sections of code that have to be included in many places with little or no alteration.
You will end up stitching highly verbose pieces of code. Which is why Java IDEs have specific features to emit get/set functions etc.
Plus you will have to access a method hiding 5 class layers below. You will need IDEs designed to do this sort of work really well.
Emacs and Vi have been designed to largely play with Text, plus I think with Java's verbosity you are just better off with a specialized IDE.