Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Annoying and alarming things about OpenCode

wren.wtf

Post reply on HN
Print view View original

211–220 of 309 posts

Re: Annoying and alarming things about OpenCode

#211

Post by beepbooptheory »

saghm wrote: post #113
evnp wrote: post #101

Earlier quoted context omitted.

"There will be no curiosity, no enjoyment of the process of life. All competing pleasures will be destroyed. But always— do not forget this, Winston— always there will be the intoxication of power, constantly increasing and constantly growing subtler. Always, at every moment, there will be the thrill of victory, the sensation of trampling on an enemy who is helpless. If you want a picture of the future, imagine a boo…

That would be an example of a non-torturted metaphor. When you copy the famous quote verbatim and then substitute both parts of it for things that are almost entirely unrelated, it becomes tortured.

Is that right though? I feel like "tortured" is usually used more when one term is overly specific/over-fitted to the other. I've never heard it used like this, where it's about its provenance?

Not that anyone really cares here, but the gp quote isn't even really fundamentally a metaphor either way, its an exhortation to "imagine". The Orwell isn't even a metaphor!

Re: Annoying and alarming things about OpenCode

#212

Post by dboon »

driverdan wrote: post #189
dboon wrote: post #164

This prose feels extremely angry and ungenerous; abstractly, I agree with a lot of the points, but when I read this: > My conclusion is that OpenCode is clown-car turboslop with a security posture of “let me bend over for you daddy”. Everyone using it should stop using it. I do not want to keep reading. There are regular people who wrote this software. When did it become normal to talk about open source like this? Ho…

It's funny though. I haven't contributed to OpenCode but if I had I'd still laugh because I have a sense of humor. Don't take everything so seriously.

I promise I'm not normally uptight like this, but there's a difference between having a laugh and whatever this is. Like I said, this feels (a) legitimately angry and (b) in a spit flecked enraged way that has become popular. I guess if you're cool with people calling whatever you work on clown-car turboslop then more power to you.

Re: Annoying and alarming things about OpenCode

#213

Post by lilerjee »

I don't know whether other arguments are true, but some arguments in the end are right:

> Using LLMs for code generation feels like a dead end. ..., This is hostile to your ability to understand your code, beyond the fact that you didn’t write it.

What you get from AI is not worth of what you have invested for it in long period.

> Drawing answers directly from knowledge in model weights leads to hallucination even for multi-trillion-parameter models, so why bother making them that big?

Current AI is like the film company producing TV series or movies. "If similar stories do not exist or details are missing, screenwriters use imagination to fill in the gaps (remember hallucination? It's just a makeup.)", refer to the article https://devcyc.life/current-ai-is-like-the-film-company-prod...

Re: Annoying and alarming things about OpenCode

#214

Post by georgemcbay »

embedding-shape wrote: post #155
snapplebobapple wrote: post #121

Earlier quoted context omitted.

Got a link? Pi is suitably as to make search engines questionable

For the future, adding the related concepts/themes around hard to search for terms tend to do the trick. Instead of searching "go" for example, do "go programming language". Or instead of "pi", do "pi agent" or even "pi llm".

While this is a generally useful suggestion you are giving, for Go in specific you can just use "golang".

All of the major search engines have understood that as a stand-in for "Go the programming language" for many years.

Re: Annoying and alarming things about OpenCode

#215

Post by chuckadams »

wasabi991011 wrote: post #148
intothemild wrote: post #139

Earlier quoted context omitted.

That's the thing. You can't change it. They do not accept PRs from what I've seen. Whilst it's open source it's only in name. There may be the odd PR accepted from outside the team. But very very rarely. It's honestly embarrassing to call this open source. Pi on the other hand, whilst they have their own unique issues with PRs, if you came to them with a genuine problem, or fix, they seem to accept it. Now I point ba…

Open source doesn't mean that it has to accept PRs. It has never meant that the code author's must accept community contributors. OpenCode has an MIT license, which allows you to copy/fork the code and modify it how you see fit. Please review the open source initiative's definition of open source: https://opensource.org/osd

SQLite famously doesn't accept PRs either, and it's public domain.

Re: Annoying and alarming things about OpenCode

#216

Post by [deleted] »

beepbooptheory wrote: post #211
saghm wrote: post #113

Earlier quoted context omitted.

That would be an example of a non-torturted metaphor. When you copy the famous quote verbatim and then substitute both parts of it for things that are almost entirely unrelated, it becomes tortured.

Is that right though? I feel like "tortured" is usually used more when one term is overly specific/over-fitted to the other. I've never heard it used like this, where it's about its provenance? Not that anyone really cares here, but the gp quote isn't even really fundamentally a metaphor either way, its an exhortation to "imagine". The Orwell isn't even a metaphor!

[deleted]

Re: Annoying and alarming things about OpenCode

#217

Post by verdverm »

wasabi991011 wrote: post #148
intothemild wrote: post #139

Earlier quoted context omitted.

That's the thing. You can't change it. They do not accept PRs from what I've seen. Whilst it's open source it's only in name. There may be the odd PR accepted from outside the team. But very very rarely. It's honestly embarrassing to call this open source. Pi on the other hand, whilst they have their own unique issues with PRs, if you came to them with a genuine problem, or fix, they seem to accept it. Now I point ba…

Open source doesn't mean that it has to accept PRs. It has never meant that the code author's must accept community contributors. OpenCode has an MIT license, which allows you to copy/fork the code and modify it how you see fit. Please review the open source initiative's definition of open source: https://opensource.org/osd

I pinged the OC devs to get someone else's PR merged to fix a slop artifact, they did indeed merge external PRs.

Like many popular Ai projects, they get 1000s of slop PRs. They are also working on a v2, so fixes to old code are much less likely to land now.

Re: Annoying and alarming things about OpenCode

#218

Post by verdverm »

Hizonner wrote: post #91
LaurensBER wrote: post #12

I feel that a better title for this article would be: "Some minor annoyances that, when fixed, would improve OpenCode" # Prompt Cache Misses > It globs your filesystem and re-reads AGENTS.md (injected in turn-0 system prompt) on every SSE turn. If you put a quick note in AGENTS.md to be read in the next session, you immediately force a full re-evaluation. > Personal favourite: it puts the current date in the turn-0 s…

> > The default system prompt is opinionated (fine) but it has shit opinions (not fine). It took me a while to figure out why my agent kept saying “Use ABSOLUTELY NO COMMENTS” when dispatching subagents. > Okay, so change it? Any LLM is opinionated, this system prompt enforces consistency across different models which seems reasonable. OpenCode embeds scatters bad coding policy all over all of its inbuilt prompts, in…

yet OpenCode is #1 harness per Artificial Analysis

https://artificialanalysis.ai/agents/coding-agents?coding-ag...

Re: Annoying and alarming things about OpenCode

#219

Post by vdomi »

schmorptron wrote: post #191
trollbridge wrote: post #179

Earlier quoted context omitted.

This seems to be quite common. You start with OpenCode (assuming you're someone who skips all the Claude Code hype); then you start thirsting for more, and switch to oh-my-pi. I generally view the kind of code in projects like OpenCode to be the same as binary machine code, and the harness that works on it is the compiler. The source code is the prompts (I guess), except we live in a weird state now we use the existi…

Yeah, this has been my progression as well. Maybe next it'll be just using plain pi when you figured out exactly what you want from omp and what you don't

I like how browser and websearch is handled in omp. But I only like these two features, it might be time for me to actually spend some time with pi
Post reply on HN