Steve Troughton-Smith🎙️ It's been a while since I did one of these, so let's go — reply and show me what you've been working on lately! Include a screenshot, link-out, and use the hashtag #showcase if you'd like to be boosted — assume the reader knows nothing about you or your projects. Remember you can edit posts if you forget something, and mute the hashtag for a period if you don't want to participate
MarkEdit for Markdown@stroughtonsmith MarkEdit: https://markedit.app a privacy-focused, native, fast & tiny Markdown editor for Mac. It's super lightweight (1.7 MB on the Mac App Store) and blazingly fast (edits 10 MB files easily). It's also an OSS, the code is available at: https://github.com/MarkEdit-app/MarkEdit #showcase #markedit #macos #markdown
‎MarkEdit for Markdown
‎# MarkEdit MarkEdit is a free and **open-source** Markdown editor, for macOS. It's just like _TextEdit_ on Mac but dedicated to `Markdown`. ## What make MarkEdit different - Privacy focused: doesn't collect any user data - Native: clean and intuitive, feels right at home on Mac - Fast: edits 10 M…
Naman@MarkEditApp it uses CodeMirror for the actual editor?
@MarkEditApp in that case, have you considered using Runestone instead? It recently got an AppKit port and should make your app even more “native”!
@nmn Thanks for the recommendation, it is a nice project for sure.
However, IMHO TextKit (1 and 2, or lower level, CoreText) has huge gap compared to web technologies, including the product and the community.
In MarkEdit, we did lots of things that are desperately hard to achieve using "native" technologies, such as multi-caret, code folding. The performance and extensibility of cm6 is also surprisingly good.
@MarkEditApp AFAIK, Runestone is built atop CoreText and not TextKit, which means those features should be easier to add. But Multi-Carey sounds challenging regardless. Runestone is iOS first where multi-caret makes less sense too.
@nmn I recently took a closer look at both Runestone and STTextView, both are good projects, but I realized that the gap is even bigger than I expected. Not only because some editor features are hard to implement, but also lack of some basic editing features like spellcheck and lookup.
@nmn It's super weird that you don't get these from native approaches (CoreText and TextKit 2) for free (another very well-known CoreText based editor Textastic doesn't support these either), but WebKit does take care of these, I am confused by which one is more native now.
Well, it is fair to say you don't need these in a source code editor, but for Markdown editing I would expect the experience more solid for normal writings.