[TYPO3-dev] RFC: Change roadmap for 4.5 and 5.0

Christopher bedlamhotel at gmail.com
Mon Apr 10 16:51:09 CEST 2006


A good idea in general, but...

On 4/10/06, Thomas Hempel <thomas at work.de> wrote:
> Hi Michael,
>
> >
> > 3. UI consistency means that you have to be *opinionated* about best
> > practices, and not encouraging 20 different ways of doing stuff. TYPO3
> > has until now been very unopinionated because of backwards-compat: We
> > still ship crappy invalid static templates *although* we know better, we
> > still support HTML4 doctypes although there is absolutely no reason not
> > to support XHTML only (except the said legacy arguments), which leads to
> > incredible amounts of code (and developer efforts, and support mails)
> > being wasted.
> Think the same. XHTML is the future! +1

This is misguided.

XHTML is the future, sure, but it is NOT the NOW. As I've said before,
HTML 4.01 is a CURRENT standard, and should be supported--all the more
so since virtually _nobody_ actually uses XHTML in a way that browsers
understand differently than 'tag soup' html anyway [1]. There is also
no real danger that developers are going to start xhtml as xhtml in
any widespread way in the near future since IE 7 will apparently not
understand it (and obviously, no earlier version of IE does either...)

5.0 is, IMO, a great opportunity to get ALL the html out of the
core--including doctypes, closing slashes, and anything else. I can't
see any reason why a CMS should prefer one current, working, valid and
extremely widely supported html standard over another.

-Christopher

[1] http://hixie.ch/advocacy/xhtml




More information about the TYPO3-dev mailing list