Also resources - which are by far the coolest part of MCP. Prompts? Elicitation? Resource templates? If you think of MCP as only a replacement for tool calls I can see the argument but it's much more than that.
A few years ago I built a weekend project (paralleltext.io) which was fairly popular, even here on HN, but sadly I let the domain expire and was just sitting on my github. I finally took the time to revive it using Claude, with a few improvements for mobile experience. I've been getting occasional questions as to what happened to the project, so here's the revived version, hope you find it useful
Golang returning tuples but not having pattern matching is something I'll never get. I really feel it's a too dumbed down version of erlang/elixir, especially with this context passing business
Replying to myself because I'm sure someone from Zulip will read this thread: I also wish for a tiered channel system. Instead of muting some, I'd like to promote some to high priority, so my inbox can toggle between the ones I really care about and a general overview.
I’ve started working at a company that uses Zulip and it’s by far the best thought out UX I’ve ever worked with in a communications app. Sure there’s some polish needed but the general structure just lets me get to where I want, gives me an overview of everything going on, and generally makes me happy. I wish for more keyboard shortcuts maybe, and the mobile app needs the recent conversations view, but I’m sure they’ll get there.
Sorry but disagree. For me the main part is the resources, which automatically get mounted in the computing environment, bypassing a whole class of problems with having LLMs work with a large amount of data.