vika_nezrimayaLocks are evil. Locks are the most evil thing in the world. Going lockless for reads seems like a good decision. Just make sure creates are atomic and updates can't conflict with each other
vika_nezrimayaand all I had to do was to get rid of locks on files read... and then make writes compete for an atomic file creation where losers bail out and tell clients to retry
[tantek]It's only since the 1990s that we've had vCard's international-aware property *given-name* 🙄 (which was re-used by hCard, vCard4, h-card, schema-org/Person etc.)
[tantek]It should have been based on a spectrum of "just" existing plain HTML elements (with *maybe* additional attributes) to Web Components which both already have much better understood security characteristics/concerns/precautions etc.
[tantek]Inventing a bunch of one-off JSON for this use-case is a classic example not understanding the existing technology stack (and how to use its existing features) and so introducing another (unnecessary) layer of abstraction on top.
[tantek]I mean seriously the diagram in the image preview literally is *mostly pre-existing HTML elements* (or trivial pairings thereof): paragraph/<p>, heading<hn>, list/<ol>/<ul>, quote/<blockquote>,
[tantek]Build Web Components for "verse" and "markdown" and "gallery" and you're basically done. of course this would mean using HTML as HTML and not just as a JS-delivery wrapper