Hi Bigin
Thanks for your reply
I already cleared that up with the "user domain" I defined in the beginning of my post.
Yes you can test a cms system in 2 obvious ways:
1) the way it was made to work - it's code base
2) the way it was made to use - it's api and backend
And then compare that to other cms systems and see:
a) which one is terribly coded
b) which one has a nightmare backend
c) which one performs faster
A cms system is not made for the coder ... a cms system is made for the end user ...
at least the ones we discuss here
I know it is often difficult for an experienced coder, but try to see it from an end user view ...
End users will never work with ... and neither are interested in the programming language it is written in,
nor in its system core ...
F.
Thanks for your reply
Quote:that's simple: because you didn't have enough knowledge on how to work with it properly.
I already cleared that up with the "user domain" I defined in the beginning of my post.
Quote:You can't just download a system, fiddle with it for two days, mess around with it, and then claim it's slow or bad.
Yes you can test a cms system in 2 obvious ways:
1) the way it was made to work - it's code base
2) the way it was made to use - it's api and backend
And then compare that to other cms systems and see:
a) which one is terribly coded
b) which one has a nightmare backend
c) which one performs faster
Quote:Again, to test something well, you need real background knowledge, first in the programming language it is written in, and second in its system core.
A cms system is not made for the coder ... a cms system is made for the end user ...
at least the ones we discuss here
I know it is often difficult for an experienced coder, but try to see it from an end user view ...
End users will never work with ... and neither are interested in the programming language it is written in,
nor in its system core ...
F.