On Tuesday, October 16, 2012 11:02:18 AM Samuel Lopes Grigolato wrote:
> There is some cases that more code (and more cycles) is a good thing. For
> example, a multi-layer architecture (like presentation, business and data
> access) is more cpu-intensive than a single page doing everything in an
>
There is some cases that more code (and more cycles) is a good thing. For
example, a multi-layer architecture (like presentation, business and data
access) is more cpu-intensive than a single page doing everything in an
entangled procedural style, but is far more easy to evolve!
As Steven said, yo
2 matches
Mail list logo
