Markwhen
https://markwhen.com/ is a beautiful website for an interesting project. The comments in the nyc thread that drew my attention to it led me down a rabbit hole of coding horror posts from a decade ago that Id missed or forgotten:
-
https://blog.codinghorror.com/responsible-open-source-code-parenting/ - 29 Dec 2009
-
https://blog.codinghorror.com/standard-flavored-markdown/ - 3 Sep 2014
-
https://blog.codinghorror.com/standard-markdown-is-now-common-markdown/ - 4 Sep 2014
In this series of posts Jeff Atwood first laments the lack of a specification for markdown, then announces that as a result of that first post a consortium of players has now build an standardised library and then within twenty four hours has renamed that library to commonmark when John Gruber the inventor of Markdown expresses his displeasure. Jeff Atwood played a blinder in that series of posts, as was often the case on coding horror in those days. It was nice to see the Meteor team get a call out in the second post.
The Markwhen example. Does it have too many features? Could it be that John Gruber's light touch / benign neglect management style helped markdown, at least in the early days.
Another thing I got from the comments and that I had forgotten about is EDTF (Extended Date Time Format) which is worth knowing about.
Finally, mermaid gantt and timeline diagrams are also well worth looking at for the same use case.
- ← Previous
JsonLogic - Next →
Bye bye Wordpress