Earlier quoted context omitted.
I've said it before but no one takes it seriously: LLMs are only useful if you're building something that's already in the training set ie already commodity . In which case why are you building it ???
"LLMs are only useful..." Is likely why no one takes you seriously, as it's a good indication you don't have much experience with them.
Cerebras Code now supports GLM 4.6 at 1000 tokens/sec
91–100 of 135 posts
Re: Cerebras Code now supports GLM 4.6 at 1000 tokens/sec
#92Earlier quoted context omitted.
I just asked glm-4.6 how to setup a z.ai api key with claude code and it kept on saying it has no idea what claude code is... Quite funny, actually.
Ask and you shall receive! https://docs.z.ai/devpack/tool/claude tldr "env": { "ANTHROPIC_AUTH_TOKEN": "your_zai_api_key", "ANTHROPIC_BASE_URL": "https://api.z.ai/api/anthropic" } Although if you want an Actually Good Experience I recommend using Claude Code Router https://github.com/musistudio/claude-code-router because it allows you to intercept the requests and forward them to other models. (e.g. GLM doesn't seem…
Re: Cerebras Code now supports GLM 4.6 at 1000 tokens/sec
#93Earlier quoted context omitted.
The industry of "software" is so large... While I agree with web development going this route, I'm not sure about "everything else". You could argue that that's the bulk of all software jobs in tech, and you'd likely be correct... But depending on what your actual challenge is, LLM assistance is more of a hindrance then help. However creating a web platform without external constraints makes LLM assistance shine, tha…
Well, there are certainly kinds of code LLMs would struggle with, but people generally underestimate what LLMs are capable of. E.g. Victor Taelin is implementing ultra-advanced programming language/runtime writing almost all code using LLM now. Runtime (HVM) is based on Interaction Calculus model which was only an obscure academic curiosity until Taelin started working on it. So a hypothesis that LLMs are only capabl…
https://github.com/GoogleCloudPlatform/aether
Note: the syntax is ugly as a trade-off to make it explicit and unambiguous for LLMs to use.
Re: Cerebras Code now supports GLM 4.6 at 1000 tokens/sec
#94I used their $50 plan and with the previously offered Qwen3 coder 480B. While fast - none of the “supported” tools I tried were able to use it in a way that didn’t hit the per minute request limit in a few seconds. It was incredibly frustrating. For the record, I tried OpenCoder, VSCode, Quen Coder CLI, octofriend and a few others I don’t remember. Fast forward to now, when GLM 4.6 has replaced Qwen3 coder in their s…
Re: Cerebras Code now supports GLM 4.6 at 1000 tokens/sec
#95Earlier quoted context omitted.
It just depends on what you are doing. A green field react app in typescript with a CRUD API behind? The LLMs are a mind blowing assistant and 1000t/s is crazy. You are doing embedded development or anything else not as mainstream as web dev? LLMs are still useful but no longer mind blowing and often produce hallucinations. You need to read every line of their output. 1000t/s is crazy but no longer always in a good w…
I've said it before but no one takes it seriously: LLMs are only useful if you're building something that's already in the training set ie already commodity . In which case why are you building it ???
Re: Cerebras Code now supports GLM 4.6 at 1000 tokens/sec
#96I used their $50 plan and with the previously offered Qwen3 coder 480B. While fast - none of the “supported” tools I tried were able to use it in a way that didn’t hit the per minute request limit in a few seconds. It was incredibly frustrating. For the record, I tried OpenCoder, VSCode, Quen Coder CLI, octofriend and a few others I don’t remember. Fast forward to now, when GLM 4.6 has replaced Qwen3 coder in their s…
Re: Cerebras Code now supports GLM 4.6 at 1000 tokens/sec
#97Earlier quoted context omitted.
This is where Rust's "if it compiles, it's probably correct" philosophy may come in handy. "Shifting bugs left" is even more important for LLMs than it is for humans. There are certain tests LLMs can't run, so if we can detect bugs at compile time and run the LLM in a loop until things compile, that's a significant benefit.
My recent experience is that llms are dogshit at rust, though, unable to correct bugs without inserting new ones, going back and forth fixing and breaking the same thing, etc.
Re: Cerebras Code now supports GLM 4.6 at 1000 tokens/sec
#98Earlier quoted context omitted.
It just depends on what you are doing. A green field react app in typescript with a CRUD API behind? The LLMs are a mind blowing assistant and 1000t/s is crazy. You are doing embedded development or anything else not as mainstream as web dev? LLMs are still useful but no longer mind blowing and often produce hallucinations. You need to read every line of their output. 1000t/s is crazy but no longer always in a good w…
I've said it before but no one takes it seriously: LLMs are only useful if you're building something that's already in the training set ie already commodity . In which case why are you building it ???
Re: Cerebras Code now supports GLM 4.6 at 1000 tokens/sec
#99Earlier quoted context omitted.
I feel the same and it's also why I can't understand all these people using small local models. Every local model I've used and even most open source are just not good
GLM-4.6 is on par with Sonnet 4.5. Sometimes it is better, sometimes it is worse. Give it a shot. It's the only model that made me (almost) ditch Claude. The only problem is, Claude Code is still the best agentic program in town and search doesn't function without a proper subscription.
Re: Cerebras Code now supports GLM 4.6 at 1000 tokens/sec
#100I have a lot of questions about how models are run at scale; so curious to know more. With such a massive wafer as chip as Cerebras, it feels like perhaps switching might be even more consuming. Or maybe there's some brilliant strategy to have multiple contexts all loaded that it can flip between! Inventorying & using so much ram so spread out is it's own challenge!