Hacker News new | past | comments | ask | show | jobs | submit login
Show HN: Moiva.io – A better way to evaluate and compare JavaScript libraries (moiva.io)
3 points by alexey2020 3 months ago | hide | past | favorite | 5 comments



React or Vue? Angular or Svelte? MomentJS alternatives? We've all been there.

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?


Looks nice. Used urql, graphql-request, @apollo/client and it's a nice comparison. https://moiva.io/?compare=@apollo/client+apollo-client+graph...

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)


Thanks for valuable feedback! I'm always glad and eager to hear such meaningful comments.

> - 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?


The stats of the libraries are essentially the same lib but they renamed it and put it to an organisation. It’s mentioned in the es-dev-server. Same goes for prisma and prisma-2.

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.


Well, I see that stats for es-dev-server/@web/dev-server and prisma/prisma-2 are completely different. Bundle size is different, languages is different. I think it's fair enough to treat them as different packages. For example, AngularJS and Angular are also totally different frameworks. And it can be also useful for example to check stats for the old package, because it might be in use for a long time and people might be interested in tracking its stats.

>maybe “trendiness” is a nice metric Good suggestion, thanks! I will look into it




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: