It occurs to me that part of this debate could be expressed in more modern terms as Declarative vs Imperitive programming. In firstclass languages a complex pr

It occurs to me that part of this debate could be expressed in more modern terms as Declarative vs Imperitive programming. In firstclass languages a complex problem can be solved by chaining together functions and can be written in a single statement (this depends on the implmentation of functions and types that are returned). Somtime 2 or three statements. Versus using core language statements and packages to implement conditional logic, control structures, and operations. Relying less on packages that extend the launguage. Having full control over the implementation. Personally I prefer declarative and wrapping it with verbose inline documentation. One downside to this is maintaining the build environment. Packages are versioned and fucntions change overtime (deprecated in favor of new implmentations that replace the old function). Somtimes Declaritive implementations must be refactored to support newer version of packages. Impertive implementations tend to be more durable and have fewer dependencies.