1
I'm already using it myself for all of my ongoing projects, but it would be great to have feedback from external users that would be interested in trying out a solid, albeit not yet that popular library.
It's hard to compete with established libraries backed by corporations on breadth of features, documentation and examples, but I think it's very much possible to compete on quality.
I think the main impediment to adoption is the perception of a library as a toy project, so perhaps I should invest the time into making it look more serious - but doing things like setting up a website for documentation seem like they don't really add much value, as github already has quite a nice interface for documenting a codebase.
Interestingly, this does seem like a similar problem to startups finding their first customers, to whom the advice is usually doing things that don't scale - although that is a bit of a generic thing to say, as it encompasses almost anything.
How would you guys approach finding early adopters?
which suggests a different concept of time for ranking posts
the main issue trying to be solved is that currently there is an incentive to find the best time to post something, as the variance in activity causes some times to make for a higher likelihood of post popularity
the suggestion is thus for there to be a different kind of time "tick" - instead of time itself, maybe a site-wide counter of activity such as number of views, votes, or submissions
I find the idea of removing the incentive to find the best time to post interesting. I think an ideal ranking algorithm drives the correlation between the time of posting to the number of impressions on a post to zero.
Interested in hearing y'alls thoughts!