On 11/10/2010 06:54 PM, [email protected] wrote:
I guess I don't really understand the goals of this group.
I guess TG is supposed to target people who want to constantly
change their code to chase the latest-and-greatest bleeding-edge opensource.

If the framework makes me code to components like dB or templates directly,
then I have 2 choices:
    1) maintain the code myself when TG tires of the underlying technology
       and moves on to something else
    2) rewrite my code so it stays current with the framework

That's not really fair.


perhaps, but for people like me that invested in TG1, we were led
to believe that SO and Kid would be supported.

For people starting from scratch, SA and genshi are good choices,
so I hope they really do get supported and not dropped for the
next greatest thing.  (So why is Elixir not really supported in TG2.1 again?)

For stuff like identity, access control, session management, and deployment,
there is no good excuse for the all the churn.

We will support the DB layer and template layer indefinitely, we're
not planning on abandoning SA or Genshi.  We just aren't planning on
"wrapping" them so that they hidden from you, and you are insulated
from changes *inside* genshi or SQLAlchemy.

If that's not enough, then you really do need a monolithic framework,
and that's not going to be TG.


I want to use TG.
If a reasonably robust and well documented branch was available, I would use it.
IMO, the 5 concurrent branch approach was a big mistake and caused lots of 
confusion.
The premise that users want to mix-and-match so many different ways is rather 
suspect.
Perhaps if SA and genshi were the only external dependencies, and the rest was 
solid TG
framework where the user API backward compatibility is a top priority, this 
would be
a winning approach.


Andy

--
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en.

Reply via email to