4 ms·
There are many reasons why apps are so big, but I think you are right about a major part of the problem. Development environments these days make it very easy t
by AndrewStephens 9y ago
There are many reasons why apps are so big, but I think you are right about a major part of the problem. Development environments these days make it very easy to add in third party libraries for very little effort.
At a previous job we had a monolithic java server that ended up at over 350Mb of compiled code simply because each development team had imported whatever libraries they thought they needed. In some cases, 2 or 3 versions of the same library were included.
- lsv1 9y agoThis is why code coverage is so important as part of the general development cycle.
- djKianoosh 9y agoWait, code coverage? How does that address the number of libraries used or duplicate versions of the same library?
- wooter 9y agoi don't see why any of this is a problem
- slaymaker1907 9y agoHow did they get multiple versions of the same library to work together? Java loads things via the class path so I would have thought that would cause some sort of error.
- swsieber 9y agoSome libraries change the namespace (package names) between major versions, specifically to allow transition from one to another in a gradual manor, or to start following namespace guidelines better.
- tedunangst 9y agojarjar?