cv VS pg-mem

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

This time I'm writing it in React, Angular, and Vue (TypeScript across the board). It's in the very early stages, but keep it at https://github.com/tony/cv

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/

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, vicious, 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-plotly/, 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/, 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.

I've used pgmem https://github.com/oguimbal/pg-mem for the last couple of years for the same thing.

I was wondering the other day how to classify tests that use a test double like pg-mem, which isn't a mock but isn't the Dockerized test DB either :

https://github.com/oguimbal/pg-mem

In my case, I use TypeORM with PostgreSQL, and there's pg-mem to run an instance in memory, it supports most of the common functionality of PostgreSQL but you will need to do some adjustment to your code to be within the limits.

Postgres in the browser is possible through pg-mem: "pg-mem is an experimental in-memory emulation of a postgres database" but it also suffers from no persistence. If you can persist to a file somewhere then read it in on startup (and if your local data isn't huge) this might work.

Dont get me wrong: I am trying to contribute to opensource as well, so I get that supporting small projects can be demanding. There's nothing wrong in not spending your weekends on OS. But not asking for help, nor specifying that a project is unmaintained, nor even answering issues & pull requests for years feels just wrong.

A pure Javascript in memory emulation of Posgres, to help writing better node tests https://github.com/oguimbal/pg-mem

Okay, I had a bit of spare time,I've implemented that, and it is now available with [email protected]

To get a glimpse of what I'm talking about, you can clone this repo and follow "Development" instructions (by the way this is a small OS lib I maintain, I wrote about it here)