That closing appeal to deal with the abusiveness of the php.internals list fell a little flat given the opening statement of "shut up". I loved Rasmus' answer to this though.
> The vision has been the same for years. A general purpose scripting
> language with a focus on web development. You are simply saying you want
> the vision to be more specific than that because everyone has a
> different view of what web development means. But even if we narrow the
> vision, it will still be open to a lot interpretation. We try to strike
> a balance between the different and changing views of web development
> the same way we strike a balance between appealing to weekend warriors
> and top-100 trafficed sites. No vision statement is going to answer the
> question of whether annotations should be in docblocks or in the core
> language. That's simply not what vision statements do.
>
> -Rasmus
Maintaining clarity of purpose in a project can be difficult sometimes. Kudos to Rasmus for managing to do so in the midst of what looks like it's gearing up to be another php.internals shitstorm.
http://news.php.net/php.internals/64771
Maintaining clarity of purpose in a project can be difficult sometimes. Kudos to Rasmus for managing to do so in the midst of what looks like it's gearing up to be another php.internals shitstorm.