Insane! Each deterministic result must be removed from the model weights.

#2
by emircanerkul - opened

Tool calls but if it run on weights it would be insanely fast, isn't it? Today you put calculator as a tool later boiler plate generator then linters etc.

Due to it lives where weight lives it must be fast and no need to make tons of roundtrips. Also it is big win for local models.

Imagine your code lives and grows within the weights. Editing files externally via tool calls also slow. It could iterate code there, run what it build there. 🤯

Do you have any example? Like it creates MicroPython script, runs it, iterates it all inside weights. But how you track if it works like that? Also any idea regarding mojo language or GPU intensive tasks, can qwenputer able to access gpu? (I think it should create threads which have to run on gpu isn't it?) If thats the case gpu related developments would be perfect fit for that.

Sign up or log in to comment