The author has identified a real problem in the JavaScript ecosystem, but I think his solutions miss the mark. Firstly the distinction between library and appl

The author has identified a real problem in the JavaScript ecosystem, but I think his solutions miss the mark. Firstly the distinction between library and application less important than he supposes. In the case of something like Babel, it can be both. There are just two interfaces to the same functionality. The errors he saw with Babel are obviously bad, but that seems to be a symptom of implementation. Dropping configuration in favor of convention is a dangerous suggestion. Magic is great until it breaks, and when that happens you've created an opaque mess for the end user. I still have configuration, it's just implicit, undocumented, and spread throughout my environment.