Show HN: Moiva.io – A better way to evaluate and compare JavaScript libraries
moiva.io
moiva.io
It's usually a daunting and time-consuming activity to find a better library and decide on a Tech Stack for your next project. Usually we developers skim through a countless number of resources in a search for a meaningful information. Every developer has its own favourite list of resources to look up in.
I want to change that and that's why I created Moiva.io My goal was to gather, aggregate and present valuable information in an easy and digestible way - one chart per a meaningful metric. If possible and makes sense - show a trend.
I don't want to clutter the page with useless information and useless metrics. I don't want to present any scientifically calculated information which is hard to digest and understand.
Evaluation and comparison should be dead simple.
I have big plans for that project and lots of ideas. I want to create something really useful for developers.
That's why your feedback is critical on that road.
- does the project bring any value to you? Do you think it makes sense?
- suggestions for new charts?
- suggestions for existing charts and information?
However, I have some comments, do with it as you like, let's put this first: I like the layout and I think it's a very useful tool to compare libraries in general.
- I think Contributors per year and Releases per year, could be monthly or quarterly as it's more granular and yearly change doesn't say much for libraries that are only there for 1-2 years.
- Also the history-back makes the url change but doesn't get reflected in the page
- A "clear all" button would be nice
- It would be nice to merge some libraries, because sometimes a library changes it's name and it would be nice to merge the statistics. (e.g. https://moiva.io/?compare=@web/dev-server+es-dev-server)
> - I think Contributors per year and Releases per year, could be monthly or quarterly as it's more granular and yearly change doesn't say much for libraries that are only there for 1-2 years. I need to give it another thought, might be it makes sense to change it the way you suggest
> - Also the history-back makes the url change but doesn't get reflected in the page Yes, I know about that problem, haven't had time yet to fix it - there were more important things to implement. But it's on my agenda. BTW you are first who comments about it )
> - A "clear all" button would be nice Agree. It'll be there soon.
> - It would be nice to merge some libraries, because sometimes a library changes it's name and it would be nice to merge the statistics. In the mentioned case the packages point to 2 different GitHub repositories with different owners. So I don't see what could be merged there and why it needs to be merged. Maybe you have a better example to understand the problem?
Another thing, maybe “trendiness” is a nice metric. Could be based on the amount of stars it receives in a given month. Not sure where to get the data from though. Such metric could show a comparison of what’s in decline and what’s on the rise.
>maybe “trendiness” is a nice metric Good suggestion, thanks! I will look into it