On 19 Feb 2013, at 14:16, Leigh wrote: >> >> >> I can understand that If you haven't tried to write a tool like >> capistrano, rspec, chef, puppet, etc, etc in PHP you probably won't see >> much value in implementing such things. >> >> > Your RFC doesn't go to great lengths to explain the value either. Pretend > the reader has no experience with any of those tools you mention, pretend > the only language they know is PHP, please explain where the value for this > syntax is in PHP?
Very good feedback. Very much appreciated. I will see if I can expand on what I have that. Thank you. > I find the existing syntax easy to understand. I find the proposed syntax > disproportionally difficult and unintuitive in relation to any benefit it > is supposed to give. > > >> What is superfluous for is useful for other users. It would be useful >> building DSL. At my company we use loads of ruby tools for deploying, >> provisioning, etc. just because of the DSL they provide. The array short >> syntax was great news. Adding a short syntax for closures would make it >> possible to write such scripts in PHP – where the syntax would not stand on >> its way. >> >> > <insert PHP is not Ruby rhetoric> > > If Ruby is the right tool for the job, and PHP is not the right tool for > the job, the answer to which language to use seems obvious right? I find that more and more my developers have to learn ruby just to be able to work in our projects. We are one of the largest PHP shops in Europe and even the proprietary tools we are writing for DevOps stuff we are writing in Ruby. This small syntax arrangement would make it possible to write DSLs in PHP. The result is that I can have my PHP developers focusing on one language only and get the job done. The problem of the web is a bit more complex now, if you look on all you need to develop and deploy a large PHP application. > I disagree wholeheartedly that this proposed syntax would make code in any > way more readable, or maintainable. Please understand that there is a difference between code you write and other people maintain, and code you write for other people to use. The purpose of this feature is focused on the later, to allow the construction of DSLs, so users of your code can focus on the task at hand. -- Marcello Duarte -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
