upvote
Coupled with VSCode forks to manage them
reply
You know which one will win for sure. ones with the worst experience.

Vue and svelte are easy to use and learn/adopt. But look what won. React.js.

So whatever the ai agent with the vast user basae will win regardless.

---

I know it's a slippery slope, but given you brought up JS framwork analogy, I had to fall into it

reply
It's all about what story you can tell.

Cursor is easily the worst experience I've had with an AI harness, yet it was acquired for billions of dollars in spite of being a middleman tied to a ripoff of VS Code. None of the colleagues of mine who were touting it last year are still using it. But if you can make yourself look like the next big thing, you'll get money thrown at you. Just look at Omarchy.

A good experience necessarily takes time and careful thought. Nobody these days can do that while also remaining relevant, or even surviving.

reply
I mean as someone who was there at the time, early React was easy to learn and adopt. It’s complexity came later after it had already won

Now Angular v1, man… if I ever see another digest loop error in my life, I will scream

reply
So glad I never had to deal with Angular, especially v1. I tried learning it and it just seemed like it would actually make applications more incomprehensible than before. React originally addressed the actual problem that most frameworks mistook for not being that important. I still don't particularly like React, but it makes sense why it became popular.
reply
"Look, LLMs will free you from the tyranny of frameworks!"

"Uh, OK, so how do I get this thing working? Where are the docs?"

"Well, first you install its unique framework..."

reply
[flagged]
reply
Go doesn't have a good mod/plugin story for harness devs to provide to their users

I say this as a gopher who also has a custom harness written in Go, it's a real challenge compared to the TS setups, but TS plugins are also a security concern

reply
I agree! Comes with the territory of a compiled language I suppose?

I haven't given this much thought (I also just started with golang last year) but I'm assuming the only real path here is to provide extension SDKs in Lua or other languages whose interpreters have been implemented in go.

I think that's what grafana's k6 [1] does with a JS interpreter

[1] https://github.com/grafana/k6

reply
I was thinking I recalled something like that, but the nice thing about the TS ecosystem is that you can write the same language, importing and using the harness sdk types.

Go has the plugin package, but I haven't actually seen anyone use it (outside of toys and blog posts)

https://oneuptime.com/blog/post/2026-01-25-plugin-system-go-...

reply
curious your thoughts on my approach: https://docs.wingman.actor/extend/plugin-quickstart/
reply
fails at step two, precompiled binary is already built, you can't change the code

why not just use an SDK where you are using a plugin?

reply
Why isn’t IPC good enough?
reply
My custom harness has a dagger based environment, binary runs in the host, every tool call and file modification creates a new layer in a container - for better session time travel and forking

It may work for some things, but you really want to be wired into that system to do the more interesting things.

reply
none are as great as https://wingman.actor!

jk its trash

reply