WebMacro compiles the template into an efficient form, and caches it,
so that execution is quick and efficient. It also caches the results
of reflection/introspection so that even the class analysis doesn't
slow it down.
I consider speed to be one of WebMacro's advantages.
http://webmacro.org
The advantages of hardcoding are then what?
Justin
Quoting Andras Balogh ([EMAIL PROTECTED]):
> Hi all,
>
> Since lately i have read a lot of discution about templates i want to ask
> a question:
> What is the advantages and disadvantages about using hardcoding or Templates?
>
> Here is my opinion:
>
> Hardcoding
> advantages:
> -it is faster than Templates
> disadvantages:
> - not portable
> -needs recompliling if something is changed
>
> Templates:
> advantages:
> -portable (if well written)
> - easy to modify
> disadvanteges:
> -slow ( because it was done to be serve a general purpose
> more genaral=slower)
>
>
> I think the best solution it somewhere between.
> So my opinion is if i need to do a job i won't rush to use template frameworks
> (made to be general) because if i know that pages are to be changed once in a month
> than i would consider that to be fast is more important than to be portable.
>
> p.s. This question is a genreal one, it is not for criticising someones work.
>
>
> I don't know if such questions ( i mean not to a specific problem ) is welcomed.
>
> I hope it is and I hope I will get some reply too.
>
> Best wishes,
> Andras.
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
