Live data from Hacker News

A Working Mathematician’s Guide to Parsing

jeremykun.com

1–10 of 23 posts

Re: A Working Mathematician’s Guide to Parsing

#2
My go-to library for parsing in Python is https://github.com/pyparsing/pyparsing, a https://en.wikipedia.org/wiki/Parsing_expression_grammar -based https://en.wikipedia.org/wiki/Parser_combinator library. I generally find it much easier to get my head around parser combinators than parser generators.

Re: A Working Mathematician’s Guide to Parsing

#4
post #3

Am I the only person who looks at Jeremy Kun's output and thinks "Nope, this guy is not actually a gifted communicator dedicated to sharing knowledge, he's just a postdoc on an annoyingly self-aggrandizing narcissism trip"?

I can't see that him being "just" a postdoc has very much to do with anything, especially when covering stuff like this which is foundational rather than cutting-edge.

Re: A Working Mathematician’s Guide to Parsing

#5
post #4
post #3

Am I the only person who looks at Jeremy Kun's output and thinks "Nope, this guy is not actually a gifted communicator dedicated to sharing knowledge, he's just a postdoc on an annoyingly self-aggrandizing narcissism trip"?

I can't see that him being "just" a postdoc has very much to do with anything, especially when covering stuff like this which is foundational rather than cutting-edge.

The "just" was supposed to apply to the whole self-aggrandizing trip.

My point is that there are a lot of people with math PhDs, but Kun is in a small unenviable minority that is driven to engage in self-promotion via all these blog post "primers", which of very dubious pedagogical quality.

Re: A Working Mathematician’s Guide to Parsing

#6
> Our hero, a mathematician, is writing notes in LaTeX and needs to convert it to a format that her blog platform accepts. She’s used to using dollar sign delimiters for math mode, but her blog requires \( \) and \[ \].

Unless our hero mathematician is writing, like, several blog posts a day, using tools like parser generators and writing your grammar in BNF and the like is WAY overkill. Just use search/replace and manually fix it up. Or, like, maybe some kind of editor macro/multiple cursor nonsense in your fully-featured text editor. If she really wants to go nuts, she should write a four-line python script to do the search/replace a tiny bit smarter. Fixing it up with some manual oversight takes like three minutes per blog post at most, it's not worth trying to automate fully.

This is one of them "killing an ant with a nuclear bomb" situations.

Re: A Working Mathematician’s Guide to Parsing

#9
post #8

Sadly, he don't understand what LaTeX is and what TeX is. And $$ is a TeX macro, should not be used in LaTeX, the are much better math display environments.

Regardless, this is a very common way of writing mathematics in LaTeX, and so will need to be addressed in any solution to this problem.

Re: A Working Mathematician’s Guide to Parsing

#10
post #5
post #4

Earlier quoted context omitted.

I can't see that him being "just" a postdoc has very much to do with anything, especially when covering stuff like this which is foundational rather than cutting-edge.

The "just" was supposed to apply to the whole self-aggrandizing trip. My point is that there are a lot of people with math PhDs, but Kun is in a small unenviable minority that is driven to engage in self-promotion via all these blog post "primers", which of very dubious pedagogical quality.

“Oh no, someone is attempting to teach, how dare they!” is what this reads like. Writing articles like this is good for the author, in terms of finding new ways to explain things, and clarify knowledge they already had. The writing style of this author in particular is quite engaging for myself and (I would assume) many others.
Post reply on HN