OpenAI really should as this too, even to Plus. I’m already paying more for ChatGPT than I use, give me some free API tokens to play with (there is a free tier for data sharing, but only older text generating models)
1,807 karma · joined March 1, 2013
OpenAI really should as this too, even to Plus. I’m already paying more for ChatGPT than I use, give me some free API tokens to play with (there is a free tier for data sharing, but only older text generating models)
I am using the single prompt approach with GPT5.4, which is free, but it’s not reliable. Using Jev I’d decompose the prompt into a bunch of smaller questions, then I’d combine the answers in software. I’m super excited to try Jev out.
If you said: Americans usually incorrectly think of Western Europe as those countries not partially or fully under control of the Soviet Union during the Cold War, then I’d agree with you.
“First rocket to launch from Europe outside Russia” would have been perfectly correct.
Note that you can run Convex on top of your own Postgres, and we do this for our internal apps, with very nice performance (plenty for our internal use cases).
This is why Rust (it’s a systems programming language) and LSP (the language server protocol invented by VS Code) are not explained in the article.
I am hoping I don’t have to define the words I used, but if in doubt, Google or ChatGPT are your friends.
- All our shipments in one UI (instead of searching trough our mail boxes or going to several merchant apps/sites)
- LLM processes update emails, but everything can be manually adjusted (or created from scratch)
- We have a bunch of destinations we order to (work, home, different pick-up spots), this lets me see where I have to pick up and with which pick-up code
- Real-time sync in case we update something, the other person sees it immediately
- PWA, with animations, feels as good as native on mobile
- $0 running cost (I only paid for AI sub when vibing this)
Desktop: https://imgur.com/a/HD9mCIr Mobile: https://imgur.com/a/EAuJiqH
1. Durability extends to the client. Replicated db might ack a write to client, but what if that ack gets lost on the way back over network? If client talks to the DB over simple HTTP, the write might first look like a failure. Can the client retry?
2. Human perception times are biological and don’t change much. But everything in the tech stack has gotten so so much faster since the 80s. Throughput matters, sure, but latency (relatively speaking), is much less of a constraint now than it was.
Should the AI sidebar be on the left, or on the right? At some point they swapped them automatically, which was jarring (maybe a bug). But now I realize that if I'm not the one primarily writing code and navigating it, then I prefer agents in the "primary" position on the left (esp. if I have the browser on the left half of the screen, the agents are in the middle).
What annoys me the most about Cursor is the random stuff that breaks (due to its nature of VS Code fork).
The tab experience is still unparalleled. The cost might be worse than Codex/Claude sub, but they are all much, much, much cheaper than API pricing, so depends on your POV.
The first page of the score card mentions that this model is not capable to replace engineers.
Hmm...
2. Support Fish too. Having one language that can generate zsh (macOS default), Fish (power users default), and bash would be really nice!
This seems too simplistic of a description of how money would work in such a world. Money is just a way to distribute your power to influence people. You never pay for machines or software. Think about buying anything, say a pen. You do not really pay for the metal in the pen. You pay the cost associated with extracting and processing the metal by humans along the production chain. If there were no humans along the chain, the cost could go down to zero.
So far, there are no “AIs” being paid.
I also think Saturn's rings don't wobble that fast.
You’d need at least some hash of sources + test results, and check that it matches that (in CI).
And you’d still deal with environment differences.