>
> CGI solves a particular class of problem in a perfectly good, language
> agnostic manner. Adding persistent services in place of those CGIs where
> none
> is needed actually increases deployment complexity. I thought we liked
> simple.
>
> I'm not using Mojo for a public website, I'm using it for less frequently
> accessed, private services in a server management layer. If CGI solves my
> problem, why should I care if someone ignorant of the problems that I must
> solve has decided to deprecate it?
That's rather ignorant of the actual situation. CGI is not going away,
just one of the two ways to deploy in CGI environments we currently support
would get moved into a separate distribution. The simple truth is that
nobody on the core team has actually used CGI in many years, know how is
dwindling and at some point we will be unable to react to problems that may
arise, this is an unacceptable situation.
I am well aware that there's a vocal minority that wants to keep
Mojo::Server::CGI in core, but at the same time nobody from this minority
has even attempted to solve our problems with better documentation. The
relevant wiki page for example has seen no major edits in a very long time.
https://github.com/kraih/mojo/wiki/Apache-deployment
--
sebastian
--
You received this message because you are subscribed to the Google Groups
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.
