On Sep 16, 2008, at 1:53 PM, msi wrote:
> > On 16 Sep., 18:42, Arthus Erea <[EMAIL PROTECTED]> wrote: >> You just admitted it is a personal thing: personal to you. We >> shouldn't be rolling in features that only a tiny percentage of users >> will use. That is the point of plugins, no matter how much you might >> hate them. > > Yes, you are right. But this is also in WordPress. Told you so many > times, do not try to immitate WordPress. But this feature is in the > editor. I can write or edit and keep a post private. That is all, I > wanted to say. :-) > >> Well I guess that's the root of the problem: you seem to want to >> avoid >> plugins at all costs. This mentality is fundamentally at odds with >> the >> Habari vision of having a lightweight core while adding additional >> features through plugins. > > Nope. I wrote myself a blogroll plugin. It can import the WP blogroll > with all links and the related link categories. I do not have just the > "Blogroll" subject in the sidebar. I can have more than this. > >> If plugins truly are such a huge overheard for you, then there must >> be >> something wrong with the system. We need to fix that problem, not >> avoid it by just rolling in minority features into the core. > > Tell you what, I never mentioned before. I came to the limits of my > server. I could not use WordPress with the language file, K2 with its > language file and some of my favourite plugins. I had to run the > backend with the English language. Wait. So WordPress hogged memory (we can certainly understand that) so you now are afraid of Habari doing the same thing? While that is completely understandable, I'd challenge you to actually complain if *Habari* starts causing memory problems. > > I guess, you will say: ask your provider. Well, I did and the > increased the memory limit. It is working now. But should this be the > solution? Having memory problems, ask the provider! Do not look into > the code to avoid it? A load of plugins, a load of languages files > (the worst case, every plugin has its own language file), etc. > > Do not get me wrong! I am not saying, Habari is causing this problem > because I just run it on my local machine. I do not use it for a real > blog. But, yes, you can say, I'm afraid (just a little) that I could > run into the same problem again because I have to load a plugin for > this, a plugin for that. *sigh* > > Before you say, change the provider: No! I do not have to pay for my > site because I worked for the company. And I like those guys. And > again, increasing the memory or changing the provider to get more > memory should never be the solution to avoid (possible) memory > problems. I completely agree. A small blog with the engine behind it should not require its own dedicated box... if there is excessive memory usage, that is a flaw in the application, not necessarily the design pattern. I guess what my point comes down to is: don't blame Habari for the faults of WordPress. :) If you're concerned about memory usage, you can run tests locally with various plugin configurations. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
