Everyone was desperate to be first because capitalism.
But we are getting good models without the insane build out requirement. Which will be hilarious to leave the cunts holding the bag. Not that the planet is better for it in the end.
The engine is a single C file (c/glm.c, ~2,400 lines)
That file is almost 6k lines. The style also makes my eyes bleed. Why do people pretend stuffing 6k lines of code with almost no whitespace and meaningless variable names into a single file is a good thing? I’ve seen this a lot recently
Assuming the vars are all really short, it sounds like the same idea behind Webpack’s (et al) minification & mangling to achieve tiny performance gains everywhere it can. Which might mean there’s a dev version that isn’t squashed and ugly, but doesn’t make it to us…?
~1 token per second (storage bound gen4 nvme)… Some of us have places to be.
Don’t get me wrong. Its impressive that it can run at all, but honestly the usecase is exceedingly narrow. You’d have better results with a structured quantized gpu-only gemma or qwen workflow. Quality over quantity, rely on validation and a structured process: lots of cross-model review and iteration loops with spec and test driven dev. You could probably get a working alpha by the time colibri set up the environment.
Yeah I’m just beginning my local AI journey on a 5080, tried Qwen3.6 27b Q4 and was getting like 1tps because of the vram overflow. Ran it over night at it was still chewing on generating a prompt for a sub agent when I got up in the middle of the night until it simply ended in some kind of “fetch failure” lol. I think I gave it something too large to tackle, but either way 1tps is kinda garbage.
That’s what I generally use. I wanted to see if I could use the 27b to “review” what the 35b put out. The 35b has been working pretty well, but it’s not very thorough. I asked it to make a program and then 27b was like “this is a skeleton, there are folders but no contents.” Lol
These models generally are not capable enough to do one-shot vibe coding. They are pretty good as coding assistants if you tell them exactly what you want and let them focus on a specific aspect/part of code, not the whole thing at once.
Using an agent framework (I like Kilo on VSCode but there are many others) you can start with a planning session to let the model find out what you want to build. Then you let it write that gist into AGENTS.md and double check if that is what you want. AGENTS.md will be loaded into the context automatically so the model has a solid base of understanding for everything you do afterwards. Once you have that, building in vertical slices on top of that skeleton is much easier. Another neat trick is to ask the model a few questions about the current code base (if there is any…) at the beginning of a session, e.g. "How does feature x work in the current code? ". This primes the model for what you are about to do. All this is obviously a bit more work than just vibe coding away, but it lets you keep in control of the code and helps in being alert for errors these models (and all LLMs in general) will inevitably produce.
Thanks for the tips! What I had started doing the other day was having one session where it reviewed the code and created a document explaining what the program did in technical detail and then in another session I asked it to review that document before attempting anything with the program. Agent programs and harnesses are the next thing I need to start learning for sure.
Actually still no
https://github.com/JustVugg/colibri
Everyone was desperate to be first because capitalism. But we are getting good models without the insane build out requirement. Which will be hilarious to leave the cunts holding the bag. Not that the planet is better for it in the end.
That file is almost 6k lines. The style also makes my eyes bleed. Why do people pretend stuffing 6k lines of code with almost no whitespace and meaningless variable names into a single file is a good thing? I’ve seen this a lot recently
Assuming the vars are all really short, it sounds like the same idea behind Webpack’s (et al) minification & mangling to achieve tiny performance gains everywhere it can. Which might mean there’s a dev version that isn’t squashed and ugly, but doesn’t make it to us…?
Yeah this article is already outdated and poorly researched
~1 token per second (storage bound gen4 nvme)… Some of us have places to be.
Don’t get me wrong. Its impressive that it can run at all, but honestly the usecase is exceedingly narrow. You’d have better results with a structured quantized gpu-only gemma or qwen workflow. Quality over quantity, rely on validation and a structured process: lots of cross-model review and iteration loops with spec and test driven dev. You could probably get a working alpha by the time colibri set up the environment.
Yeah I’m just beginning my local AI journey on a 5080, tried Qwen3.6 27b Q4 and was getting like 1tps because of the vram overflow. Ran it over night at it was still chewing on generating a prompt for a sub agent when I got up in the middle of the night until it simply ended in some kind of “fetch failure” lol. I think I gave it something too large to tackle, but either way 1tps is kinda garbage.
You could use the 35B MoE model, tune it a little bit and get much better results. I have a 5060 ti and 70-80 tok/s are the norm
That’s what I generally use. I wanted to see if I could use the 27b to “review” what the 35b put out. The 35b has been working pretty well, but it’s not very thorough. I asked it to make a program and then 27b was like “this is a skeleton, there are folders but no contents.” Lol
These models generally are not capable enough to do one-shot vibe coding. They are pretty good as coding assistants if you tell them exactly what you want and let them focus on a specific aspect/part of code, not the whole thing at once.
Using an agent framework (I like Kilo on VSCode but there are many others) you can start with a planning session to let the model find out what you want to build. Then you let it write that gist into AGENTS.md and double check if that is what you want. AGENTS.md will be loaded into the context automatically so the model has a solid base of understanding for everything you do afterwards. Once you have that, building in vertical slices on top of that skeleton is much easier. Another neat trick is to ask the model a few questions about the current code base (if there is any…) at the beginning of a session, e.g. "How does feature x work in the current code? ". This primes the model for what you are about to do. All this is obviously a bit more work than just vibe coding away, but it lets you keep in control of the code and helps in being alert for errors these models (and all LLMs in general) will inevitably produce.
Thanks for the tips! What I had started doing the other day was having one session where it reviewed the code and created a document explaining what the program did in technical detail and then in another session I asked it to review that document before attempting anything with the program. Agent programs and harnesses are the next thing I need to start learning for sure.
Wow I’m starting to feel bad about that time I asked AI to make a joke about scatology & eschatology sounding similar.
Is that quantized? 4 bit Qwen 3.6 can get 22tps on a 1060.
It’s the q4 quantization, but it requires 20+GB vram and my 5080 only has 16
My framework 13 with shared RAM runs qwen quite well