[BW-dev-discussion] Is it important to adopt a new framework before proceeding?
jeanyves.hegron at laposte.net
Sat Aug 21 18:10:04 CEST 2010
Strategy is always a difficult subject it depends on who makes it.
Everything depend on how long it is needed to show something to the
world. The task to switch to a new framework is really hard, I think
here we should speak about "several monthes", where whith current EF it
is "very few month" for a visible result - and everything will need to
be done again with the new framework.
There is also the alternative of two teams (-we just don't yet have a
clear one-): one working quietly on a new frame work, well designed, and
the other on the pilot. This can be dangerous (for the delay) but also a
good solution to make a more clean BW(+ServasOnline) with fresh bases.
Something to inquire about the Framework is also the constraint it might
add on the DB Model. Many frameworks generally require strict rule for
naming database column (for example), may be this is also the
opportunity to make a big cleanup even if this is disruptive.
Are we going to open the Pandora box ?
Le samedi 21 août 2010 à 11:37 -0400, John Gunther a écrit :
> That one sentiment, Jean-Yves, says unequivocally to me, "Switch now!"
> If a framework change will ever be necessary, why would we not do it
> just before a major feature/code expansion, and before new coders get
> involved with the project? Some delay is inevitable, but the point of a
> framework investment is to speed coding and create a more maintainable
> product. Building new stuff on a framework that we know needs to be
> replaced strikes me as a very poor strategy.
> On 8/21/2010 10:55 AM, Jean-Yves Hégron wrote:
> > I think that it will be needed to switch to a more supported framework soon or later.
> bw-dev-discussion mailing list
> bw-dev-discussion at bewelcome.org
More information about the bw-dev-discussion