Live data from Hacker News

GLM 5.2 and the coming AI margin collapse

martinalderson.com

171–180 of 495 posts

Re: GLM 5.2 and the coming AI margin collapse

#171
post #86

Earlier quoted context omitted.

If you're developing on top of LLM APIs directly, this is definitely not true. There are differences in how context caching works, in what's available through native harnesses, the types of tools you're fine-tuned on (GPT uses apply_patch while Claude uses edit, with different formats), the API surface (Agents SDK, Responses API, Managed Agents), cost structures, and best-practice guidance all around. Not to mention…

Exactly, as in, really, will they? Where and at what price, especially across an actual enterprise that needs to deploy them to lots of devs? There's much more than just the actual model. Of course my numbers are a sample of one and I am not spending a lot of money or time on it. Just lazily trying things on my "happen to have this" hardware. But basically trying out the Claude Code I'm used to from work but locally…

4.7 Flash is a small model that's almost a year old, which is ancient. And yes, your dinky GPU will not run anything worthwhile.

Just spend $5 on OpenCode Go and give GLM 5.2 a shot if you have the time. It's not quite as good as Opus, but it's more than good enough for many tasks.

Re: GLM 5.2 and the coming AI margin collapse

#172
post #5

I'm not convinced raw costs matter: 1. Compute costs collapsed since the advent of Cloud and yet hyperscalers still have fat margins. 2. Many open source office suites exist yet none compete with the ubiquity of gsuite or office. GitHub, Slack are similar examples. 3. Both Windows and macOS dominate the home desktop space despite free alternatives existing for a long time. 4. Many formerly open source infrastructure…

There's a huge case of survivorship bias when trying to recall historical analogues, because in every instance where margins collapsed and competition made the industry a commodity business, the big proprietary names are no longer with us. Here's a selection of examples, though: 1. Memory chip margins collapsed so much in the 80s that Intel exited the memory chip business entirely. At the time, they were known much m…

100% agree with the sentiment here, but a small nitpick - MS SQL originated as a port of Sybase onto (IIRC) OS/2.

Re: GLM 5.2 and the coming AI margin collapse

#173

> Of course, this was a hugely poor read of where the costs actually lie in AI. Training - while no doubt capex intensive - is a fixed, up-front cost. You spend hundreds of millions to train a model, then you are "done". I don't understand this point that people make. If you're consistently needing[0] to train new models and the cost of training relative to the % improvement seems to go higher, isn't this just a cons…

These models rely on knowledge that are embedded in their weights, if a new library is released, a new linux version comes out, some new protocol succeeds the previous one, you want your llm to know about it. Sure you can just add that into the context window, but that has its own problems. Unless new research, there are a few which look promising, gives a new method, training is going to be a constant cost sink. On…

it does not require training a model from scratch for it to be updated. the entire LLM training process is iterative. essentially each step (there are hundreds/thousands for a training run) yields a complete, usable model. tokens with updated data can be added on top essentially at any time in the future.

Re: GLM 5.2 and the coming AI margin collapse

#174

Earlier quoted context omitted.

Unlike all your examples, switching out an LLM is both cheap an easy. So easy that every 3 months or so new models are released and people grab them and start using them. The UX is the same regardless the provider. You send in a prompt, it spits back an answer. In all your other cases, the cost to switch is losing support and a difficult transition period. But in the case of LLMs, there was no support to begin with.…

Switching an agent harness is more difficult, especially on the enterprise/teams level. Once your team gets settled with Claude teams, cowork, and the various plugins, it’s going to be a pain in the butt to switch.

Is it? I switched to Kiro and it's essentially identical.. well a bit better because you get a better idea of what the harness is doing, but otherwise identical.

Re: GLM 5.2 and the coming AI margin collapse

#175
post #47

Earlier quoted context omitted.

Those solutions have moats: 1. the cloud moat is mostly around talent really. Try finding people who can self host the alternatives to S3 et al at the HA and the scale the businesses need. Those alternatives are usually not free either, and each product might have its creator acquired (and the product cancelled) or similar. if you're a larger business then the data lock in becomes a moat: getting your data out of the…

Linux has a very stable userspace syscall ABI. About as stable as Windows, and much more stable than MacOS or the BSDs. I agree with everything else though.

Most people don't directly call Linux syscalls though but go through glibc. It might even be unavoidable if you want to ship desktop apps as the library will use it. If it's that easy there wouldn't be Python's manylinux, flatpak base packages or Steam Linux runtime

Re: GLM 5.2 and the coming AI margin collapse

#177

Earlier quoted context omitted.

Unlike all your examples, switching out an LLM is both cheap an easy. So easy that every 3 months or so new models are released and people grab them and start using them. The UX is the same regardless the provider. You send in a prompt, it spits back an answer. In all your other cases, the cost to switch is losing support and a difficult transition period. But in the case of LLMs, there was no support to begin with.…

Switching out an LLM? What do you mean by this? Sure some models can run locally but in a company with lots do people they might not be willing to spend to self host a larger model that requires beefier hardware to host, plus all the complexity to scale that out to a bit internal user-base

Most of the AI companies have OpenAi compatible API's, so you just get a subscription from another provider and change the URL that your LLM Agent Harness uses to talk to the AI.

I use OpenRoutet which lets you switch between providers (Anthropic, ChatGPT, Z-AI) whenever you want. Sometimes I'll have two different models from different providers evaluate each other's answers.

Re: GLM 5.2 and the coming AI margin collapse

#178
post #5

I'm not convinced raw costs matter: 1. Compute costs collapsed since the advent of Cloud and yet hyperscalers still have fat margins. 2. Many open source office suites exist yet none compete with the ubiquity of gsuite or office. GitHub, Slack are similar examples. 3. Both Windows and macOS dominate the home desktop space despite free alternatives existing for a long time. 4. Many formerly open source infrastructure…

[dead]

Re: GLM 5.2 and the coming AI margin collapse

#179
post #97

I think the profits depend on how well they manage their fleet purchases (or possible sub-leasing?) to get high utilization without overloading or idle racks. Because accelerators like H200, B300 etc. are highly parallel and designed to run like 200 or maybe 300 sequences at once (depends on the model, just guessing). I assume they finance the hardware and that cost per device or rack is the same whether each unit is…

Someone on HN made a comment in one of these threads that we could bake the weights into something like Cerebras's wafer scale chips and serve essentially the entire world off a single wafer, which is a pretty wild thing to think about. You'd have to make new hardware any time you trained a model but that seems really worth it.

I think the future will have to include specialised host boards for memory chips.

What I actually want is an FPGA board with a very large number of DDR3/DDR4 RAM slots arranged in banks (2, 4, 8 or even more banks). I want an FPGA board that can hold 1TB of DDR3/DDR4 RAM.

The throttling point right now is not RAM, it's bus speed. Having different busses for banks of RAM alleviates that.

Re: GLM 5.2 and the coming AI margin collapse

#180

I also think we’ll approach a point where increasing intelligence is not really going to suddenly improve most work tasks. I bet that’s already happened actually. We’re oohing and aahing about models, when the ones a few versions ago did a good enough job for most of the dumb coding, etc we do

I’ve been on a GLM coding plan since they launched ~year ago and it’s been at „good enough“ since the start. Tangible behind absolute SOTA but like you say most coding isn’t rocket science.
Post reply on HN