Martin Dougiamas

Firstly, we're not forcing anything.  It's just a default.

But on the other hand, it's very stable for our needs already and should only improve as we keep bringing in the new versions from upstream.

We are not trying to do away with blocks. 

We are trying to make blocks unnecessary on most pages, meaning that you should be able to reach everything and use everything without them.

The big exception of course is dashboard which is completely blocks. 

Is that clearer now?

No, that's not come up yet.   Currently ANY block already works there and the institution can have complete control, or just set defaults and allow the user to add/remove blocks as they see fit.

What would you think would justify a special new plugin type?

"But why should we deprive those who access Moodle on a 20 inch display from blocks?" 

Boost is certainly not doing this.  It has a fixed block region that is always there.

What I was saying was that it should be for EXTRA or helpful info or shortcuts, and not things that are critical for students to finish the course (because of the possibility they will be on the mobile app).

If you like the deep-menu administration block you can keep it on for your site, no problems.  But it's just not a good direction to be the MAIN direction in the future, given the trends in interfaces everywhere all around us.

I'm looking forward to the user testing we'll be doing on Boost with 3.2 to see what comes out of it.

The exact numbers here will vary but are not important because the trend to mobile devices is extremely clear.  Just look around you at how you and the people are REALLY using the internet these days.  And AR is coming on fast .... 

I'm really looking forward to the UX research process ahead.