On 11 Dec 2001, Nathan E Probst wrote:
> Well, I've always thought that Easy of Use trumps Speed. You can buy
> faster hardware, but programmer productivity is relatively fixed!
That's my take on it all, too.
> Since this is an OSS project, Extensibility and Modularity are definate
> virtues! As I understand it, you can use the API to build a ruleset, so
> in a speed pinch, compiled code could still be used, right?
Ayup. Just the current semantic modules are interpreted (either
java introspection or XML xpath evaluation). But, you can certainly
implement the correct org.drools.spi.* interfaces, and do whatever
you like.
You can also mix'n'match run-time and compile-time stuff. You
can also mix'n'match semantic modules within a rule. (ie,
asserting that some XML document's attribute has the same value
as a member of a java class, or whatnot.)
> here's my preference:
> 1. Ease of use.
> 2. Run-time extensibility.
> 3. Speed.
I think that's the priority list I'm using to direct my activities.
-bob
_______________________________________________
drools-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/drools-interest
