On Tue, Oct 1, 2013 at 2:53 PM, Tyler Romeo <tylerro...@gmail.com> wrote:
> On Tue, Oct 1, 2013 at 2:46 PM, Ryan Lane <rlan...@gmail.com> wrote: > > > This is only true if you want almost no functionality of out MediaWiki > and > > you want it to be very slow. MediaWiki is incredibly difficult to > properly > > run and requires at least some minor sysadmin experience to do so. > There's > > a reason that almost every MediaWiki install in existence is completely > out > > of date. > > > > Do you have some specific examples? > > Extension management, upgrades, proper backend caching, proper localization cache, proper job running, running any maintenance script, using a *lot* of different extensions, etc. etc.. > Also, if that's the case then removing file caching would be a step > backwards. > > Pretending that we support the lowest common denominator while not actually doing it is the worst of all worlds. We should either support shared hosts excellently, which is very difficult, or we should just stop acting like we support them. I'm not saying we should make the software unusable for shared hosts, but we also shouldn't worry about supporting them for new features or maintaining often broken features (like file cache) just because they are useful on shared hosting. It makes the software needlessly complex for a dying concept. - Ryan _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
