Why you shouldn't parse the output of ls(1) (mywiki.wooledge.org) | HN Screenshots

YHacker Newsscreenshots

Screenshot of mywiki.wooledge.org: Why you shouldn't parse the output of ls(1)

First screen, captured 2 years ago.

Looks similar

Screenshot of tratt.net: Parsing: The Solved Problem That Isn't (2011)

Parsing: The Solved Problem That Isn't (2011)(tratt.net)

102 points by contr-error 2 years ago | 65 comments

Screenshot of tratt.net: Structured Editing and Incremental Parsing

Structured Editing and Incremental Parsing (tratt.net)

15 points by todsacerdoti 1 year ago | 2 comments

Screenshot of tratt.net: Structured Editing and Incremental Parsing

Structured Editing and Incremental Parsing (tratt.net)

119 points by ltratt 1 year ago | 36 comments

Screenshot of tkte.ch: Parsing URLs in Python

Parsing URLs in Python (tkte.ch)

148 points by ibobev 2 years ago | 76 comments

Screenshot of gunkies.org: Gordon Letwin OS/2 Usenet post (1995)

Gordon Letwin OS/2 Usenet post (1995)(gunkies.org)

92 points by walterbell 1 year ago | 68 comments

Screenshot of flak.tedunangst.com: Polarizing Parsers

Polarizing Parsers (flak.tedunangst.com)

21 points by upofadown 1 year ago | 3 comments