yes, i've considered including both of those as well. i've also
considered writing a dsl on top of f# using a custom ( and greatly
simplified) rule language.
the desire to use powershell comes from a desire to target existing
skills that our technical staff has. we already use powershell in-
house for a variety of admin tasks, so, there wouldn't be a learning
curve for the people who will support the rule engine. the goal behind
the scripting support in the rules engine is to allow advanced users
to create more complex rules than the builtins. as it is, using c#,
vb.net, javscript, f#, or ironpython would be a significant learning
investment for them, wheras powersell is already in thier skillset.
its also much easier to learn for someone with no existing programming
skills...
Karl Prosser[MVP] wrote:
Quote:
> PowerShell isn't really the best choice for performance against 40
> million rows, even if the solution is great semantically. its good you
> are allowing other languages as scripting languages though it might be
> hard for them without an integrated editor, checker. Another option
> might be choosing preformant dynamic languages on the dotnet platform
> like F# or ironpython.
>
> -Karl