@gtwilson There's a system setting that controls whether they reorder or stay put. I think the default is to reorder. Yeah, the Spatial Finder is thoroughly dead.
@matigo Drafts and Editorial and Scrivener and Ulysses are other options. I have the first two. Use Drafts like a scratch pad and Editorial sometimes for longer writing.
@matigo Oh. On a back end, there's a ridiculous number of parser options. There's the classic Yacc up to very recent Hammer [github.com]. And I think @gtwilson has had fun times with ANTLR. ;)
/@rafial
@kdfrawg Final Cut and Logic are their current "no, really, we still do Pro software" examples.
/@joeo10
@matigo Looks like Ragel will generate a JS parser with no added dependencies.
/@rafial
@b123400 The worry isn't size of value but reliably sized and laid out serialized structure.
It looked like it's just snagging the structure memory and splashing it on disk and back, which should be OK up till compiler changes alter memory layout (#pragma packed can help here) or the file gets synced to a device with different integer width or endianness.
The fix would be to de/serialize intentionally to a byte buffer. But not sure how that would interact with the JavaScript preferences system's assumptions.
@rafial Scratch that. Serious gibberish: https://mastodon.xyz/%3Cspan%20class= became the href!
@matigo are you using regex rewrite rules rather than a full parser?
@rafial Workaround is to use explicit hyperlink syntax, like @rafial">mastodon!rafial [mastodon.xyz].