3 ms·
I thought that "weight" generally referred to less resource usage (RAM primarly, cpu second) and loc weren't part of those resources. Was I wrong?
by awelxtr 4y ago
I thought that "weight" generally referred to less resource usage (RAM primarly, cpu second) and loc weren't part of those resources.
Was I wrong?
- TickleSteve 4y agoweight == resources (both in terms of RAM, code space, maintenance overhead, etc).
- fsloth 4y agoThere is no "standard" terminology but I would say small line count is a definite factor here. Small LOC count implies low complexity of integration and low risk. Risk? Yes, the smaller the codebase, the easier it is to take your own fork and maintain it, even if the original project is no longer maintaining the codebase. Of these two low complexity is probably the main selling point. Small also implies generally "an elegant engineering solution to a problem that generally may involve layers of accidental complexity" and hence also incites a sense of beauty. Aesthetics can be important for people that are hand crafting their codebases.