Talk:Principles

PHP
I considered making it "mainly in PHP" because that's the starting point but we have an increasing amount of JavaScript, 5 % in core and over 20 in extensions according to ohloh. (Not to mention all the JS served via gadgets and so on; if only they weren't such a mess, they'd be worth mentioning on the same level as extension for their important as regards customisation... after all, the WebAPI is good enough, but the internal PHP API for extensions is a disaster.) --Nemo 12:03, 29 July 2013 (UTC)


 * I don't think that the implementation language belongs in principles at all. We should continue to use the best tool for each job, whether that is PHP, JS (Parsoid, Mathoid, PDF renderer, VE, Rashomon), C (caches, Apache, MySQL), Lua (templates) or Java (search, Cassandra, Hadoop). By number of requests served pure C would win by far. -- Gabriel Wicke (GWicke) (talk) 03:58, 15 January 2014 (UTC)


 * Well, caches are not MediaWiki and MediaWiki was originally called "the PHP script", so there was some truth in it. :) --Nemo 07:05, 15 January 2014 (UTC)

Overriding principles
20.15 In http://aosabook.org/en/mailman.html there's an interesting bit about what their overriding concerns are: [...] 20.16 ooh that’s not a bad idea 20.16 ‘never lose data destructively’ (unless you really need to) 20.16 ‘audit logs for everything’ 20.16 ‘make it easy to use’

Open data
I'm wondering if we should state or imply somewhere that MediaWiki is so much open data ante litteram. Few or no other wiki engines have such wide import/export capabilities and web APIs. --Nemo 08:45, 9 January 2017 (UTC)