on startup { tail.wag(high); status.set("Ready to pounce"); } on receive "hello" { if mood == "sleepy" { reply("zzz... ask me later."); } else { reply("Oh, hey there! Want a virtual treat?"); increment(treat_counter); } }
Disclaimer: No actual cats were harmed in the writing of this interpreter. Only egos.
git clone https://git.neko-lang.org/neko-script neko run my_script.nks Or, if you just want to play around:
No semicolon wars. No indentation anxiety. Just keywords, curly braces, and a standard library that prioritizes and timer events . Why Developers Are Switching (Or At Least Side-Eyeing) 1. Built for State Most scripts require you to manage state manually. Neko Script treats mood , energy , and focus as first-class citizens. You can set triggers like:
on startup { tail.wag(high); status.set("Ready to pounce"); } on receive "hello" { if mood == "sleepy" { reply("zzz... ask me later."); } else { reply("Oh, hey there! Want a virtual treat?"); increment(treat_counter); } }
Disclaimer: No actual cats were harmed in the writing of this interpreter. Only egos.
git clone https://git.neko-lang.org/neko-script neko run my_script.nks Or, if you just want to play around:
No semicolon wars. No indentation anxiety. Just keywords, curly braces, and a standard library that prioritizes and timer events . Why Developers Are Switching (Or At Least Side-Eyeing) 1. Built for State Most scripts require you to manage state manually. Neko Script treats mood , energy , and focus as first-class citizens. You can set triggers like: