On Mon, 26 Nov 2001 19:45, Paul Hammant wrote: > > XML, XSL , LTPJB, XUL > > Is not Stefano's cryptic parting words of wisdom hinting (amongst other > things) that we should avoid new solutions when existing ones will work.
if we avoided solutions when existing ones work then we would still be using assembly. If it can be done faster, better, easier, cheaper by developing a new technique then do it is my opinion ;) > I.e. build a classic facade API for management of Phoenix, build > presentation layers with that using existing technologies. (Servlets, > JSP, struts ; Swing). Just because we can develop fancy & perfect > solution using markup languges does not necessarily mean that the > existing technologies are wrong. http://www.javaworld.com/jw-08-2001/jw-0824-myth.html It discusses why using "procedural knowledge" (PK) to define what should is essentially an assembly step (ie declarative knowledge or DK) is wrong. Making a programming langauge out of XML is wrong but representation of DK ... now thats a good idea ;) Phoenix is pretty much based on the same principles outlined in that article ;) -- Cheers, Pete --------------------------------------------------- Murphy's law - "Anything that can go wrong, will." (Actually, this is Finagle's law, which in itself shows that Finagle was right.) --------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
