Comment 2 for bug 1621295

I guess my thinking, having played with it a lot over the past few
months as 2.0 has matured, is that "add-model foo" is very natural to
do, and means that you don't have lots of "default" models.

Another approach might be to name the initial model with the same name
as the controller.

But I think the big change of *explicitly showing* ongo and jujud in the
status mean that showing the controller model by default won't create
the illusion of having a blank canvas to work with. Initially, you would
bootstrap and see "nothing here", which made it tempting to deploy stuff
there.

Mark