Threadwell

Recent Notes

  • DemetriSpanos

    Oct 06, 2026

    • archive
    • twitter
    • demetrispanos
  • NOTimothyLottes

    Oct 06, 2026

    • archive
    • twitter
    • notimothylottes
  • bonzajplc

    Oct 06, 2026

    • archive
    • twitter
    • bonzajplc
Home

❯

Archive

❯

Threads

❯

rfleury

❯

Why do we spend so much effort to encode programming language semantics into a textual form just so a parser can go through the error-prone process of ripping that same exact information back out? Why not work directly on a program's abstract-syntax tree? (1/8)

❯

@rfleury Are you familiar with @stevekrouse and his http://futureofcoding.org community?

@rfleury Are you familiar with @stevekrouse and his http://futureofcoding.org community?

Properties5
typearchive
sourcetwitter
date2019-08-29
tagsarchive, twitter, rfleury
description@rfleury Are you familiar with @stevekrouse and his http://futureofcoding.org community?

Aug 29, 20191 min read

  • archive
  • twitter
  • rfleury

Source

  • URL: https://x.com/azmreece/status/1167148675140857856
  • Author: Andrew Reece (@azmreece)
  • Posted: 2019-08-29 18:55:03

Branch

1/ @azmreece

@rfleury

Are you familiar with @stevekrouse and his http://futureofcoding.org community?

Related

  • Spine: 2019-08-29-why-do-we-spend-so-much-effort-to-encode

Graph View

  • Source
  • Branch
  • Related

Backlinks

  • Why do we spend so much effort to encode programming language semantics into a textual form just so a parser can go through the error-prone process of ripping that same exact information back out? Why not work directly on a program's abstract-syntax tree? (1/8)

Created with Quartz v5.0.0 © 2026

  • GitHub