| To give a little more background, let me breifly say that the argument started when I called an addon to a piece of software 'bloated' based on my standards as a programmer. The idea that I'm coming from is the way you can write an object in an OOP language which encompases a small part and take the all the little parts that you need and put them together, rather than clump it all together in one big object where everything follows you around as you subclass, etc. Example:
I can write 'Lettuce', 'Tomato', 'Hamburger', 'Ranch Dressing', and 'Bread' as objects.I can then make a salad from the lettuce, tomato, and dressing. Or if I felt up to it, make a sandwich from the lettuce, tomato, and bread. My comment to him was that I would rather just have the parts (Lettuce, etc.) than a sandwich, and even moreso than a sandwish with ranch on the side that I don't want (If you just include everything 'just in case', which is the case here). So now that you have the background, I refer you back to my original post and pose you this new question: "Am I thinking straight, or am I just really hungry?" |
