Thread:Project:Support desk/Why is this software so complicated?/reply

As for the file system access: Sure, config settings could also be done via a web interface. For MediaWiki that already partly is the case with the pages inside the MediaWiki namespace, where you can e.g. define CSS, which then is used for all users. However, usage of the file system amongst other things is an important barrier of additional security: The credentials of one of your admins might get lost and then attackers can manipulate e.g. these pages inside the MediaWiki namespace. However, what they cannot do is e.g. delete your complete database, because in order to gain access to the DB they would have to know the DB credentials, which only are available with direct file system access. And - another security-relevant aspect: You can have a hugh amount of wiki admins, but there should only be a very limited number of people with actual access on the file system level, which strengthens security even more.

As for the complexity of MediaWiki as a tool for the internet just have a look at other tools: MediaWiki is one of the bigger and more powerful wiki engines, no question. However, compared with other tools it is just like baby software: It does not offer full CMS options, workspaces, versioning, sophisticated user access levels, timed display of content, content rotation and so on, just to name a few.

However, I want to invite you: When you know how MediaWiki can be improved - made more simple, using better practises in the backend, then participate in its programming: Get Developer access and contribute your patches! Welcome aboard!