idea for improving branding of echarty

lgnbhl commented 2 years ago

Hi, It could be interesting to make a comparison with other R package wrapping "Echarts", in particular the popular R package "echarts4r".

What are the key differences between "echarty" and "echarts4r"?
Is "echarty" lighter/faster than "echarts4r"? (give a proof of it with R code)
how the API differs between "echarty" and "echarts4r"?
What are the main advantages using "echarty" and not "echarts4r"?

This would help new users to choose echarty for their projets instead of echarts4r.

Thanks again for you help regarding https://github.com/helgasoft/echarty/issues/14.

Best, Felix

helgasoft commented 2 years ago

Yes, agree, it is time to build a comparison table. Here is the essence. The API is completely different. While echarts4r is wrapping many ECharts options in separate commands, echarty relies exclusively on R lists to match ECharts options. This adds flexibility (we think) and make for smaller code size - echarty 176KB vs echarts4r 877KB.
Less commands to learn is a benefit - echarty has only two(2) major commands to build any chart: ec.init and ec.upd. Actually we encourage users to work primarily with the original ECharts documentation because all options can be plugged directly in echarty commands as R-lists.

Your test case #14 is an example of functionality scope. ... categories= LETTERS[1:4], dimension= 2 ... echarty covers ECharts dataset, but echarts4r does not. That's why categories and dimension options work in echarty.

helgasoft commented 1 year ago

added a comparison table in the Github main page introduction

helgasoft / echarty

idea for improving branding of echarty #16