News for hackers. Stuff that matters.
Re:Zend Framework 3 Released by coldtea on Thursday June 30, 2016 @08:51AM (#12008133)
>That's was the attraction. I guess it still is for very simple web apps that one person can build.

It's better to insist on simplicity at every level, whether you're building "simple one-person web apps" or "complex large-team" ones. In fact simplicity at every level would be even more beneficial in the latter case.

So I find this "dead easy deploy is only beneficial for small apps" dichotomy false.

Re:Zend Framework 3 Released by onion2k on Thursday June 30, 2016 @09:14AM (#12008251)
It's a great deal simpler to have a process that runs when code is merged in to a repo than to have a manual process of copying files to a server that relies on a human getting things right. "Dead easy to deploy" these days means "create a process that can run automatically, that checks things worked correctly, and rolls back changes if things go wrong". Doing those things manually is not simple.

If a deploy fails and a client is panicking because their app isn't available, the last thing you want is a team of stressed developers trying to work out which files they need to revert.

"Simple" doesn't mean "easy".

Re:Zend Framework 3 Released by coldtea on Thursday June 30, 2016 @07:57PM (#12012868)
>It's a great deal simpler to have a process that runs when code is merged in to a repo than to have a manual process of copying files to a server that relies on a human getting things right.

Who said it's has to be either one or the other?

The "manual process of copying files to a server" can be done simply by a person for a small scale project, and it also can be automated any way one likes -- e.g. to "automatic copy files to a server when code is merged in to a repo".

"Copy a file to a directory and the server just works and shows it" doesn't imply manual ftp uploading or manual editing of any kind -- it's just so flexible and easy that can it work that way too.

And if anything breaks, it's still simpler to find out what went wrong -- as opposed to some convoluted server deployment process with more moving parts.