For the last year I’ve been picking away at supporting TextKit2 in @drafts editor…while still supporting TextKit1 and backward compatibility.

The project likely would have gone faster if I was clear what I was gaining, other than “full” Writing Tools support, and, though I haven’t tested enough myself, I’m pretty sure I’m going to have to ship with a “use legacy editor” mode for people who run into the edge cases TextKit2 still doesn’t handle well.

Doesn’t instill a lot of confidence…

0

If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.social/users/agiletortoise/statuses/115585371374966524 on your instance and quote it. (Note that quoting is not supported in Mastodon.)