I agree. I don't see why something getting more competition and plummeting costs is going to get significantly worse. Meta being Meta is not the strongest argument.
The Hash-anchor edit guy! Sincerely great idea, I used it in my own toy harness to good effect. I just checked this out, never tried it before, and its great! Clearly a well-iterated design with good choices made.
It is so refreshing to see real FOSS and not a grift. Simple openrouter api key, and I'm going.
This is what I'm using from now on. You are doing the best work in this space.
We tried to vote for normal 21st century healthcare and the billionaires spammed race-baiting nonsense and backed an unconstitutional fascist to shut it down.
Man, its hard not to have a reaction to another BaaS. Every "pricing" page really goes to show that engineering took a backseat to rent-seeking.
There is an incentive to take advantage of users ignorance rather than instruct them. There is no incentive to make self-hosting easy or secure or sustainable.
This is literally $600/month for 250GB of storage with no SLA. Cool "value add" bro.
Sure, yeah, I saw grubhub happen too... but this is compute, not cookies. It gets cheaper.
I don't even get what "skeptical of AI" means. We made AI, many companies reliably teach computers every spoken language. I perform my white collar job with a massive AI multiplier to my productivity.
I'm typing this on a machine comparable to Japan's Earth Simulator, a $350M supercomputer.
I don't see why tokens/$ would suddenly stop dropping. Maybe this is the first time the cost of compute will plateau, but do have any reason to think so?
That isn't true. In a Codex or Claude Code instance, sure... but those are not the main users of APIs. If you are using LLMs in a service for customers, costs matter.
That is immediate-mode graphics. Fine when you are already power-budgeted for 60 frames each second. UIs typically use retained-mode graphics, with persisting regions.
Prompting LLMs for code simply takes more than a couple of weeks to learn.
It takes time to get an intuition for the kinds of problems they've seen in pre-training, what environments it faced in RL, and what kind of bizarre biases and blindspots it has. Learning to google was hard, learning to use other peoples libraries was hard, and its on par with those skills at least.
If there is a well known design pattern you know, thats a great thing to shout out. Knowing what to add to the context takes time and taste. If you are asking for pieces so large that you can't trust them, ask for smaller pieces and their composition. Its a force multiplier, and your taste for abstractions as a programmer is one of the factors.
In early usenet/forum days, the XY problem described users asking for implementation details of their X solution to Y problem, rather than asking how to solve Y. In llm prompting, people fall into the opposite. They have an X implementation they want to see, and rather than ask for it, they describe the Y problem and expect the LLM to arrive at the same X solution. Just ask for the implementation you want.
Asking bots to ask bots seems to be another skill as well.