groovy-eclipse VS Drools

I’ve got a project that has both eclipse and IntelliJ contributors. Groovy-eclipse’s parrot parser support is still in basically alpha status.

I've met a few young programmers who heard somewhere that object-oriented programming was bad and they want to get the enlightenment of functional programming that they've heard about. Frequently they travel from job to job like itinerant martial artists always looking for somewhere where they practice the true technique but they always seem disappointed as it is just as easy if not easier to screw up handling errors with monads than it is with exceptions and they find analogies like "a monad is like a burrito" just get them more confused.

As for something profound I'd point you to

https://github.com/cerner/clara-rules

which many people will struggle with because like many other production rules engines in LISP (and many other examples of simple compilers), there is hardly any code! Contrast that to the orders of magnitude larger rules engine Drools

https://github.com/kiegroup/drools

which is so crazy-complicated primarily because the Drools language is Java-based so you need all sorts of things that Clara or CLIPS don't need.

IMHO you're better off using something like https://www.drools.org/ for this. Non-devs writing code is a pipe-dream. It never works out.

https://www.drools.org/ an open source solution that allows you to use the UI to define rules. You can even import excel files.

Hi all, I am doing a project in rust right now (a web server with axum, postgres, redis), and am in need of a good rule engine like Drools in java (https://www.drools.org/). From what I have searched, I couldn't find any that are well maintained or provide similar levels of functionality.

Also ... https://www.drools.org/

Drools - Drools - Business Rules Management System (Java™, Open Source)

Drools (a Business Rule Engine),

Hopefully you already know that Drools is a business rules management system. You write rules in either "drl" syntax, in spreadsheets, or in glorified flowcharts, and then let your application throw data at it.