Again and again... A lot of thoughts about ways but what are we talking about?
Proposal to rewrite? What is a target? new features, speed and new bugs... Suppose better to review a roadmap, maybe better to collect most popular & demanded tasks|features > At this point, I try to assess the decision using a few questions: > 1) What does this gain/provide us with? or what problem does this solve? > 2) What does this restrict or lose us? also, What does this cost? > 3) Are there any other ways of achieving this? and their related merits. > 4) Is this in the best interest of the community/project? and is this > what the community wants? First of all... 1) It brings a lot of new bugs. Solve some old problems but ... 2) loose compabillity, restrict in support older versions, brings a lost of old customers and hard way of invit new. Cost is not cheep but suppose very high! 3) Many ways... - but first to document current code some way... - then draw architecture and bottlenecks - review code (mostly done) - and only then make proposals! and costs :) 4) What purpose of Community? Bring bugreports & patches, answer a support questions, collect opinions of features My opinion is NOT rewrite but overview current state! 2008/8/1 Timothée Boucher <[EMAIL PROTECTED]>: > >> >> What do you mean by an "incremental transition"? Copying code over to >> the rewrite or refactoring the current code enough so that it's much >> easier to copy to a new "setup". > > What I meant by "incremental transition" would be either one of these. > Actually, I could see three ways: > 1. Start on a new framework, rewriting the current code "dumbly" to just > work the way it does now and prepare the whole thing for further > improvements (think about how Apple transitioned to Intel chips without > changing anything else). > 2. Rewrite the current code to make it easy to transition (kind of similar) > and for the crazy one: 3. Add the framework first, without changing anything > else and then incrementally modify the code to use the new framework. > > Well, I'm not sure of the method to do it but what I meant by "incremental > transition" is mostly: is there a way to end up with a new framework down > the road without having to start from scratch and instead be able to use it > all along, the way it works right now. > My main concern, again, is that if we get started with a rewrite, we won't > see any improvements for a long time. Additionally, I'm not convinced that a > rewrite would seduce many developers since it would probably be a lot of > boring tasks at first. > > Tim > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Projectpier-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/projectpier-development
