> > > 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?
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 disagree wholeheartedly that this proposed syntax would make code in any way more readable, or maintainable.
