You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am wondering if there is any recommendation for an ideal package size, either in bytes, lines of code or number of classes. I can always break down packages into smaller ones, but how far should I take this? My concern is that too many packages increase the development overhead of managing dependencies and releases and maybe there is an overhead of loading too many assemblies at app start.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am wondering if there is any recommendation for an ideal package size, either in bytes, lines of code or number of classes. I can always break down packages into smaller ones, but how far should I take this? My concern is that too many packages increase the development overhead of managing dependencies and releases and maybe there is an overhead of loading too many assemblies at app start.
Beta Was this translation helpful? Give feedback.
All reactions