dougbarrett

I think they meant the 'Plan with Opus' model. shift+tab still works for me, the VS code extension allows you to plan still too, but the UI is _so_slow with updates.

I wonder if it's a difference between SSE and HTTP streaming support? I've been working on a tool for devs to create their own MCP tools and built out support for both protocols because it was easier for me to support both protocols vs explaining why it's not working for one LLM client or another.

Batching is a pattern I’ve had to manually build in the past to push large amounts of analytic data to a database. I’d push individual events to be logged, map reduce those in batches and then perform insert on duplicate update queries on the database, otherwise the threshold of incoming events was enough to saturate the connection pool making the app inoperable.

Even optimizing to where if an app instance new it ran the inert on update for a specific unique index by storing that in a hash map and only running updates from there on out to increase the count of occurrences of that event was enough to find significant performance gains as well.

I wonder why they didn’t just continue this under the Alexa product?

I've seen this argument come up frequently and I find this is just a weird hill to die on. I can see where the author is coming from as far as taking you out of the experience, but QR codes and NFC absolutely have a place in the restaurant ordering experience and I'm here for it.

Plus, if you’re writing the front end in react or something else, that’s essentially the “other endpoint”. You’re just moving that back closer to the source of the origin.

This is definitely possible, and this is definitely already happening. It may be hard for some people to even tell the difference between an AI generated script/audio vs 100% human curated.

AWS beanstalk allows you to run on very cheap instances, even cheaper if you get a plan and commit to a term.

It’s not a 1:1 experience, but I’ve enjoyed it as an alternative to Heroku for sure. Alternatively, you could spin up a server and install dokku which is pretty close to a shipping experience, but still requires some maintenance and hand holding.

I've been using echo for years. Has a great balance of adding helpful utilities while also not imposing bad patterns.

Have you considered doing payment processing, then the output goes to the users preferred payment method? So say my customer pays with a CC (via stripe or braintree on your end) - you could pass that payment along to PayPal, stripe, crypto, etc.

To me, that would be a useful alternative because all I'll need to do is enter my CC info, or preferably use apple pay which is much faster than me needing to ensure I have paypal, zelle, etc. installed.

I'm probably in the minority here, but I know for older people paying by CC is going to be easier than using an alternative payment processor.

This is really cool! I tried building something more basic than this a few years back, but this looks a lot more mature. I'll definitely be following and testing it out on a few small projects.