prolink-connect VS Joplin

example overlay: https://www.youtube.com/watch?v=4rvdzTYK29E

Technically the software covers a _lot_ of the stack

* Reverse engineered Pioneer DJ gear's proprietary low-level network protocol to masquerade as one and receive state updates from the physical DJ gear on the network. The implementation is a typescript library [0].

* Implements a NFS client in typescript to download the music metadata database off of the USB drives DJs plug into the DJ gear.

* Uses kaitai-struct [01 to generate parsing code for the (very old) DeviceSQL database files that the music database use.

* The application is built as an electron app, react + emotion (styled-components) + framer-motion (animated components), and mobx with serializr to handle IPC between the main thread and renderer.

* Uses websockets with the same serialization driver to communicate updates to the overlay browser window which is rendered in OBS (or another livestreaming studio software)

I've just started working on an API backend for it as well, where the same serialization backend is used to publish users app store to a central server which will be useful for features like "Live user track voting", where you pick a playlist on your gear to expose to users, and they can vote on tracks.

[0]: https://github.com/EvanPurkhiser/prolink-connect

I've had great success with using Joplin for this, with Syncthing as a sync backend. Works well across OSes; I use it on Linux, macOS, Windows and Android.

https://joplinapp.org/

The tools to manipulate SQL aren't that bad, no.

But rather than having a self explanatory markdown & flat file, now I have to start learning about the schema & making specific tools (in my preferred language) for manipulating Joplin's schema.

Suddenly I'm digging through 20 different technic specs to decode what data is where, how it works, and what I can do to it. Want to edit history? This is the best help you'll get, pray it's adequately technical to expedite you to your purpose: https://github.com/laurent22/joplin/blob/dev/readme/dev/spec...

As I began with, I struggle to imagine anything that generates anywhere near as much user agency as flat files and markdown. Having boring common data & systems lets me apply portable skills I already have, rather than having to skill up in some particular product's own ecosystem.

Joplin is a good open source option too, feels more like the original Evernote in terms of UI/UX https://github.com/laurent22/joplin/

Joplin, an open source, extendable, Markdown-based hierarchical note-taking app: https://joplinapp.org/

It lets you choose a synchronization backend, offers applications for every major desktop and mobile OS (also has a terminal version). You can create notebooks and subnotebooks to organize your notes. You can also add tags for better search experience. I created notebooks for specific domains (work-related, home improvement, etc.) and also keep a "temp" for quick notes and W.I.P. snippets.

Its only con that it uses Electron on desktop which causes relatively slow start of the application.

done