Earlier quoted context omitted.
Thankfully he didn't say that they're all like that. Instead he pointed out the few that are as a well known example of similar behavior. If you reread the comment with a fresh mind you'll notice that you misunderstood what he wrote
When attacking archetypes of people, there is some responsibility to make clear who you’re attacking and why, even to someone who’s not being hyper-open-minded. At least if you want them to learn from you: which may or may not be your goal. When you attack/signal you’re on the offensive, it is foolish to believe that they won’t knee-jerk attack back and become closed minded at least a little. Regardless, the “misinte…
Previewing GPT‑5.6 Sol: a next-generation model
391–400 of 797 posts
Re: Previewing GPT‑5.6 Sol: a next-generation model
#392Other than the worst naming I have ever seen (Sol / Terra / Luna), the pricing is still expensive: > GPT‑5.6 is priced per 1M tokens across three model sizes: > Sol is $5 input / $30 output; > Terra is $2.50 input / $15 output > Luna is $1 input / $6 output. The OpenAI casino has never been more ready to take your money on gambling even more tokens.
> For GPT‑5.6 and later models, cache writes are billed at 1.25x the model’s uncached input rate
Charging for cache writes is cringe and literally only Anthropic did it. Anyway this does mean the "real" prices are +25% on top of what you wrote there.
Re: Previewing GPT‑5.6 Sol: a next-generation model
#393I think GPT writes code the best. How well will it write in version 5.6? It gives me chills. Recently, I went head-to-head with GPT on nearly 2,000 lines of code, and GPT's solution was superior and faster. I even referenced multiple codebases on GitHub while trying, but they were incomparable to GPT. So using GPT brings both fear and excitement. The fear comes from realizing that this level of code is now the averag…
Re: Previewing GPT‑5.6 Sol: a next-generation model
#394Earlier quoted context omitted.
>Unless you're running Linux yourself, it can absolutely be taken away.
Yes. The difference is obviously that full, fat Linux runs on a superset of anything a layperson would call a computer, and can be built from source on roughly the same set of hardware. Running the full, fat Deepseek (as in the 1.6T model, unquantized) is too big to run on anything a layperson would call a computer, and being able to actually build it is even harder.
Re: Previewing GPT‑5.6 Sol: a next-generation model
#395Earlier quoted context omitted.
At a certain rate we will be able to move towards continuous / real-time inference systems. The discrete, turn based solutions are quite confining with how they must be trained. Continuous and real-time would fundamentally alter the domain. From an information theory perspective we are still in dial-up territory with regard to the actual information rate. 750 tokens per second would be a really bad dialup connection.…
Your comment made me think of another real time. Real time, dynamic code/apis. Imagine a world where there is no code, just things mildly handshaking and then creating data APIs on the fly. Where communication is fuzzy and locked in on an individual basis. No years of RFCs, no RFCs at all, just... data. Just data, man. An API arbitration aberratically assigned at authorized access, abridged and annotated, analyticall…
Re: Previewing GPT‑5.6 Sol: a next-generation model
#396Earlier quoted context omitted.
At a certain rate we will be able to move towards continuous / real-time inference systems. The discrete, turn based solutions are quite confining with how they must be trained. Continuous and real-time would fundamentally alter the domain. From an information theory perspective we are still in dial-up territory with regard to the actual information rate. 750 tokens per second would be a really bad dialup connection.…
Your comment made me think of another real time. Real time, dynamic code/apis. Imagine a world where there is no code, just things mildly handshaking and then creating data APIs on the fly. Where communication is fuzzy and locked in on an individual basis. No years of RFCs, no RFCs at all, just... data. Just data, man. An API arbitration aberratically assigned at authorized access, abridged and annotated, analyticall…
Re: Previewing GPT‑5.6 Sol: a next-generation model
#397Re: Previewing GPT‑5.6 Sol: a next-generation model
#398Re: Previewing GPT‑5.6 Sol: a next-generation model
#399Earlier quoted context omitted.
At a certain rate we will be able to move towards continuous / real-time inference systems. The discrete, turn based solutions are quite confining with how they must be trained. Continuous and real-time would fundamentally alter the domain. From an information theory perspective we are still in dial-up territory with regard to the actual information rate. 750 tokens per second would be a really bad dialup connection.…
Your comment made me think of another real time. Real time, dynamic code/apis. Imagine a world where there is no code, just things mildly handshaking and then creating data APIs on the fly. Where communication is fuzzy and locked in on an individual basis. No years of RFCs, no RFCs at all, just... data. Just data, man. An API arbitration aberratically assigned at authorized access, abridged and annotated, analyticall…