[FLOW3-general] why is default context Development and not Production?

[Nicolas Forgerit]

Hey guys,

>> If a user had misconfigured something, he'll get automatic debug
>> informations. Especially useful for beginners.
Hm i think debug differentiation is just a plus, the main point in
having different contexts is to alter the framework's caching
behaviour without changing its underlying infrastructure code. FLOW3
does a lot of awesome cowabunga stuff under the hood which would make
it terribly slow without being cached. Contexts come in handy, when
you're deploying your stuff: It changes it's caching just with a flip
of its context switch. (The server environment var you mentioned
before.)

> yes, that would make sence but I have never seen a framework that is in
> debug modus by default. Usually you ALWAYS have to enable debug modus.
What does make sense is thatm when installing a new barebone
framework, you firstly develop and then deploy to your production
server afterwards. It would just be an unnecessary step having to
switch to development first because you rather wouldn't deploy the
hello world example, would you?

> Take Magento for example. Magento just writes logs and files with the
> exceptions and the user gets notified in the frontend that something went
> wrong but the user will never see any debug trace in the frontend.
You won't confuse a web shop application based on the Zend Framework
with a sole PHP Framework like FLOW3, will you? Having said that, i
think Phoenix should be shipped in Production Context but i'm
currently too lazy to investigate this. :o)

> Of course i get your point and see also the advantage of it, you just have
> to configure "more" to put in into production mode than in debug mode.
See above, it's a step less instead of a step "more".

Ciao Nico