james2doyle

However, I likely wouldnt suggest Pi (or even opencode) to someone who I would also suggest Juggler. They just dont feel like the same type of user, in my opinion.

I do think you could take a look at ChatWise, Kelivo, Rikkahub, Jan, and Waku if you wanted to see who your real competitors are. Again, in my opinion.

Those are full standalone GUIs with workspaces and built in tools that help you get things done without requiring any terminal commands.

Comment · 1 month ago

The biggest win for me is they can have state. So you can log in to an MCP (via oauth) and not worry about having to refresh tokens locally or in the ENV. I use it for Trello. I log in, then I can call all the data about my board. No CLI to install, no token to copy-paste somewhere. It just opens a browser tab to log in when required, next, next, next, and it works.

Comment · 1 month ago

Plan mode is for me not the agent.

I also bounce around to lots of different models. Some are cheap and dumb, some not. When unfamiliar with a model, the last thing I want it to allow file edits and destructive tool calls. Having a mode explicitly for that is helpful.

Comment · 1 month ago

2.5 Pro or the regular 2.5?

I always found that those Mimo models to be really good at tool calling and following instructions

Comment · 1 month ago

Not only that, the output of tps is high. So not only can it handle most mid-level tasks perfectly fine, but can do it with speed!

Comment · 2 months ago

Funny enough, I have a simple test that I have been running on each new model that catches my eye on OpenRouter. It is just a short prompt that asks the model to research yesterdays news and summarize it in a specific format along with a critique of the article or a highlight of any bias: https://gist.github.com/james2doyle/6afb04ea6b18e1a36bc45258...

I have been doing this test for about a year now. I run it on different harnesses and apps as well just to give me an idea of what they differences between them might be. Since I have been running it for a while now, I have a good sense of the correlation between this output and how the model will be on the rest of the things I want it to do.

I would say that almost every model (just tested Mercury 2.5 Preview and IBM Granite 4.2-8b) are pretty much the same on this task. Some are more diligent with how many sources they go out and get, but for the most part they are all very close in quality and will follow the instructions very well.

So saying "everything struggles" with that has just simply not been my experience.

Comment · 2 months ago

> `hx-alpine-compat` - smooths over compatibility issues between htmx and Alpine.js

I looked into this when I tried HTMX 4 on a project earlier this year. I actually found that https://alpine-ajax.js.org/ was smaller than HTMX while providing all the features I needed. It is one of the sanctioned projects they link to so I felt good using it

Comment · 3 months ago

Nice. I’ve been using the new split tabs in Chrome. Works perfectly. I believe Firefox had this first?

Comment · 3 months ago

I used HTMX to serve my HTML partials. My HTML partials got too big. Not HTMXs fault. How do I fix that? Split them up? Use lazy loading? Pagination? That isn’t clear. I settled on a solution that gave me the least compromises while not abandoning the sprit of HTMX and HATEOAS.

HTMX has a whole section on their site dedicated to reasons not to use HTMX: https://four.htmx.org/essays#counterpoints

Alpine Ajax is actually promoted on their site as an alternative option but to stay within the HATEOAS universe: https://four.htmx.org/essays/alternatives#alpine-ajax

I tried building something more than a like-button or simple search. It wasn’t that easy to wrangle once it got more complicated.