Micro grained name space

Before dependency managers, publishing an eight-line code library would have been unthinkable: too much overhead for too little benefit. But NPM has driven the overhead approximately to zero, with the result that nearly-trivial functionality can be packaged and reused. In late January 2019, the escape-string-regexp package is explicitly depended upon by almost a thousand other NPM packages, not to mention all the packages developers write for their own use and don’t share.Dependency managers now exist for essentially every programming language. Maven Central (Java), Nuget (.NET), Packagist (PHP), PyPI (Python), and RubyGems (Ruby) each host over 100,000 packages. The arrival of this kind of fine-grained, widespread software reuse is one of the most consequential shifts in software development over the past two decades. And if we’re not more careful, it will lead to serious problems.

Right, an ongoing program for two decades.  Then he goes into security and management issues, which i don;t ignore except to push them w and onward.

I think that ten line code might be excessive, but certainly we should design for 100 lines of snippet code. The snippet containing multiple ten line elements.

As far as where these snippets are, they are identified by common plain text names in an enterprise dictionary, their loadable element has the same name, it is their name space name, their entry point.  Folks in the enterprise need named rectangles to display anything at all to a particular user. If you don;t have named rectangles then you have layers of bloat needed to put up a chart.  So, everyone use the company  xchars package. A 300 line snippet, well tested from a number of suppliers , the various xchars  all supply named rectangles with text methods and overlays for charts and graphs.

Why have a dozen different syntax engines do namespace differently? let us deploy a n enterprise name space technology, gets u down to snippet level, with common formats.  All the engines can easily adapt their own import of using, or whatever.  Just create  a plain text grammar command language, and let it define the name space grammar.