Well, I think @martin has a proper point. One I touched upon before. Maybe summarize it with uniformity, coherence etc. across the whole eco-system (no Zen please)
One way to use a 2d .. 4d vector. One way to deal with colours. One way to .... I don't want lego blocks with different form or shape of "nipples". Simple example. I wrote a naive app to render textures from math functions, just for fun. I can use the resulting images to generate sound. But they have to be greyscale. I use Pixie as I used it before, but it does do not grey values, it depends on chroma that is only colourful. So I just did color (0.5,0.5,0.5) and wrote that to .png Not the "proper" way. Then I found a Nim lib for PNG's that supports greyscale. But it uses a different colour type.... I just saw there's a bit on colour in Nim core libs too. Also different. One of several things I hate in Python, when I ask a question, "how do I do this in Python", I get a numpy (function) answer. (Or JQuery answers on javascript questions). Just as an example / question, what part of arraymancer should become part of "base" to be build upon? How many batteries and what should be included? So, imho, there has to be great library (type) "synchronisation" to create a great "language". A language and libraries with as little fragmentation as possible. Pick a very good solution and change it when a better one comes up. Put the old one in core-old and give it a few years of support. Cheers.
