This article is *really* muddying a few conceptual things... you have your data, renderer and event handlers together with a class that really doesn't need to be a class. Even if you don't want to put yourself into MVC, there are lots of other patterns that are appropriate for user driven interfaces with events (personally, I like redux).
It's pretty bad advice and doesn't even demonstrate the concepts it's trying to clearly.