Rationale for dropping ModuleImport syntax?

[Domenic Denicola]

From: Axel Rauschmayer [mailto:axel at rauschma.de] 

> Isn't the problem, though, that default-exporting an object prevents static checking? It feels like an abuse of this feature to me.

We don't have static checking today, so this is no loss to me. (And ES6 modules give enough benefits over ES5 ones without static checking to still have a chance in the marketplace, e.g. they statically require imports being at top-level and string-only, and automatically introduce `"use strict"` for you.)