Deprecate features previously identified

[joshbruce]

Marked version: 0.3.17

Proposal type: other

What pain point are you perceiving?

Marked, over the years, has been taken beyond its single responsibility of converting spec-based Markdown into HTML. This has increased the size and complexity of the codebase; thereby, making it more difficult to maintain. This bloat can actually lead to marked being less performant than it could be in comparison.

What solution are you suggesting?

• Remove the features marked (see what I did there) for deprecation from the codebase in the transition between 2.0 and 2.1 (this should give our users enough fair warning to respond accordingly...the rest of 0.x, all of 1.x, and the first push of 2.0)