For it's size it's pretty good.
I run it and the older Qwen 3.6 35B A3B, which is significantly faster, but also a bit dumber, on both my PC and my MacBook.
Wouldn't trust it for long form coding, but for shorter stuff it's really good.
That's fair enough, but for me, it was just a really procedural way to think through the process. All the work we did, summarised in one document felt kind of good.
100 Mbit/s (IEEE 802.3u) is commonly called "Fast Ethernet" (Compared to the prev 10 Mbit/s which is just "Ethernet", or the later 1000 Mbit/s "Gigabit Ethernet" (IEEE 802.3ab)
I would go with lua for the players.
You can easily sandbox it, by not compiling in the dangerous functions.
Using debug.sethook you can limit execution by count (https://www.lua.org/pil/23.2.html).
And finally you can bring your own alloc for lua.
There are also decades of articles on how lua works with C and C++, and you can find examples for Rust and others too.
Wouldn't trust it for long form coding, but for shorter stuff it's really good.
reply