Development

QUOTE
__

I think you're complaining way too much. Quite possibly Tiki is not 100% efficient. Or even 50% efficient. Why don't you check out the cvs version and see if you can help speed it up. Instead you produce a long rant. Vision changes, new ideas come up and software becomes better (hopefully).

_

Well, if it was just a code related issues, I would be more than happy to help out, and patch up things on the CVS. However, it seems to me that Tiki will never be efficient until they change the design of it. I'm not just talking about speed here, there are conceptual issues I disagree with here in the way it handles content. to me, if Tiki was be a great project as a piece of code as well as and end product for others to use, I think it's ***design*** needs changing.

I think this is the trouble with so much open source software, escpecially in thinks like this, PostNuke, and PHP Nuke. Each project has a really good vision for a good project, and they have coders capable of making this vision a reallity. However the bit in the middle, the design just seems to be lacking to me. I have my own idea of how a CMS/Portal should work, and I am working on it as a project myself. I'm still planning and designing it, and I don't want to dive into coding until I'm truely happy with the design and feel that everything is as efficient as possible.

Since upgrading this site to 1.8, there do seem to be a few less SQL queries, but it's still a lot of queries.

I'm not putting down someones work. I'm questioning the fact why there is so many queries and why the system is so resource intensive. OK, fair enough, I haven't been very polite about it, but it is the harsh reallity. I'm just saying if there was a bit more thought about the design of the product, Tiki would be a much better system, and won't be as limited as it is (for instance people can tell these days if Tiki or *nuke is used to make a page).

I know software is never going to be 100% effiecent, however Tiki is far too resource intensive.