geraltofrivia
Joined 12 years ago
Joined 12 years ago
That's pretty much what we did. We start with a repository, and
- (vibeclean pipeline) make changes to clean analyzer issues (some of them involve moving big code chunks around to reduce cognitive complexity), and tweak the existing test sets when needed.
- (slopify pipeline) inverse, add analyzer issues and increase complexity, add dead code etc.
In both cases, we ensure that the test coverage remains the same, and the tests are passing, before we start our experiments.
What we didn't do (stupid oversight on my part) was to ensure that there are no regressions in the remaining tests in the repo (unrelated to the current task). In practice, when using Sonnet 4.6 IRL, I don't see a lot of regressions because often the agent runs the test before calling it done. But it could have gone either way. We don't know.
In fact, there are some papers (that we cited) which create a set of tasks doing exactly this, and it is non-trivial [1].
Using LLMs to rewrite code to remove these violations is a rather accepted practice. Sonar's existing one-shot LLM based approach [1] (in production since 1+ year), and a recent agentic approach [2] to do the same work rather well to do this.
[1] https://www.sonarsource.com/solutions/ai/ai-codefix/
[2] https://www.sonarsource.com/products/sonarqube/remediation-a...
But also, due to infrastructure. Everyone who could afford it has had a battery and inverter in our homes since forever. Hooking up some solar panels to it is relatively straightforward.
I think there are also some state sponsored subsidies involved although I couldn’t tell you how much.
So i would have to disagree. We are significantly far ahead from the initial “idea”.
My home country (India), and others (Singapore, others?) have outright banned all electronic cigarettes which is a regulation I hate. I acknowledge that vapes reduce barriers to entry to kids. This is partly solvable in countries with strong governance.
But disposables? Ban that shit
My point being, with time performance might go up. But instead of that making my device faster/long-lasting, developers use that extra performance to cram in more stuff, at the end of which I come out only slightly better if not worse (as is in my case)
That said, it leaves a salty taste in the mouth to see
> Orion is part of the broader Kagi ecosystem
and
> Supporters (via subscription or lifetime purchase) unlock a set of Orion+ perks
I would imagine that paying for Kagi is also a vector for having the paywalled features of your browser.