>ut at the time, rules-based
programming was still novel enough to be considered a viable approach
to AI.
Pick MLite from https://t3x.org and you'll get it pretty fast. Or with invariants under Lisp. Or its weird cousing, CLIPS, born from Common Lisp clauses.
On code quality, Neomacs (an Emacs clone in Rust, it has Elisp support) crashes a lot. And by a lot, I mean once you hit the menu with the mouse, it segfaults.
>he only catch is
you'll have no idea how it works. No one does.
Is not about the rules, but the relations. It's a network of clauses, and not something akin to if-then-else with flow controlling. There's no actual "flow".
It's a highly experimental thing someone decided to mess around with, without any prior design discussion with any Emacs core devs. It's like a forty-minute-old baby and you're asking it to parallel park without crashing. What's your point here, I don't get it?
GNU/Emacs is incredibly stable. It's one of the most reliable pieces I've ever had; I sometimes run it for months without ever restarting. Which I can't say about pretty much any app on my system. Including the system itself.
That's unfair; Emacs had 50 years of shaping into what it is. What the Neomacs team achieved in a very short amount of time is absolutely impressive. I'm not stoked about the fragmentation or about the use of AI, but I think we all should curb our skepticism too; some opinions are aging faster than milk.
I didn't got a crash on Linux/Wayland. And I didn't tested on MacOS or Windows.
What's your device envionment?
Could you please submit a GitHub issue to neomacs? (better with a minimal reproducible script and log `RUST_LOG=INFO ./neomacs` can output the debug log)
reply