[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Application Design

• From: Don Park <donpark@d...>
• To: xml-dev@l...
• Date: Sun, 12 Aug 2001 16:30:42 -0700

> I think that the problem with XSLT is that  XSLT
> is often misleading, pretending to be more
> 'powerful' and 'portable'  than it actually is.

I don't think 'hype' is the problem at all.  The 20% part of XSLT is easy to
learn too, so learning curve is not the problem either.  The problem is that
there is no real need to learn XSLT.  Observe that:

1. People had to learn HTML and JavaScript because there were no
alternatives.
2. Learning HTML and JavaScript lead directly to XML and DOM.
3. Learning an API like DOM is far easier to learn a new declarative
language like XSLT.
4. Once you learned DOM, there is no real need to learn XSLT.

While DOM-based solutions are harder to implement and maintain, there are
plenty of people available with DOM expertise.   This is not true for XSLT.
Even if XSLT become universally available in browsers, JavaScript and DOM
combination will be the preferred method of implementation.

Best,

Don Park
Docuverse

• Follow-Ups:
  • Re: Application Design
    • From: Paul Tchistopolskii <pault12@p...>
  • RE: Application Design
    • From: Alaric Snell <alaric@a...>

• References:
  • Re: Application Design
    • From: Paul Tchistopolskii <pault12@p...>

• Prev by Date: Re: XML vs. EDI questions
• Next by Date: Re: Application Design
• Previous by thread: Re: Application Design
• Next by thread: Re: Application Design
• Index(es):
  • Date
  • Thread