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 You can still have the representation be textual but have the ide give you tooling of this kind.

@rfleury You can still have the representation be textual but have the ide give you tooling of this kind.

Properties5
typearchive
sourcetwitter
date2019-08-29
tagsarchive, twitter, rfleury
description@rfleury You can still have the representation be textual but have the ide give you tooling of this kind.

Aug 29, 20191 min read

  • archive
  • twitter
  • rfleury

Source

  • URL: https://x.com/SasLuca/status/1166992282173739008
  • Author: Luca (@SasLuca)
  • Posted: 2019-08-29 08:33:36

Branch

1/ @SasLuca

@rfleury

You can still have the representation be textual but have the ide give you tooling of this kind. For example if you use swift in xcode you can drag and drop an image and set it as the value of a variable, or a 3d model, etc.

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