Live data from Hacker News

Show HN: Markwhen: Markdown for Timelines

markwhen.com

11–20 of 93 posts

Re: Show HN: Markwhen: Markdown for Timelines

#11
Very interesting. Why is there work inside of the education sections of the life timeline? In the project planning example, I could see it being useful to have something like $ref references from Swagger to e.g. reference a duration from a project group into the overall section.

Re: Show HN: Markwhen: Markdown for Timelines

#12
post #9

This looks neat. I wish it used iso8601 [0] dates. It’s pretty convenient as the time periods uses the format YYYY-MM-DD/YYYY-MM-DD and I think is easier to mentally parse than MM/DD/YYYY-MM/DD/YYYY. Of course I didn’t even know what a solidus (“/“) was until using iso8601. Also, I usually find standards pretty much as overhead, but 8601 seems pretty good as a universal standard. [0] https://en.wikipedia.org/wiki/ISO…

Yeah, so long form 8601 are supported

`2022-08-02T23:00:00.000Z - 2022-08-03T00:00:00.000Z: Event`

but in general I do need to figure out a way to allow more customizable date parsing.[0]

[0]https://github.com/kochrt/markwhen/issues/27

Re: Show HN: Markwhen: Markdown for Timelines

#13
post #9

This looks neat. I wish it used iso8601 [0] dates. It’s pretty convenient as the time periods uses the format YYYY-MM-DD/YYYY-MM-DD and I think is easier to mentally parse than MM/DD/YYYY-MM/DD/YYYY. Of course I didn’t even know what a solidus (“/“) was until using iso8601. Also, I usually find standards pretty much as overhead, but 8601 seems pretty good as a universal standard. [0] https://en.wikipedia.org/wiki/ISO…

> It’s pretty convenient as the time periods uses the format YYYY-MM-DD/YYYY-MM-DD and I think is easier to mentally parse than MM/DD/YYYY-MM/DD/YYYY

Especially for those outside the USA!

Re: Show HN: Markwhen: Markdown for Timelines

#14
post #10

Really awesome to see this evolving to this stage :)

I'm glad you're here to see it!

So cheeaun here posted his life timeline project[0] 9 years ago (!) to hacker news[1] and I always thought it was pretty neat. I made a tool to make timelines like that and it has since evolved into markwhen.

[0] https://github.com/cheeaun/life [1] https://news.ycombinator.com/item?id=6833565

Re: Show HN: Markwhen: Markdown for Timelines

#16
post #9

This looks neat. I wish it used iso8601 [0] dates. It’s pretty convenient as the time periods uses the format YYYY-MM-DD/YYYY-MM-DD and I think is easier to mentally parse than MM/DD/YYYY-MM/DD/YYYY. Of course I didn’t even know what a solidus (“/“) was until using iso8601. Also, I usually find standards pretty much as overhead, but 8601 seems pretty good as a universal standard. [0] https://en.wikipedia.org/wiki/ISO…

> It’s pretty convenient as the time periods uses the format YYYY-MM-DD/YYYY-MM-DD and I think is easier to mentally parse than MM/DD/YYYY-MM/DD/YYYY Especially for those outside the USA!

As someone who grew up in the US, it's still bizarre as a programmer to have a mixed-significance ordering (MM-DD-YYYY) instead of any consistently-endian ordering (DD-MM-YYYY or YYYY-MM-DD).

Out of curiosity, in what order do Europeans verbally say full dates with month names? Or does it vary by language?

Re: Show HN: Markwhen: Markdown for Timelines

#17
This is awesome! I want to see other tools like this. I dream of a project management system that is text based and lives in your codebase seems we are pretty close with this. Planning (this), comments / descriptions (markdown), identity / people (??), tickets (??) Anyone know of something like this?
Post reply on HN