Exploding feature set...time to apply the brakes?

Hi all,

I'd like to ask if we really want all the proposed
features by 1.0? Could we not defer some till 2.0
maybe? Especially the larger or more esoteric features
like 'decorators'. My concern is that with too many
features (and keywords), it will take longer to get
stable or even debug effectively. More features ==
more features to debug.

There are other things to do (modules?), right now
it's still pretty much 'batteries not included' as far
as day-to-day usage is concerned. We need a networking
module, to be sure. And some xml-related stuff. The
earlier we have batteries the earlier prothon is
useful, the earlier we get more user feedback. It's
tough to build modules when the core is so fluid.

Aside:
I like the way twisted implements networking and
protocols. This is not the same as saying I like the
twisted implementation. Whether or not we need async
networking will depend on whether prothon has the same
problems as python when it comes to threading and so
on. The separation of transport and (application)
protocol is a good idea though.

________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html