Since I’m not an experimented user of those solutions, maybe other people might share their opinion on the points listed there. Any feedback is welcomed. Thanks.
On the “Programming capabilities”, XWiki actually support any scripting engine implementing Java Scripting API and Python 2.7 (in standard WAR) and Ruby (extension) both works very well (as well as Groovy actually except a bit slower in case of Python).
There is actually structure data support in Mediawiki trough Wikibase - MediaWiki. It’s used on https://fr.wikipedia.org/wiki/XWiki for example (not a very good advertisement I must say since it’s making a huge pain to edit information in that page).
By “App Store” you just mean “install extensions directly from the software” ? When reading that line in the MediaWiki comparison it feel like “XWiki has lots of extension and MediaWiki don’t” while MediaWiki probably have more.
Programming
– OLD: “VERY ADVANCED using Velocity, Groovy and Java using thousands of available APIs”
– NEW: “VERY ADVANCED, supporting any scripting engine implementing Java Scripting API, Velocity, Groovy, Python, plus Ruby, PHP with extension”
— Let me know if it’s fine, or please edit it in the wiki page
Structure Data
– I’ve modified from “No” to “Partial, with extension”
App Store
– By App Store I mean a Repository application, paying or not. The “app store” is defined as a “digital distribution platform… that allows users to browse and download apps”
– I’ve marked that MediaWiki has extensions in the “Extensible” row, although my focus was more on applications. Let me know if I should have a special entry for applications, since I’ve tried to compress apps+extensibility into a single line.
Thank you so much for your comments. Keep them coming
Do you have other ideas of XWiki features that set it apart from other solutions?
Since Velocity is not used trough Java Scripting API (it’s actually so customized that it’s closed to being the “XWiki Scripting Language”) I would say something like:
“supporting Velocity plus any scripting engine implementing Java Scripting API (Groovy and Python are embedded and shortcuts are also provided as extension for Ruby and PHP)”
The “shortcut” thing is too complex to understand (not even sure I understand it) and I don’t think it’s necessary. This is just a summary table. We just need highlights.
Also Java Scripting API is too technical too. It’s better to list the main languages we support and say something like “and more” and link to the scripting page on xwiki.org that explains that we support the Java Scripting API and give more details.
I think it’s important that we mention scripting and you removed it with your proposal. Also PHP should not be mentioned since it’s useless (you can’t do any real work work with it - I really wouldn’t advertise it).
You could say:
“VERY ADVANCED, Java but also full API access through scripting in various languages: Velocity, Groovy, Python, Ruby, and [[more>>…]]”
ok that’s confusing. Just drop “plus” and “with extension” and it’ll be more readable (it’s not needed at this level IMO). And ideally the Python one should be with extension too (just that we need it ATM for the code macro). If you really want to keep “plus…with extension”, I’d suggest using “+” which will make it more visible.
