My opinion is that the decision to F&$K backwards compatibility is moot at this point for Tap4. We are too far down the road to RC now. Any migration tool development that may need to begin would be starting many many months (a year?) behind the development of T4. T4 has benefitted greatly from months of user feedback, any migration tool built now would be greatly disadvantaged by not having the same benefit.
Make the decision and announce that fact for T 4.1 or 5.0 or whatever the next version will be called. Then it's up front and plain to see before coding even starts and the discussion/development of migration strategies, tools, whatever can proceed in parallel. I think that T both benefits from, and is hurt by it's free form development methodology. The benefits are obvious as T can change much faster than the "spec'ed" frameworks can. And that is no barrier to adoption for the coding junkies like me. But widespread adoption is hurt if compatibility is broken without a clearly defined way, in place and bulletproof, to migrate because bigger shops will be loathe to move to T if they are not sure that they can move with T in the future. Make plan, stan, and mitigate the risks to adoption. Geoff On 11/2/05, Richard Clark <[EMAIL PROTECTED]> wrote: > > On Nov 1, 2005, at 15:55, Howard Lewis Ship wrote: > > > Well, if we can get enough of the community to say "Howard! Build us > > something better, and F**K backwards compatibility!" then I can do > > that, and maybe just a little bit more :-) > > The reality is that if you want to keep serious commercial customers > (those showcase apps that drive adoption), you need a fairly > straightforward way to migrate to new platform releases. That could > be by building a compatibility layer, by keeping "backward > compatibility", or by a source-to-source translation mechanism. > > Right now, the update for the largest app I'm working on would be a > bit of a stretch, but is doable (and there are aspects of T4 that we > could use to clean up some inelegant code.) But if the answer was "we > can't upgrade, and there's no support anymore for what we are using", > there'd be trouble. > > ...R > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- The Spindle guy. http://spindle.sf.net Get help with Spindle: http://lists.sourceforge.net/mailman/listinfo/spindle-user Announcement Feed: http://www.jroller.com/rss/glongman?catname=/Announcements Feature Updates: http://spindle.sf.net/updates --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
