TileFlip VS victory

If you’re interested in how I built this: https://github.com/vbhaip/TileFlip. If you create anything cool, please share it in the comments, because I’d love to check it out!

I’d love to get feedback from the community. If you’re interested in how I built this: https://github.com/vbhaip/TileFlip.

Hi everyone! I recently built TileFlip, which is a playground where you code a rule that applies to every tile and try to make a visualization (inspired by tixy.land!). I’d love to get feedback from the community on what everyone thinks. If you’re interested in how I built this: https://github.com/vbhaip/TileFlip.

Victory is a set of modular charting components for React and React Native. Victory makes it easy to get started without sacrificing flexibility. Create one of a kind data visualizations with fully customizable styles and behaviors. Victory uses the same API for web and React Native applications for easy cross-platform charting.

Victory Native is a chart library that was developed in 2015. It has been 7 years since its inception. With a high cumulative download count of 7,434,044, it has garnered an impressive 10.3k+ stars on GitHub. It is the longest-standing and most widely used chart library in the history of React Native.

Anyone use Victory? It looks like it is gaining traction.

For convenience of others, here’s a link to Victory Native’s project site (it’s a react.js library with a native version, so be sure to find the native docs).

Victory is a ReactJS and React Native chart library created by Formidable. It's based on ReactJS and D3, and comes with a slew of fully configurable charts pre-installed.

I've enjoyed using Victory - needs React tho: https://formidable.com/open-source/victory/

Victory is great, it doesn't officially support React 18 yet, you'll get warnings because the peer version is still looking for React 17, but it shouldn't be an issue if you force install. It's really just that the tests won't work with React 18, but it should be fine to use it in your project.

They have an open issue for React 18 support, but they are stuck because they are using Enzyme for unit tests (which is effectively obsolete and will likely never work with React 18). So their plan appears to be to move from Enzyme to RTL first and then support React 18.