[TYPO3-dev] Moving the topic of the discussion a little bit --Based of thread "Change roadmap..."
Dimitri Tarassenko
mitka at mitka.us
Thu Apr 13 00:30:26 CEST 2006
Joey,
On 4/12/06, JoH <info at cybercraft.de> wrote:
> Kick the great inventions Kasper has made during the last 8 years in favour
> of something that will make it just a framework for some techniques you
> could even use without TYPO3.
Ahem... Can we get a bit more real about the amount and degree of
actual innovation TYPO3 contains? Not to rain on anyone's parade or
anything, but the last "great invention" I know is the Internet, and
we all know who did it ;)))
> > Smarty is _clearly_ superior to TYPO3 marker-based templating as it
> > provides better separation of business logics and presentation. Martin
> > gave you one very good example with looping but it doesn't end there.
> Maybe you didn't understand the meaning of "separation" but AFAIK smarty
> does just the contrary: It mixes up logics and presentation completely,
> forcing the template designer to think like a programmer.
Iterating items in a set just to display them is the task of
presentation layer. And right now in Smarty you can do it in the
template, while in TS+Markers you have to do it in your object code.
> > That's exactly what we are rooting for. Smarty suites my needs a lot
> > better than TypoScript, and not because it's "standard", but because
> > it's better. ADOdb is better than t3div_db and DBAL. Et cetera.
> There is always something missing in your sentences: The words "for me".
Yep. This time I used "suites my needs". Guilty as charged ;)
> So why not find a way of keeping TypoScript and implementing the possibility
> to use other templating techniques as well?
For the same reasons that MS killed VB6 in favor of VB.NET - to free
themselves of the burden of backwards compatibility that was getting
to heavy.
> Well - as far as I understood the details you described of your vision of
> TYPO3 5.0 this sounds like a fork to me.
It was meant to sound like a proposed turn in direction. And if there
continues to be some movement in the current direction after the turn,
then I guess it is a fork.
> BTW: If all those things that make out current TYPO3 are so badly written,
> sucking and crappy solutions: Why are you using it then?
For the same reasons I still drive my rusty 1993 Ford Taurus to work -
it's there, it still can handle 15 miles a day and it's paid for. Am I
proclaiming by driving it that '93 Taurus is the best thing since
sliced bread? Hell no, I take my other car when I hit the
interstate;))
--
Dimitri Tarassenko
More information about the TYPO3-dev
mailing list