Those examples are just clear indications that languages sometimes have really terrible default behaviors. Namely, Perl should have been strict by default (with a "no strict" if this didn’t perform well enough), and C++ should have at least added #import.
That's not what boilerplate code is, and DRY is not the way you get rid of boilerplate (the article claims it is a part of the solution).
boilerplate is a repeated preamble that's necessary and unchanging in order to get down to the business of actual logic.
An easy example of boilerplate would be include guards in a C/C++ header file, or 'use strict' in perl.
For example, the author says this:
> When I write Go, I noticed that my tweaks almost always go exactly where they naturally belong. My boilerplate doesn’t stay untouched!
If you're "touching your boilerplate" while writing code that affects the logic of your system, then it isn't boilerplate.