News for hackers. Stuff that matters.
Re:Micropackages and Open Source Trust Scaling by tetha on Thursday March 24, 2016 @11:46AM (#11353735)
Thinking about this for the last few days, I think the Java SE / commons-approach seems the most sensible to me.

Your stdlib is bundled with the language runtime and contains binaries, OS interactions and the necessary fundamental stuff. Updating this is hard, because this depends on hard things like the OS, and because it must maintain compatiblity with everything.

However, the commons-package can add all kinds of pure (as in, just the language in question) stuff to the language, such as several dozens of collections, all kinds of utility languages, and so on. Updating this would be a lot less risky than updating the entire language runtime, especially if it uses proper semantic versions. This would allow this lib to iterate faster and include these utility-functions easier as well.

Re:Micropackages and Open Source Trust Scaling by dec0dedab0de on Thursday March 24, 2016 @12:01PM (#11353880)
The example that always drives me crazy is itertools in the Python standard library. In the documentation there is a recipes* section that lists 23 helpful functions, instead of just including them in the library

* https://docs.python.org/2/library/itertools.html#recipes

Re:Micropackages and Open Source Trust Scaling by talideon on Thursday March 24, 2016 @12:19PM (#11354057)
What's super frustrating is that Python 3 would've been an ideal opportunity to move those into the standard library, but it was never done.