Content
@
https://warpcast.com/~/channel/six
0 reply
0 recast
0 reaction
shazow
@shazow.eth
Long LSP and treesitter: they are *still* underrated in how impactful they are to the present and future of editor tooling. We're just starting to scratch the surface on what we can build with them. Here's things we haven't even done yet: - We can build jq that works with any language works with treesitter, not just JSON. - We can make a tool that generates control flow diagrams for any language. - LLMs can use TS grammars to tightly constrain valid output, vastly reducing training costs and possibly model sizes. - We can make plugins that augments tooling for any language that works with any editor (not just programming!), a lot of AI-assistants already use hooks like this. - Agents can interface with language structures at a higher level (AST) rather than sending text diffs back and forth. These two technologies began a golden age of editor tooling, and we're just getting started. https://x.com/shazow/status/1406289893895122951
5 replies
2 recasts
17 reactions
HH
@hamud
writing up a new grammar for a new language is a pain in the bum in treesitter but you are defo right that treesitter has made things so much easier. You can write a security tool, static analyzer using just treesitter
1 reply
0 recast
2 reactions
Daniel Lombraña
@teleyinex.eth
Do you use neovim?
1 reply
0 recast
0 reaction
mindtree
@mindtrizzl.eth
Big agree for the majority of cases! My only qualm with both (treesitter especially) is that they tend to fall short for languages pushing the cutting edge with dependent types (like Idris, Agda, Coq). So editors like Helix that only support treesitter and LSP are ruled out for me.
1 reply
0 recast
0 reaction
Daniel Fernandes
@dfern.eth
LSP is awesome, I swapped out VSCode's default intellisense C++ langserver and replaced it with Clang and it was a seamless several-orders-of-magnitude UX improvement.
0 reply
0 recast
2 reactions
Fucory
@fucory
This post is a neovim maxi dog whistle
1 reply
0 recast
0 reaction
