parse

The difference between (lex, parse, execute) and (lex, parse, generate assembly) are very small, if you are willing to forego optimizations.

No javsacript for the client to download, parse and process, just straight content to render and done.

Conversation threads are buried under a click/touch and even then, it's hard to parse it.

Perhaps possible for HN to parse the title/og:title meta data on a page and force that as the title of HN submissions?

Now on that point alone, I'd say that `10.times.do` is certainly easier to parse, but easier is not better.

I'd rather read/parse quickly 50 insightful comments, that 300 where most of them are jokes, puns, etc.

Leave out how long it took you to learn node.js and parse.com.

Sure, they parse the numbers and can do basic comparison about whether something is less than, equal to or greater than a given version.

That took me a few seconds to parse correctly.

The post appears to emphasize the importance of (human) communication, with the partially explicated implication that being able to parse human communication well is an aspect of communicating well.

And that this appears to him to be at least somewhat related or correlated to the interest and ability to parse and to understand parsing and/or similar constructs in programming.

[citation needed], preferably in a format both my conscious and unconscious mind can parse.

Signs point to Googlebot using a browser, so it doesn't need to "parse" things, per se.

I guess one could also raise the question of the context being discussed, and therefore which meanings of "parse" are being discussed.

I believe this situation is usually referred to as the "Most vexing parse".

"What has this person done?" is my internal dialogue while I parse through resumes.

On the backend, we run on Parse, so any JS/Parse experience would be a plus.

Parse.ly's analytics platform helps digital storytellers at some of the web's best sites, such as Arstechnica, New Yorker, The Atlantic, The Next Web, and many more.