I don't think we need yet another list. That said, I think that some features (such as weak typing) would benefit greatly from having a small body of people get together and flesh out a proposal together before presenting it for sacrifice on the altar of public discussion. Part of the value in this is keeping the group limited to just collaborators on that specific feature, so a general features mailing list wouldn't really add anything.
Not sure how you want to coordinate this group. In my company we have a distributed team and we typically coordinate this sort of design process using Google Docs + Donedesk(our own product, but free) + Skype. This works well and strikes a nice balance between persistent and realtime collaboration. I'm open to other ideas, but if I had to choose how to coordinate a group to design a single feature, that's what I would use. John Crenshaw Priacta, Inc. -----Original Message----- From: Kris Craig [mailto:kris.cr...@gmail.com] Sent: Monday, February 27, 2012 6:36 PM To: Ángel González Cc: Anthony Ferrara; Ferenc Kovacs; Michael Morris; internals@lists.php.net Subject: Re: [PHP-DEV] Scalar type hinting I agree. What does everyone think about the idea of creating a new list specifically discussion of new feature ideas? The idea could be announced on the Internals list with a link to the discussion on the other list. That way, the noise ratio would be reduced and only those who are interested in brainstorming new ideas would have to listen to it. Thoughts? --Kris 2012/2/27 Ángel González <keis...@gmail.com> > On 27/02/12 22:52, Anthony Ferrara wrote: > > Ferenc, > > > > Thanks for the comments! > Thanks from me, too. > > And thanks to you, Anthony if you get to summarise that. > > > >> There were ideas, but they didn't have enough traction. > >> IMO we can't have a proper solution without changing the existing > behavior > >> for complex types, if you implement strict typing for scalars that > turns the > >> language strict typed, if you add dynamic/weak typing for the > >> scalars, > you > >> will have an inconsistent implementation. > > What behavior would need to be changed for complex types? Adding > > the ability to hint/cast between trees? I'm kind of confused by > > this bit... > I suspect one of the scalars should be complex (= objects?) > > > > > I think that's my biggest problem with the dynamics of this list. > > Ideas aren't really nurtured as well as they could be. If the idea > > is solid, and has an implementation, then it's great. But there are > > plenty of seedling ideas that get lost or down trodden-ed simply > > because it's not bulletproof... > Yes, the noise ratio of this list is quite high. Probably related to > its high volume. That makes people faster in discarding ideas as "been > there" > and generates friction. And low-quality discussions like that don't > attract smart people insights, precisely. > It's a vicious circle. > > > -- > PHP Internals - PHP Runtime Development Mailing List To unsubscribe, > visit: http://www.php.net/unsub.php > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
