|
|
|
|
|
by Catloafdev
6 days ago
|
|
I don't agree with the conclusion at all. I can see the value of RTK - whether it is buggy or vibe coded is kind of secondary. That basically comes down to how severe and often the bugs are. There's no gamification of savings here. Tool output can be meaty. Is the author skeptical of the concept, or the implementation? Because only one of those is worth critiquing. |
|
Concept is fine to me and I believe we should optimize, but a repo that will handle all tools sounds like Sisyphus rolling a rock up the hill.