sundown

I thought this is the famous Markdown parser by Vicent Martí. [1] It was the most popular Markdown implementation before CommonMark, and is used by GitHub (via RedCarpet, its Ruby binding) before they switch to CommonMark a while ago. The name choice is a bit unfortunate, but I guess it’s too late to change it now. [1]: https://github.com/vmg/sundown

As a product marketer, I have to say that the name is very unfortunate. 1. Sundown is the name of a Markdown library written in C: https://github.com/vmg/sundown. That Sundown is pretty widely known and used among Markdown implementers. As such, when/if the OP's project takes off, it is going to be confusing (for awhile). 2. Also, the name itself doesn't strongly suggest that it's an alternative to Markdown. Do recall that Markdown's etymology comes from "(HTML) markup". For the Markdown-implemented-in-C Sundown, the name worked because it evoked its relationship with Markdown. In this case, that's not what the project is about. If the intention was to evoke Markdown, then they should have kept the "Mark" part of it, not the "down" part of it.

At SunSed we provide a cloud IDE to our users so they can easily update their website. Every time they make a change the IDE automatically saves the file and on the server we had to compile Markdown -> HTML+SunSed(custom HTML tags) -> Executable. Not to mention bulk website upload, backups and restores (a website could have thousands of pages). Markdown was the slowest part with the most resource usage. I actually bench marked all of the Markdown implementatinos back in 2016 (or early 2017). https://github.com/vmg/sundown was by far the fastest!

Very poor naming choice. Sundown is the name of a popular Markdown implementation: https://github.com/vmg/sundown Strongly suggest renaming your project as early as possible.

First off, Good work on your project, Sed! Here are some clickables of SunSed: - https://www.sunsed.com/ - https://www.sunsed.com/pricing - https://www.sunsed.com/tags/s A list of builtin tags for Sundown I am fine with a new markup if it's quick and to the point. I believe that we need to give the markdown/reStructuredText things a fresh look. At the very least, we may come up with ideas to improve existing languages. Are you planning on opening the source to Sundown? What's the current implementation running in? (golang, python, c, etc?) Some of the other commenters are mentioning markdown being fast. This is probably true. Since there are processors for markdown in C. Actually, when I first glanced the title, I thought it was https://github.com/vmg/sundown. In any event, that's just a naming issue. The bigger point is, I think the over

Almost a year and a half ago Jeff Atwood proposed a Markdown standardization effort: http://blog.codinghorror.com/the-future-of-markdown/). The popular Markdown parser Sundown was subsequently deprecated in antipication of this effort (https://github.com/vmg/sundown/commit/37728fb2d7137ff7c37d0a474cb827a8d6d846d8) and has not been updated since. What happened to this effort? It seems implausible to me that it could take a year and a half. Did it fall apart?

In related news, I recently saw this: https://github.com/vmg/sundown/commit/37728fb2d7137ff7c37d0a... Looks like the proposal to create a formal markdown standard is actually going somewhere.

You might also want to look into GitHub's Sundown library. It's an awesome library and being written in pure C, you can use it natively. The reason I wrote myself is that my use case was more markdown highlighting than markdown parsing. I needed to preserve the markdown source untouched, which Sundown doesn't support. https://github.com/vmg/sundown

> I have a wishlist of people who should sign the resulting spec. Jeff and Gruber, of course. Why them? > A few markdown users (Doxygen, Github, ...) Github are also implementors, hence the 2 or 3-years old "github-flavored markdown". https://github.com/vmg/sundown is their core library, with https://github.com/vmg/redcarpet as the ruby interface.