On Thursday, January 31, 2013 10:12:14 PM UTC-5, ringmaster wrote: > > Hey guys, > > I added core code to implement revisions in API in 0.10. The basic idea is > that revisions are always on within core, and plugins modify or disable > that functionality and provide the otherwise non-existent UI for it. > > There's a discussion going on in the issue tracker about the feature right > now. Your opinions (reply here?) are appreciated. > > https://github.com/habari/habari/issues/454 > > Thanks! > Owen >
I've been watching the comments on #454 and this thread with interest, mostly because my immediate thought was "Why do we need this? How will it help me?" Because at first blush, it won't. As others have said, it's yet another feature, yet more code, yet a bigger database. After thinking about it, I have no strong feelings one way or another. I've been using Habari several years, and haven't really missed the feature. The same can be said of many things that are already in Habari, though, such as ACL. It is a lot of code that adds to the database that I, as the single user of my sites, have no use for, that I know of. But I'm just one user, and not necessarily representative. For example, I like HiEngine. From what I can see, I'm the only one who likes, or uses, HiEngine. It could probably go away and no one but me would miss it. There are many other uses cases for Habari than the single user site, though. Many people would, or would like to, use it commercially or on multiuser sites. ACL, for example, is a necessity in such cases. It does nothing for a single user site From what I can see, revision control is just as necessary for a multiuser site as ACL, As far as database bloat goes, I can't see that as a major problem. Revisions, unless the post content is the part of the post being changed, will be relatively small. Logging adds much more to the size of the database than revisions will due to the sheer number of things we log, enough so that with SQLite I can't wait for the cronjob to truncate the log table and have to do so manually. In terms of code bloat, from what I've seen this changes adds somewhere around 100 lines of code, counting blank lines and comments. This isn't a horrible amount of code bloat If you look at Ohloh, over the past four years code size (counting only lines of actual code) has increased approximately 50% ( https://www.ohloh.net/p/habari ), from approximately 33K lines of code to 49K lines of code. That's 4K lines of code a year added that would include many features which not everyone is going to use, but which many people will see as a requirement to make the software minimally useful. Compare that to WordPress with 177K lines of code, Drupal with 865K lines of code, Typepad with 6600K lines of code, or Joomla with 1265K lines of code. Those comparisons tell me Habari is still lean and mean. Rick -- -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev --- You received this message because you are subscribed to the Google Groups "habari-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
