271–280 of 361 posts
Setting up a limit of spending is even more difficult
In case it's helpful to anyone, https://openrouter.ai/google/gemini-3-pro-preview is useful to know about. Adding another layer on top of Google's own APIs adds latency, lowers reliability, and (AFAIK) doesn't allow batch mode - but if that's tolerable, it avoids the mess that is Google Service Account JSON and Cloud Billing.
I complained about this on HN recently and Logan responded and asked me to email him with feedback on how I'd like the experience to work (I didn't, sorry Logan, been busy :)) - Logan, to his credit, is very active everywhere reading and soliciting feedback. I think they're going to be giving it a pretty big bump on ux/ui of AI studio next month. It's easy to see he's a super smart guy trying to build something compl…
This has often been the case (Google dev rel soliciting feedback) and they very rarely take meaningful action. Like firing a bug report with Apple. They'll get to it when it becomes strategically important to. Why making it easier to pay them isn't always strategically important, I'm not sure.
Using metaphors is dangerous, but I would dare to say that big tech AI is like cement suppliers. It's too low level of a service. In civil engineering you have the option to contract value added suppliers that will give you prefabricated pieces in concrete or steel you could be using to build your construction. I'm seeing a lot of AI firms building value added services on top of big tech "foundational" AI offerings.…
Openrouter is roughly at that level of value-add. With plenty of competition now, since being able to charge 5% on your AI spend just for having sane billing, spending controls (actually enforced per-api-token budget limits!) and easy sign-up is an insanely profitable business proposition On the other hand I think it's fair to criticize the model hosts for not offering the same
But there's a lot more functionality that becomes relevant when building in production. We do automatic fallbacks, route between providers based on data policies, syndicate your data to agent observability tools / your logging platform of choice, user-level and api-key-level budget management and model allow/block lists, programmatic API key management, etc, etc. More good stuff shipping all the time!
Earlier quoted context omitted.
The number one rule of business that should just be passively reiterated to everyone working in any type of transactional field: 1. Never make it hard for people to give you money.
Parking apps don’t seem to care much for that. They know you’ll jump through their shoddy UIs and data collection because they have a local monopoly. Often with physical payment kiosks removed and replaced with “download our shitty app!” notices.
Earlier quoted context omitted.
I can’t tell if you might be joking. If you are, the rest of this comment is irrelevant. That general idiom is old and fairly widely used. There was a Seinfeld episode in 1997 in which Elaine talked about “…not lurching around like a caveman.” If you’re objecting to criticism of writing code by hand, the phrase is almost invariably used in a self-deprecating way, acknowledging some inefficiency or old-fashioned behav…
Thank you. Seinfeld reference does it. About the "hard way", everything in the article is screaming that OP's new way of coding is the hard way, not the other way around
He should have used OpenAI or Anthropic - instead of using Google, like a Neanderthal.
I complained about this on HN recently and Logan responded and asked me to email him with feedback on how I'd like the experience to work (I didn't, sorry Logan, been busy :)) - Logan, to his credit, is very active everywhere reading and soliciting feedback. I think they're going to be giving it a pretty big bump on ux/ui of AI studio next month. It's easy to see he's a super smart guy trying to build something compl…