One drawback to our large library of functions, is that it took a fairly long time to load with each web request. This library contains massive quantities of small functions that do everthing for logging errors to database independent access. But was there a way around this besides senselessly duplicating code... I dont think so.
How do you know that's the reason it's slow? Function calls are cheap, performance wise. If you profile your code and look at what is slowing it down, you might be surprised.
They reflect fundamental user interaction design principles. It tooks Micorsoft ten years to get it right. Apparently, a lot of the *nix people are too busy to code than to design.
Slashdot Mirror
One drawback to our large library of functions, is that it took a fairly long time to load with each web request. This library contains massive quantities of small functions that do everthing for logging errors to database independent access. But was there a way around this besides senselessly duplicating code... I dont think so.
How do you know that's the reason it's slow? Function calls are cheap, performance wise. If you profile your code and look at what is slowing it down, you might be surprised.
I just did this in Newark, California. It cost me 95 bucks, not counting the fictious business name.
They reflect fundamental user interaction design principles. It tooks Micorsoft ten years to get it right. Apparently, a lot of the *nix people are too busy to code than to design.