echarts-for-react VS nivo

Before adopting nivo and Cloudinary, we initially used Apache E-charts (specifically a React wrapper called echarts-for-react) to handle image processing and loading. This approach proved extremely slow, and it was quite the process in figuring out a better solution while we had a real-time constraint.

Make echarts come in handy for React. Based on echarts-for-react

What about echarts-for-react?

Rating: 3.1 stars on GitHub

Although I haven't used Semiotic but Echarts [1] for the last 4 years, I agree with the sentiment. D3 is regularly on top of HN and I always wonder if its popularity is due to people not knowing there are easier alternatives or it's because they really need a library as low-level as D3 for plotting their data.

[1] https://github.com/apache/echarts + https://github.com/hustcc/echarts-for-react

been using echarts for the last 3 years

Nivo is a data visualization library built on top of D3.js and React. It offers a range of well-designed, customizable charts with great animations, making it suitable for creating visually impressive data visualizations.

When it comes to charting, Nivo makes you immediately superhero.

Since no one mentioned it, checkout nivo

Today this works thanks to nivo and Cloudinary, but that journey included a lot of trials and testing for the perfect solution.

Nivo is built on D3 and provides a variety of templates for data visualization and presentation. It is one of the few libraries that provide server-side rendering ability and fully declarative charts.

Then, we can think about the implementation. We use Nivo for most data visualizations, but we do have a few that either use straight HTML/CSS, or use D3 directly.

I always use https://nivo.rocks/ you can customize it a ton. Works great.

I use nivo.rocks to visualize the genres and make the list more interactive. Please read my comment on how I implemented it.

CRUD is just one part of the layer. It allows adding/removing/updating data. This is simply a data-foundation for an application.

Of course it feels the same across apps and industries-- it's a concrete slab upon which you build things.

Add layers on top of that, such as:

- Data visualizations. You have data from your CRUD, so do something creative with it. If you're familiar with ReactJS, check out open source, free libraries such as: https://nivo.rocks/ and https://charts.ant.design/

- Data integrations. Depending on the business you're in, experiment with integrating your CRUD app with external data sources via REST API or GraphQL. For example, a CRM like Salesforce or Marketo. Or a REST API in a particular business domain. Or a Google product which a customer might use, such as google drive.