Welcome to WebmasterWorld Guest from 184.108.40.206
Forum Moderators: phranque
We must all remember - it's not the size of the code, but how you use it.
Pleading innocence to the alpha male charge, I didn't bother to look for my largest bit of programming; instead I pulled one from the trio I'm currently working on most. (and I'm still not going to bother looking - even as the opportunity and challenge present themselves)
Back in a previous life, when memory and disk space were precious, we used to work very hard on code reduction and memory utilization. The ace programmers were the ones who could get the most performance with the smallest code. Seems like these days we just happily use up memory, disk space, and processor resouces with wanton abandon.
Back in a previous life, when memory and disk space were precious, we used to work very hard on code reduction and memory utilization.
I still try to keep code tight and efficient. CPU power and memory have grown but so too has OS bulk. My next upgrade to my beast of a program will be to implement data storage in an xml file rather than use the registry. This will increase the size of the program but make it much faster to start up. It will also provide several other benefits but I can't easily explain these.
Total 14,121 lines between the main program, 3792 lines, and three included modules, and does not include site output templates. It's important to mention that (like most of your web-based programs) over 9,000 of that is strictly internally-generated HTML, so the actual programming functions only involve 5,000 lines, give or take.