Live data from Hacker News

Show HN: I ported Tree-sitter to Go

github.com

31–40 of 116 posts

Re: Show HN: I ported Tree-sitter to Go

#31

Claude attempted a treesitter to go port Better title

I work on a revision control system project, except merge is CRDT. On Feb 22 there was a server break-in (I did not keep unencrypted sources on the client, server login was YubiKey only, but that is not 100% guarantee). I reported break-in to my Telegram channel that day.

My design docs https://replicated.wiki/blog/partII.html

I used tree-sitter for coarse AST. Some key parts were missing from the server as well, because I expected problems (had lots of adventures in East Asia, evil maids, various other incidents on a regular basis).

When I saw "tree-sitter in go" title, I was very glad at first. Solves some problems for me. Then I saw the full picture.

Re: Show HN: I ported Tree-sitter to Go

#33
This is great, I was looking for something like this, thanks for making this!

I imagine this can very useful for Go-based forges that need syntax highlighting (i.e. Gitea, Forgejo).

I have a strict no-cgo requirement, so I might use it in my project, which is Git+JJ forge https://gitncoffee.com.

Re: Show HN: I ported Tree-sitter to Go

#36
post #33

This is great, I was looking for something like this, thanks for making this! I imagine this can very useful for Go-based forges that need syntax highlighting (i.e. Gitea, Forgejo). I have a strict no-cgo requirement, so I might use it in my project, which is Git+JJ forge https://gitncoffee.com .

thank you for the kind words! Very cool project! Very happy you can find some utility in it

Re: Show HN: I ported Tree-sitter to Go

#37
Do you have an equivalent of TreeCursors or tree-sitter-generate?

There are at least some use cases where neither queries nor walks are suitable. And I have run into cases where being able to regenerate and compile grammars on the fly is immeasurably helpful.

At least for my use cases, this would be unusable.

Also, what the hell is this:

> partial [..] missing external scanner

Why do you have a parsing mode that guarantees incorrect outputs on some grammars (html comes to mind) and then use it as your “90x faster” benchmark figure?

Re: Show HN: I ported Tree-sitter to Go

#39

Do you have an equivalent of TreeCursors or tree-sitter-generate? There are at least some use cases where neither queries nor walks are suitable. And I have run into cases where being able to regenerate and compile grammars on the fly is immeasurably helpful. At least for my use cases, this would be unusable. Also, what the hell is this: > partial [..] missing external scanner Why do you have a parsing mode that guar…

the 90x figure is on Go source for apples to apples against CGO bound tree-sitter.

your use case is not one i designed for although yeah maybe the readme has some sections too close. the only external scanner missing atm is norg. now that i know your use case i can probably think of a way to close it

Re: Show HN: I ported Tree-sitter to Go

#40
post #34

Earlier quoted context omitted.

Shouldn't you be able to answer that?

yes and if you clicked the links you would know that i did answer it in the readme.

> Pure-Go tree-sitter runtime — no CGo, no C toolchain, WASM-ready.

No you didn't. The readme is obvious LLM slop. Em-dash, rule of three, "not x, y". Why should anyone spend effort reading something you couldn't be bothered to write? Why did you post it to HN from a burner account?

Post reply on HN