All that keeps jumping out at me is how they've set it to refuse giving users thinking tokens and prompts for full reasoning in output. Just drives me further away; I may not stop using Claude completely for now, but I'll be moving even more of my primary workload to Chinese providers. That's where openness and freedom is now at.
Noobs are burning tokens like "make me an app that does this" whereas an experienced engineer would go with certain language, framework and architecture in mind.
How exactly does specifying the language, framework, and architecture in advance save a meaningful amount of tokens? I'd expect saying "make me an app" and "make me an app using Swift and SwiftUI" would be pretty close in terms of token usage. You save maybe one look up by the LLM for "what is the preferred language for writing an application for iOS?".
Now this prompt has huge variety of implementation details. Language? PHP/Ruby/Python/Java/Typescript? In each of them then there are tons of frameworks, templating engines, ORMs, database servers, frontend tooling, bundler, frontend framework alone has several dozen candidates from React, Preact, Vue, Svelte and what not.
So if you really know your craft, you'll already be knowing what specific implementation you need so let us not discount the existing expertise here.
skeledrew · · focus · HN ↗
wg0 · · focus · HN ↗
kabes · · focus · HN ↗
wg0 · · focus · HN ↗
Jeremy1026 · · focus · HN ↗
wg0 · · focus · HN ↗
Now this prompt has huge variety of implementation details. Language? PHP/Ruby/Python/Java/Typescript? In each of them then there are tons of frameworks, templating engines, ORMs, database servers, frontend tooling, bundler, frontend framework alone has several dozen candidates from React, Preact, Vue, Svelte and what not.
So if you really know your craft, you'll already be knowing what specific implementation you need so let us not discount the existing expertise here.