On Sat, Aug 6, 2016 at 1:43 PM, Arne Babenhauserheide <[email protected]> wrote: > > > On Sat, Aug 6, 2016 at 12:39 PM, Arne Babenhauserheide <[email protected]> > > Because why make the devops of a web server our problem (eg. dealing with > > security, sudden traffic influxes, etc), when we can make it someone > else's > > problem (ie. Github's)? We should focus on the software we're creating, > > not on devops for websites. > > Because using yet another wiki makes the conversion of the existing > content and the replacement of all the incoming links our problem. > > And that’s a problem at which we already failed once (in the transition > From the old wiki to the current wiki which is still not finished). >
Maybe the reason the new wiki failed was because it also uses the awful MediaWiki syntax, while the rest of the world has moved on to a Markdown-based syntax (like Github Wiki)? > Because I think the problems with the existing site are fundamental, and > it > > would be very inefficient to solve them incrementally. > > Do I understand it correctly that with that you mean you consider the > cost of fixing the current site incrementally to be higher than the cost > of redoing what is needed to make everything work with a rewrite? > Yes, the current site is hideous, I am confident that it would be far more work to fix it incrementally than to start again from scratch. Ian. _______________________________________________ Devl mailing list [email protected] https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
