Hi,

Couple of comments:

>Harvey: Also, I'm guessing the other responses will be along the
> lines of "does the world really need another CMS" and "What does this do
> that Drupal, Wordpress, Silverstripe etc don't?"
>
> So give some thought to the answers to those questions.

Agree with Harvey thats its a very valuable question to ask. In
addition, however consider what sort of frameworks, web applications
and software have come onto the block in the last 5 years that
"re-invent the wheel", but then are really better solving some very
basic problems. CMSs, CRUD frameworks, Online task/project management,
time sheets, FTP programs. The latter are a good example. Is the one
you're using really the cat's whiskers? Why is not everyone using it.
Someone *has* to make something new now and then, if only for the idea
to be gobbled up by the major frameworks.

Christopher Tombleson:
> My main reason for creating a cms framework is because I couldn't find
> anything that isn't full of extra stuff I didn't need, what I trying
> to do is give people the flexibility that you can't get from some cms
> systems.

That is a really bad reason, because I believe its a myth that
something gets better if you take things out of it. That is only true
for things that consist of large amounts of crap. A well thought out
framework can have all the extra fluff, while being more scalable,
flexible and secure than a simple solution.

Keri:
> I think that the grammar was intentional, to go with the "Cribz Network" 
> branding.

Agree, its consistent branding. "Four" would have been worse ;)



Berend:
> Wouldn't it be more helpful to get to know an existing framework
> really well, and only then make another one?
>
> Else it will be the usual stuff from 25 years ago, full of security
> holes, missing things that everyone takes for granted, etc.
>
> Only when you know certain frameworks really well, you know enough to
> write something better.
Robin:
> I would say the reverse is true, that it's only after you have worked your
> way through building your own framework (or two) that you appreciate the
> structure and power that a framework can give you.
> I can only speak for myself but I wouldn't have known how to figure out why
> and how a framework behaves like it does as a novice developer.

Totally Agree with Robin here from own experience, the only knowledge
that understanding a good system completely gives you is that you can
solve most problems reasonably well with all major programming
frameworks, but you still wouldn't know why and which one to choose.


Kind Regards,

Jochen Daum

Chief Automation Officer
Automatem Ltd

Phone: 09 630 3425
Mobile: 021 567 853
Email: [email protected]
Skype: jochendaum
Website: www.automatem.co.nz
http://twitter.com/automatem
http://nz.linkedin.com/in/automatem
http://www.xing.com/go/invite/3425509.181107
http://www.aucklandbusinessnetworking.co.nz

-- 
NZ PHP Users Group: http://groups.google.com/group/nzphpug
To post, send email to [email protected]
To unsubscribe, send email to
[email protected]

Reply via email to