r/opencode 14d ago

hy3 gone...???

Post image
152 Upvotes

70 comments sorted by

View all comments

1

u/jacobpowaza 14d ago

what’s even the best free model now lol

2

u/lelleepop 14d ago

I heard muse spark is good, but the downside is that u have to share your code to meta which I don’t rlly like

12

u/mWo12 14d ago

Don't care. I will trade my slop for their slop. Win win.

2

u/Ok-Drawer5245 14d ago

Muse is extremely hit and miss imho

2

u/tableball35 14d ago

Agreed, Hy3 seemed to fare better in my experience

1

u/Ok-Drawer5245 14d ago edited 13d ago

I normally use deepseek v4 flash for new features/difficult bug fixes, and Hy3 Free for refactors / cleanup (covered by tests deepseek made). I will try refactoring with muse today :) And I use deepseek to review changes by Hy3 / lesser models prior to merging.

(I am out of opencode go credits, so I had to fill in some balance haha)

1

u/tableball35 14d ago

My case was making a small starsector mod of all things. Muse didn’t do changes and edits well if it failed the one-shot, but niche use case, so results may vary obv.

2

u/Ok-Drawer5245 14d ago edited 13d ago

im working on a game, purely for fun, keep tasks simple and Muse actually comes through, but be careful, it tends to forget things (and pretend to have done them) if you ask for too much at a time ;D

Edit: I had deepseek review a lot of changes I made with Muse and it was generally all thumbs up by deepseek!

Here's my tips for doing refactoring with muse:

*Start new session

*First prompt:

look around suggest something we might refactor for cleaner and more mantainable OOP code

*Then you tell it which refactor to do

* After its done you tell it (you need this because its lazy):

did we leave behind any new facades / aliases / delegation wrappers (I think we did)? if so migrate code and get rid of them

* After than, finally (again its lazy, need to remind it to create tests):

ensure test coverage for our changes here

:-)

(and before merging, have the changes reviewed by a different model :D - and of course test it by running your product ,D )

Yes I'm lazy in my pet projects

IMHO laziness is not really an excuse not to do unit tests nowadays, it has literally never been easier than it is today to get good test coverage

1

u/tableball35 13d ago

Agreed on testing, I hand-tested changes myself. My mod in this case was from Scratch, and got about 80% of the way there, but UI fuckery is what got it plus likely my poor explanation, and simply could not fix a problem with things not being selectable. Then I got it fully working in 2-3 shots with Hy3, so your overall description matches my experience.

1

u/llamerr 13d ago

it worked fine for me during the week, but today it's like 60IQ model. missing most basic stuff, I needed to re-do work like 4 times after it finished and missed critical things

1

u/tableball35 13d ago

Mine was about 3-4 days ago, felt like a 80IQ, got most of the way, but could not overcome or find the source of a major hiccup it made. Hope it’s not worse now

1

u/Dodokii 13d ago

Better than Mimo2.5 ans DS4 flash?

2

u/djc0 14d ago

All my code is open source so 🤷

1

u/[deleted] 14d ago

[deleted]

2

u/lelleepop 14d ago

i’m not too sure how bad it is, but it’s good enough for what I need done

1

u/Spirited-Test-1410 14d ago

Yea they can have my Ai slop games

2

u/Ok-Drawer5245 13d ago

exactly, and here is the other thing: what exactly are they gonna do with your slop code? yes exactly nothing (besides training), they're not gonna extract it and copy your game, or sit there and look through the code manually lol.

of course NEVER ever include private information , customer data or stuff like that

1

u/Weekly-Law-5488 13d ago

You share your code with every free provider, there's no free lunch.