Is Small Still Beautiful?
lambda-the-ultimate.org
lambda-the-ultimate.org
Orthogonality (or representational independence), not size, is the relevant criteria. Harmonic analysis is the appropriate comparison. While every complete basis can represent any function in the relevant function space, it is better at representing some than others; notably the functions which are a finite linear combination of the basis functions. So trigonometric series represent one kind of function very efficiently, wavelets another. It's similar with programming languages.
Of course the orthogonal core may be mostly of interest to the language implementer,as orthogonality should, in the most faithful sense of the word, make the implementation of one construct independent of implementing another construct, particularly in optimization.
Regardless, I think the post is postulating that a large, overcomplete "basis" is the new beauty de jour.
The standard library should be comprehensive and well documented so that it's easy to (1) decide if there's a package that does what you want, and (2) work out how to use it. Simply documenting all the functions/methods on an API is not enough; documentation should start by saying what problems the module is trying to solve, then give some worked examples. If the worked examples don't give a bloody good idea of how to use it, then probably either the package is badly designed or the documentation badly written.
There are libraries in Python that I have given up on using simply because I've not been able to figure out how to use them.
Basically, the difference between "language" and "library" is normative. What you put in "language" are requirements for conforming implementations. It is a political decision more than a technical one.
That's a language definition, not a language. Consider a language L which is implemented in implementation language M.
Stuff that's written in L is part of the satndard library. Stuff that could have been written in L but is written in M (e.g. for speed) is part of the language. And stuff that is written in M is also part of the language.
Having said that, I do use big tools in my day job.
Functional. Functions. And, the only important "Library" is a small and beautiful compiler which is invoked with a built-in function called compile that you can change, swap out and completely remove, of course. Anything else seems like big globs of crufty glue.
Not that that's stopping me from hacking in Haskell.