Simon Klee

Joining @anomalyco to build @opencode

@LukeParkerDev Vite+ is the the ruby on rails of tooling. Vite++ on the other hand, is Vite+ with objects ­- but that is first coming next year.

I don’t know what Vite+ is and I’m too scare to ask

If all you want to do is write tests then this is the job for you

I'm thrilled to introduce: loom! The first signal-based component framework for Go. You can use it today to build terminal UIs and web SPA.

@1slimewell @opencode Next release: with sound and no way to mute

@simonklee @opencode is this gonna happen in my tui

@Neolectron @opencode Need Kit’s voiceover for that

@simonklee @opencode I thought it was a kitlengton pr at first. I've been conditionned

@gabrielstuff @Huggiapp @aisdk It did get better

@jasonkneen @Huggiapp @aisdk OpenTUI is great but Tables support was not that great. Did it get better recently ?

Introducing "OpenTUI x AISDK" by @Huggiapp -- an @aisdk OpenTUI interface for gorgeous terminals in React + TypeScript. Primitive based TUI where everything you see is an extension that can be replaced/customised and hot reload. Create extensions to add / @ commands, create dialogs, providers, features, replace anything from a runtime core extension manager (also replaceable) and comes with skills to do all that. Write an @aisdk chat UI for web, then run the same code in a terminal. Coming soon, MIT license.

@robdotzip @ThePrimeagen It's not that bad — and you don't get distracted by typos's or syntax errors.

@simonklee @ThePrimeagen That’s wild. Im using this example the next I think “i dont have time”

it's crazy how many people think that 30 minutes a day isn't enough to learn anything. Who told you this? Unknown knowns are wild. People just ingrain hurdles in their head about the universe because some thought leader spoke into their life in the distant past.

Added a test for each key definition in the Kitty protocol spec. Caps Lock was typing gibberish in @opencode, but soon it wont. The real question is who uses caps lock!

@LukeParkerDev most prs that address real issues leave more spaghetti behind than they remove. Usually solving problem the obvious and wrong way. You still need a good mental model of the code to see how you can make things better and solve the issue.

opencode open source: the bottom line with community PRs are they are 99% of the time slop. even in the case that it looks like a good PR, there's suspicious things. this takes the team's time. we have to exactly repro the bug (because there's no steps in the issue/PR) there's a UI change with no before/after screenshots/video there's terrible code - we'd need to pull the code, refactor/cleanup, verify after there's tests that don't test anything - e.g. they always go green, even after you intentionally add the bug back at the end of the day, most the PRs are NOT worth the time it takes to properly go through it. in the case of an abysmal implementation we will instead just do the fix/feature ourselves from scratch. that being said - good OSS people still stick out, and their contributors get merged, and they get more trust, to be able to do bigger contributions. even when we merge community contributions they don't own the code once it merges - what if there's a fatal bug and we don't totally understand the new code? its completely fine to go disspear for a month as an OSS contributor. but that is risk we have to account for. at the end of the day the team has to tend to the garden and enforce some level of quality, sometimes this includes not merging PRs that look 80% good to go a lot of PRs will 'fix thing URGENT IT BREAAKS FOR EVERYONE ROLL THING BACK NOW', but then the linked 'fix' community PR breaks 1000s of other things.

@SevereSig @LukeParkerDev It’s true that there are too many and it makes it difficult to find the good ones for all the slop.

@LukeParkerDev You guys have too many to go through. I tried to make mine as few LOC as possible so it was clear and easy to review. I just wanted to test Qwen through LMStudio and ran into this little bug so I figured it was worth a shot to send a PR. github.com/anomalyco/open…

I'm looking at this issue github.com/anomalyco/open… but most issues here seem unrelated. Will try to fix, though.

This was released as part of 1.2.24 version of OpenCode.

@LukeParkerDev @jarredsumner Now, make it avoid depending on wall clock.

@jarredsumner I did get it simpler

my most complicated Bun segfault 'minimal' repro yet... :D

@thoughtlesslabs @opencode @thdxr It works. I just tried it.

i am joining @opencode* *unofficially. kind of just hoping @thdxr doesn't notice with how fast they are growing.

@iamdamianb @anomalyco @opencode Yes. Top priority.

@simonklee @anomalyco @opencode Hopefully the gif is not alluding to OC supporting Win95

Joining @anomalyco to build @opencode

@thdxr @anomalyco @opencode @ryanflorence Soon, we'll be making terminals feel like a Monday morning standup

@simonklee @anomalyco @opencode @ryanflorence look we made windows 95 instead

@__morse @thdxr @Shreyassanthu77 You mean X.com.

@thdxr @Shreyassanthu77 do you know any other company using discord for internal comms?

sent this to the team today everything great comes from being able to delay gratification for as long as possible and it feels like we're collectively losing our ability to do that