react-native-hashing VS taro-playground

I went this route when the new arch was an up and coming thing, spent a lot of time learning how to do cpp stuff and i made this: https://github.com/TheRogue76/react-native-hashing From my experience, unless you are doing something that is computationally extremely expensive, or doing something that needs access to the Yoga and the whole of the rendering pipeline, you are better off doing it in Kotlin and Swift. Cpp is not a pleasant or modern language (from the generics to the null handling to enums, my experience was terrible). We are mobile developers, so there will never be a time in your career when Swift or Kotlin are not useful. For my part, I won’t touch cpp ever again unless i have to. But it’s up to you

@wuba/react-native-echart supports a wide range of chart types, but they are too numerous to display here. If you want to explore more comprehensive chart types, you can visit the taro-playground repository to check them out. There, you will find example demos showcasing various ECharts chart types.

In terms of support, @wuba/react-native-echarts supports all types of charts except GL series and map charts which are not yet supported, which is very enough for daily business. The code to implement the various charts in echarts can be found in taro-playground.

The sample code in this post is on the https://github.com/wuba/taro-playground project, which is also open source, and interested parties can also install the new version of the Taro Playground app directly from the app store or from the releases page to experience it.