Shadowed, this is why I asked for the lock. This isn't productive discussion. If you want to criticize code, do it. Don't banter over semantics to criticize. And if someone says he's currently not ready for input, that's a fair position to take too and I think should be respected.
Give Alar some constructive feedback or let it be, if I see that I'll revert my opinion that this thread needs locking. The statement that he has to accept criticism isn't actually constructive I fear. Because it doesn't deliver content he can learn from and improve with.
He said multiple times now that it's for interal use. It's marked on WAU as for internal use. I don't think there ever was a need for him to justify anything and certainly there is no need to continue justifying it when he already has!
Clearly he only even responded to the question of what a library is because he's been put on the defensive about it.
The question of the thread has been answered, maybe lock before there is more treading and trolling?
Alar, I think you are holding up well. Multiple people already gave the warning signs that things can be very blunt.
You have to understand that there is a certain culture among some people around here that like pecking and adversity for some reason. But there are also people out there that'll be very welcoming and open to things.
And in general the vast majority of people are very helpful once you get to know them better and understand how they tick (and what ticks them off).
In either case I agree that #wowace is very helpful once you manage to assert yourself and develop a filter for stuff that happens that isn't helpful to you. Also people will get to know you which helps a lot.
The reason why some folks are a tad harsh already is basically because you unwittingly are hitting some hot-button issues for some people.
*) Code beauty
*) Code reuse
*) Code that hides detail and is easy to code
aren't categories that some will accept as important and certainly not as categories that trump code size and code efficiency arguments.
The question of what should be in a library is hostly debated and in general, if in doubt a library will nowadays not carry a feature than carry it.
But if you can make a good use case for some things there is a chance that you'll find an ear for it. Still because code reuse isn't a hot commodity, reinventing the wheel happens a good bit (which is very educational though if you have the time).
Once you understand that better it's easier to take all the good feedback that is to be had and develop the cognitive filter for other stuff (I recommend the pink heart-shaped glasses for this purpose).