Feels like solving a cultural problem.. but one that affects a large part of the software development community. The aversion to writing documentation seems pretty deep set in most developers :)

Perhaps I'm missing something obvious, but cannot a large part of this be addressed by significantly expanding the standard library? A favorite feature of mine in AWS CloudFormation is the ability when writing Lambda functions for the Python runtime to inline the code into the template and sidestep the process of generating and uploading code artifacts. This works because other than the (provided) boto3 SDK, I generally need nothing but the standard library.

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui...

Putting things in the standard library can greatly slow down their development as it upgrades when the standard library does and deprecating things can be more painful for library users because it is much easier to choose an older version of some boring library than of the standard library.

Then again, maybe one would want such things to slow down development

There is probably a _right time_ to start pulling more libraries into the standard library.

That comes with all of the downsides of significantly expanding the standard library.