4 ms·

"MiMoCode is built as a fork of OpenCode." Why not just contribute to OpenCode instead of creating a clone :/

by pmdlt 4mo ago

konart 4mo ago
To go a different path perhaps? You can't expect that all your ideas will land into a main repo and you really want to implement your vision while using a sane base.
orangeisthe 4mo ago
Why not?
ComputerGuru 4mo ago
[flagged]
- aaomidi 4mo ago
  What does “shamelessly forked” mean? It’s literally software meant to be forked lol
- moonu 4mo ago
  I don't think that's true? AFAIK OpenCode started as a TUI and their GUI app is Tauri-based, so don't think it was forked from OpenCode. You might be thinking of Cursor
- maxloh 4mo ago
  Do you even know what you're talking about? OpenCode started as an independent CLI project. Their desktop app is still in beta, and it was never a fork of VS Code. I believe they contain no code derived from VS Code.
- klaxce 4mo ago
  Are you thinking of Cursor? OpenCode is a TUI like Codex.
- ignoramous 4mo ago
  There were once two harnesses named OpenCode, one written in Go & the other in TypeScript (the more popular one). Kujtim Hoxha creates a project named TermAI. (SST folks) Dax & Adam join the project, rebrand it to OpenCode with Dax buying the domain, opencode.ai. Charm, the company behind the original libraries, acqui-hires Kujtim, who moves the project to Charm's organization, leaving SST unimpressed (due to VC involvement?) Allegations Charm rewrote git history and deleted GitHub comments. Dax claims ownership of the brand, forks project. For a time, 2 projects named OpenCode exist. Charm eventually renames its version to "Crush". https://news.ycombinator.com/item?id=44741894 https://news.ycombinator.com/item?id=44741894
  - scottyeager 4mo ago
    Back then they were both written in Go too. OpenCode was rewritten in TypeScript after Crush got the rename.
mythz 4mo ago
Because they want to optimize it for their models and don't want to be blocked by waiting for PRs to merge or be rejected. There's plenty of reasons to start your own fork that you have full agency of, as long as the OSS License is maintained anyone will be able to benefit from any new features they want to make use of.
- dannyw 4mo ago
  This is the beauty of open source :) KHTML -> WebKit -> Blink is a good example.
  - bigyabai 4mo ago
    KHTML is dead now, though. It was basically embraced, extended and extinguished by Apple and Google, who both wanted to take away the leverage of the community. Today, legacy KHTML maintainers are boxed-out of upstream decisions that might prevent Manifest v2 from swirling down the drain. I'd argue the story isn't very beautiful anymore.
    - gunapologist99 4mo ago
      True. Although the cruel twist is now that KDE's upstream decisions are boxing out X11/sysvinit/etc maintainers.
      - bigyabai 4mo ago
        X11 and sysvinit are not downstream KParts libs like KHTML was. KDE has no obligation to fork or support either project.
        bmacho 4mo ago
        KDE is not a fork, nevertheless KDE was building on X11 heavily and now they are trying to kill it. So while technically not the same story as if it was a direct fork of X11, practically they have the 'obligation' to support X11 indefinitely. KDE trying to kill X11 too is the same exact EEE that you mentioned as a sad story in regads of KHTML.
re-thc 4mo ago
> Why not just contribute to OpenCode instead of creating a clone :/ It's controlled by a different organization; in particular a startup in a "competing" space.
doctorpangloss 4mo ago
have you ever tried contributing a large number of changes to OSS?
postalrat 4mo ago
OpenCode can merge in all their changes if they want.
rurban 4mo ago
Opencode sits on a ton of important PR's, so they didn't want to wait. Everybody else switched to omp (oh my pi) already.
dartharva 4mo ago
Could just be a courtesy - Americans tend to be rather suspicious and hostile to contributions coming from China, and it might draw unwarranted attention from agencies and bad media.
est 4mo ago
There's a blog link https://mimo.xiaomi.com/blog/mimo-code-long-horizon https://mimo.xiaomi.com/blog/mimo-code-long-horizon I think there's simply too much changed.
polski-g 4mo ago
Because its currently impossible to "contribute to Opencode". There are over 500 pages of open issues, up from 78 less than a month ago. They are doing nothing to halt the garbage/duplicates that pop up, and not even addressing legitimate PRs/reports.

"MiMoCode is built as a fork of OpenCode." Why not just contribute to OpenCode instead of creating a clone :/

by pmdlt 4mo ago

"MiMoCode is built as a fork of OpenCode." Why not just contribute to OpenCode instead of creating a clone :/

To go a different path perhaps? You can't expect that all your ideas will land into a main repo and you really want to implement your vision while using a sane base.

orangeisthe 4mo ago

Why not?

ComputerGuru 4mo ago

[flagged]

aaomidi 4mo ago
What does “shamelessly forked” mean? It’s literally software meant to be forked lol
moonu 4mo ago
I don't think that's true? AFAIK OpenCode started as a TUI and their GUI app is Tauri-based, so don't think it was forked from OpenCode. You might be thinking of Cursor
maxloh 4mo ago
Do you even know what you're talking about? OpenCode started as an independent CLI project. Their desktop app is still in beta, and it was never a fork of VS Code. I believe they contain no code derived from VS Code.
klaxce 4mo ago
Are you thinking of Cursor? OpenCode is a TUI like Codex.
ignoramous 4mo ago
There were once two harnesses named OpenCode, one written in Go & the other in TypeScript (the more popular one). Kujtim Hoxha creates a project named TermAI. (SST folks) Dax & Adam join the project, rebrand it to OpenCode with Dax buying the domain, opencode.ai. Charm, the company behind the original libraries, acqui-hires Kujtim, who moves the project to Charm's organization, leaving SST unimpressed (due to VC involvement?) Allegations Charm rewrote git history and deleted GitHub comments. Dax claims ownership of the brand, forks project. For a time, 2 projects named OpenCode exist. Charm eventually renames its version to "Crush". https://news.ycombinator.com/item?id=44741894 https://news.ycombinator.com/item?id=44741894
- scottyeager 4mo ago
  Back then they were both written in Go too. OpenCode was rewritten in TypeScript after Crush got the rename.

mythz 4mo ago

Because they want to optimize it for their models and don't want to be blocked by waiting for PRs to merge or be rejected. There's plenty of reasons to start your own fork that you have full agency of, as long as the OSS License is maintained anyone will be able to benefit from any new features they want to make use of.

dannyw 4mo ago
This is the beauty of open source :) KHTML -> WebKit -> Blink is a good example.
- bigyabai 4mo ago
  KHTML is dead now, though. It was basically embraced, extended and extinguished by Apple and Google, who both wanted to take away the leverage of the community. Today, legacy KHTML maintainers are boxed-out of upstream decisions that might prevent Manifest v2 from swirling down the drain. I'd argue the story isn't very beautiful anymore.
  - gunapologist99 4mo ago
    True. Although the cruel twist is now that KDE's upstream decisions are boxing out X11/sysvinit/etc maintainers.
    - bigyabai 4mo ago
      X11 and sysvinit are not downstream KParts libs like KHTML was. KDE has no obligation to fork or support either project.
      - bmacho 4mo ago
        KDE is not a fork, nevertheless KDE was building on X11 heavily and now they are trying to kill it. So while technically not the same story as if it was a direct fork of X11, practically they have the 'obligation' to support X11 indefinitely. KDE trying to kill X11 too is the same exact EEE that you mentioned as a sad story in regads of KHTML.

re-thc 4mo ago

> Why not just contribute to OpenCode instead of creating a clone :/ It's controlled by a different organization; in particular a startup in a "competing" space.

doctorpangloss 4mo ago

have you ever tried contributing a large number of changes to OSS?

postalrat 4mo ago

OpenCode can merge in all their changes if they want.

rurban 4mo ago

Opencode sits on a ton of important PR's, so they didn't want to wait. Everybody else switched to omp (oh my pi) already.

dartharva 4mo ago

Could just be a courtesy - Americans tend to be rather suspicious and hostile to contributions coming from China, and it might draw unwarranted attention from agencies and bad media.

est 4mo ago

There's a blog link https://mimo.xiaomi.com/blog/mimo-code-long-horizon https://mimo.xiaomi.com/blog/mimo-code-long-horizon I think there's simply too much changed.

polski-g 4mo ago

Because its currently impossible to "contribute to Opencode". There are over 500 pages of open issues, up from 78 less than a month ago. They are doing nothing to halt the garbage/duplicates that pop up, and not even addressing legitimate PRs/reports.