imagine releasing agi and calling it 'spud' x.com/theinformation…
@alexjc
-
Cursor’s Business Model Conflict with User Pricing Demands
By
–
All of Cursor's PR problems stem from the fact they are in an adversarial relationship with their own users. Users predominantly want the best frontier models at cheap prices, but Cursor can't provide those competitively without taking a loss on API pricing. Cursor's own
-
MIT License Violation: Attribution Requirements in Kimi K2.5 Fork
By
–
You meant violation not valuation? I think that's the biggest problem: they tried to pass it off as their own work, but the last clause of Kimi K2.5 modified MIT license requires prominent attribution. I expect there'll be emergency licensing meetings happening shortly…
-

Cursor’s Unlicensed K2.5 Model: Strategic Misstep Analysis
By
–
A member of the Moonshot team claimed (in now deleted tweets) they confirmed Cursor's new model is based on K2.5 without a license. Hard to not see this as a massive strategic mistake of Cursor's management and the board. If you're going P0 "War Time" all-in on a frontier coding
-
Language Models Struggle with Esoteric Programming Languages
By
–
All models struggle in this benchmark because languages are: Brainfuck, Whitespace, Unlambda, Shakespeare. 😅
— Alex J. Champandard 🌱 (@alexjc) 19 mars 2026
If you actually pick a useful but still esoteric language like Joy, the frontier models do great (they *can* reason), but the open source ones struggle (they memorize). https://t.co/E5Mozy0yEBAll models struggle in this benchmark because languages are: Brainfuck, Whitespace, Unlambda, Shakespeare. If you actually pick a useful but still esoteric language like Joy, the frontier models do great (they *can* reason), but the open source ones struggle (they memorize).
-
3D Model Rasterization and Image Rendering Process Explained
By
–
Say there was a rasterization or rendering step in the program which converts that transformed/processed 3D model into an image?
-
3D Model Processing Pipeline for Image-to-Image Transformation
By
–
Can you imagine a piece of code that takes the 3D model data, transforms/processes it, and then passes it on to the next Image-To-Image step? Let's call this the full program, because the word pipeline seems to be difficult.
-
3D Model Processing and Geometric Transformations in AI Pipelines
By
–
Hypothetically, if the full pipeline can be shown to do rotations/transformations, then by your explanation of geometric transformations above, then it *must* be processing 3D model data?
-
Rendering Pipeline Logic: Generative Processing Inclusion
By
–
If the rendering pipeline includes both the processing of the 3D model as well as the generative part, then the answer must be "Yes" too because the first part does it and it's included? (This is basic logic, not a trick either.)
-
Frontier Models: Cleaning Up Lower-Generation AI Output
By
–
The biggest usecase for advancing the frontier models is to clean up slop written by frontier(n-1) models! Arguably, skilled programmers writing building on quality code could manage just fine on prior generations of models by just improving tools, harnesses, skills, etc. With
