HN Showcase
Back to browse
GitHub Repository

Pure Go tree-sitter runtime

514 starsGo

I ported Tree-sitter to Go

by odvcencio·Feb 25, 2026·222 points·106 comments
Visit ProjectView on HN

AI Analysis

●●●BangerWizardryBig Brain

90x faster incremental parsing in pure Go—tree-sitter without C toolchain friction.

Strengths
  • •90x incremental reparse speedup is not marketing—critical for real-time editors and language servers.
  • •Pure Go means `go get` works on WASM, arm64, Windows without C toolchain—solves actual CGo pain.
  • •Drop-in replacement for existing tree-sitter grammars, so zero migration cost for grammar authors.
Weaknesses
  • •Most Go projects don't need tree-sitter yet—audience is narrow (editor/LSP builders).
  • •Tree-sitter itself is Rust-native; Go adoption of this is unproven despite the technical win.
Target Audience

Go developers, editor/IDE builders, language tool authors

Similar To

tree-sitter (C/Rust original) · Zed parser · rust-analyzer

Post Description

This started as a hard requirement for my TUI-based editor application, it ended up going in a few different directions.

A suite of tools that help with semantic code entities: https://github.com/odvcencio/gts-suite

A next-gen version control system called Got: https://github.com/odvcencio/got

I think this has some pretty big potential! I think there's many classes of application (particularly legacy architecture) that can benefit from these kinds of analysis tooling. My next post will be about composing all these together, an exciting project I call GotHub. Thanks!

Similar Projects