As a maintainer of Lua modules and abuse filters, I want to be able to use the same language for both tasks, so that the learning curve is not so steep.
Rather than using AbuseFilters own language, with its own bugs and limitations, could/should we switch it to Lua? Just dropping support of the current language would be bad, but preferring to use something more standard?
See Also:
It is a very good idea. Now the conditions of all filters are tested for all edits, by using Lua we can group the conditions and don't test, for example, filters for anonymous in registered edits.
Not sure whether it's good to add bug 50454 to "see also" and/or reopen it, but this Lua (for AbuseFilter) needs to include a regex library (see ngx.re in the nginx version of Lua), or it will be impossible to migrate current filters.
I think it's worth considering to let the next generation of AbuseFilter work on the HTML DOM rather than wikitext.
Advantages:
Issues:
@Ricordisamoa added a project: Scribunto.
I'm not sure what this has to do with Scribunto, besides that AbuseFilter would likely want to reuse Scribunto's classes for interfacing with Lua and that might want some refactoring.
Scribunto isn't going to get a regex library, for the reasons described in T52454#555457.
But that doesn't mean AbuseFilter can't create its own instance of Scribunto_LuaEngine or Scribunto_LuaInterpreter and inject extra libraries, including one that provides regular expression matching, if it's deemed safe for that context.
@Anomie写道：
I'm not sure what this has to do with Scribunto, besides that AbuseFilter would likely want to reuse Scribunto's classes for interfacing with Lua and that might want some refactoring.
Not only this, I would also suggest to add Wikidata here, since Lua things are more and more intimacy with them.
My assessment:
Personally I never had the necessity to do something in AbuseFilter for which Lua would be needed, nor I see possible use cases. Also, bugs from AF parser should be resolved inside AF parser, so that's not a good reason for the switch.
If someone can find a use case for Lua syntax, a simple way to adapt Lua to our needs without performance loss, and it turns out that Lua is easier to learn for non-tech people, then feel free to reopen the task.