Good to see this exist. Inference providers quietly swap quant levels. Most users never check. A standard verifier from the model maker is the right move, would love to see other labs ship the same
The modified MIT clause is sneakier than people think. Hit 100M users or $20M a month and you have to slap "Kimi K2.6" on your UI. That covers any consumer app worth building. Not really open, more like free until you matter. Llama pulled the same move
Small models in the browser are a different optimization problem than small models on a server.
On server you chase throughput so you batch. In browser you're stuck at batch size 1, which means kernel launch overhead and memory bandwidth dominate, not FLOPs
The requirements gap point is underrated. AI guesses where a human would ask
By the time you catch it in review, you've already wasted the time you saved -_-
30+ years maintaining one of the most critical pieces of infrastructure on nearly every Linux and Unix system, and he's currently looking for a sponsor to fund continued development. Every company running sudo in production owes this man. Someone should fix that
Great job! This is the kind of project that should exist for every complex system
Systems like vLLM's codebase are massive and hard to follow
Would love to see the same approach for other infra (a nano-Kubernetes, nano Postgres.....
The real issue was never AI in Windows
It was AI with no clear user benefit. A Copilot button in Notepad doesn't solve a problem anyone has
Good to see them pulling back, but the test will be whether the features they keep actually earn their place in the workflow instead of just being there because someone had a KPI to hit
We did something similar with TypeScript strict mode
Turned it on per file with a ratchet count, and over a few months, the whole codebase was strict without ever blocking anyone