I'm working on a new version of my CV (v1: https://cv.git-pull.com https://cv.git-pull.com) I keep it at https://github.com/tony/cv https://github.com/tony/cv.

I'm working on a new version of my CV (v1: https://cv.git-pull.com https://cv.git-pull.com) I keep it at https://github.com/tony/cv https://github.com/tony/cv. It's in the very early stages This time I'm writing it in React, Angular, and Vue (TypeScript across the board). While doing it, I've tried to find various ways to share the chart and data code across all 3 versions. The library I found to make it happen with data akita: https://datorama.github.io/akita/ https://datorama.github.io/akita/ For UX it's not so easy. The truth is, some of the best UI libraries are framework specific. This creates a lot of fragmentation in the frontend community IMO. For instance react has nivo, victory, and react-vis, but at the end of the day it's svg and canvas underneath the hood. Still though, the efforts are amazing. It makes you wonder what it'd be like if there would be just one agreed upon way to write a widget. (There's web components, custom elements... but those won't even work with typescript out of the box) In the past few years, that stuff that's been going on with webpack v5's persistent caching, TypeScript (and its tooling), and all 3 of these frameworks getting better is amazing. Examples of charting software I've tried: https://cv-react-v2.git-pull.com/dev/branch/v2-billboard.js/ https://cv-react-v2.git-pull.com/dev/branch/v2-billboard.js/, https://cv-react-v2.git-pull.com/dev/branch/v2-plotly/ https://cv-react-v2.git-pull.com/dev/branch/v2-plotly/, https://cv-react-v2.git-pull.com/dev/branch/v2-carboncharts/ https://cv-react-v2.git-pull.com/dev/branch/v2-carboncharts/ For the first time I've found a UI suite called Carbon: https://www.carbondesignsystem.com/ https://www.carbondesignsystem.com/, an IBM thing. I'm most impressed by their chart offering. Even though it's relatively new, they maintain bindings for react, vue and angular.