§ — · Community
Voices from the field.
Notes, reactions, and quiet approvals from practitioners using sem, weave, and the rest of the stack in anger.
§ 01 · on sem
sem
Semantic version control. Entity-level diffs, blame, and impact analysis on top of git.
21 voices
“すごく良さそう!AI以前もほぼ無意識にこの程度のレビューで十分だと思ってたけど、今はなおさらだと思う”
jackchuka@jackchuka
source ↗“Remember Weave, the entity-level git merge tool? Same team just shipped Sem: semantic version control on Git. Instead of 'line 43 changed' you get 'function validateToken added.' Entity-level diffs, blame, impact analysis. 16 langs via tree-sitter.”
Zoltan@zoltansoon
source ↗“いいね、振り切ってる。Every tool in software development was designed for human hands. We're done building for human hands.”
Mako@fulore
source ↗“構文解釈したgit代替commandかな。sem diffを実行すると対象ファイルの言語構文を解釈した上で差分がある関数名を提示してくれたり。diff以外にblame, graph, impactなどが用意されてる。”
matsuu@matsuu
source ↗“you need to check this out. this has SO many applications, from build optimizations to CI / CD, to LLMs. i have no doubt that this, or a project like it, will become the go-to in the future”
merlin@merlindru
source ↗“Not exactly what you asked for but you really really really gotta check this one out. Semantic diffs”
merlin@merlindru
source ↗“git tells you 'line 43 changed'. sem tells you 'function validateToken was added in src/auth.ts'. entity-level diffs on top of git. also does impact analysis, dependency graphs, and entity-level blame. this is how code review should work”
Anandu@BFRAnandu13
source ↗“Git diff está oficialmente muerto. En vez de escupirte 300 líneas para que adivines qué cambió... te dice la verdad: Función login() fue modificada. Clase UserService renombrada. Método validateToken() se movió.”
Erick@ErickSky
source ↗“Another really cool one built on top of a different abstraction from the same team”
Oliver Beavers@oliverbeavers
source ↗“if i never had to write 'this code hasn't changed, i just moved it' comments on my own prs again i'd be a happy bunny”
jenna@jjenzz
source ↗“Okay, I took a look. This is freaking awesome.”
Lacy@lacybuilds
source ↗“Crazy no one ever thought about building this before. Insanely useful!”
Parth S.@savss624
source ↗“This is some cool shit”
Allison@allisonology
source ↗“I've wished for something like this”
tmuxvim@tmuxvim
source ↗“very satisfying watching agents make changes in real time with change impact scoring courtesy of Ataraxy Labs sem-core”
Charles Smart@CharlesMSmart
source ↗“Currently using @codeaborbit for the code review side and sem from Ataraxy for understanding structural impact of changes. Both are fantastic.”
coderabbi@coderabbi
source ↗“良さそう、試してみよ”
y_uucu@y_uucu
source ↗“これは良さそうじゃん、早速試してみよ”
Mako@fulore
source ↗“ディレクトリ構造を直感的に把握できるターミナル向けのツールっぽい 複雑なプロジェクトの全体像を掴むのに使えそうかな”
ぷーじ@yug1224
source ↗“@tigkindel @Palanikannan_M and @rs545837 released this just a couple of days ago - Worth checking it out”
Jacques Verre@JacquesVerre
source ↗“semantic diffs”
agusti@bleuonbase
source ↗§ 02 · on weave
weave
Entity-aware merges. Resolves conflicts git can't see past.
10 voices
“definitely check out weave... entity-level semantic merging. Has saved me a few hrs in the last week alone”
Johann Hipp@jhipp_
source ↗“Weave: entity-level git merge via tree-sitter. Two branches add different functions to the same file? Git panics. Weave parses them as independent entities and merges clean. 31/31 scenarios vs Git's 15/31. Essential for multi-agent coding workflows.”
Zoltan@zoltansoon
source ↗“Weave -- A language aware merge algorithm based on entities”
Angsuman Chakraborty@angsuman
source ↗“Gitの行ベースマージでは独立した変更でも衝突が発生する問題を、tree-sitterで関数・クラス単位の意味的マージに置換して解決。Gitが31件中15件しかクリーンマージできないケースで31件全件を自動解決”
su8 / denchu@__su888
source ↗“Weave -- A language aware merge algorithm based on entities #hackernews”
Data Cyborg@data_cyborg
source ↗“@banteg this one looks cool too”
qando@qandokan
source ↗“Agreed but these tools do help.”
IMRAN@imrane
source ↗“!”
chex@factormystic
source ↗“This new merge algo for git looks pretty good! It symantically understands various languages including Python, TypeScript, markdown etc and avoids a lot of conflicts that aren't really conflicts!”
Shital Shah@sytelus
source ↗“I've wanted a language-aware git merge algorithm for years. Is this what I've been waiting for?”
James@Darpinian
source ↗§ 03 · on inspect
inspect
Semantic code review. Entity graphs plus LLMs reading for meaning, not syntax.
3 voices
“I've had the opportunity to only briefly use this tool, but what I've seen so far is really useful.”
Scott S. Lowe@scott_lowe
source ↗“Inspect does semantic code review using entity graphs + LLMs – it understands what your code *means*, not just what it says. Most linters catch syntax. This catches logic.”
Gustavo Salami@gustavosalami
source ↗“annotation-led review is the future. I wonder if you'd consider incorporating something like Inspect”
Oliver Beavers@oliverbeavers
source ↗§ 04 · on opensessions
opensessions
A tmux sidebar for managing coding-agent sessions.
5 voices
“If you use tmux daily and have recently been using coding agents, this project might be worth checking out. A tmux sidebar that can synchronize and manage the status and sessions of different coding agents.”
Jintao Zhang@aiandcloud
source ↗“I just gave opensessions a spin after vibe-slopping my own solution – amazing work”
Nimrod Gutman@theguti
source ↗“Tried cmux/conductor/superset/etc, the random bugs are really annoying. I've completely abandoned them for tmux plugins. Using opensessions.”
Micro 小熊猫@xxm459259
source ↗“That's some quite satisfying overengineering”
Natik Gadzhi@natikgadzhi
source ↗“superset/conducter 感觉是用 electron 包了一层 worktree,预览 diff 编辑都不好用”
鸽@AniHermit
source ↗