App sizes are out of control

Re:App sizes are out of control by AndrewStephens on Tuesday August 01, 2017 @11:37AM (#14901835)

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.

[ Parent | on HN ]

Re:App sizes are out of control by slaymaker1907 on Tuesday August 01, 2017 @02:19PM (#14903701)

How 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.

[ Parent | on HN ]

Re:App sizes are out of control by swsieber on Tuesday August 01, 2017 @02:24PM (#14903758)

Some 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.

[ Parent | on HN ]

Re:App sizes are out of control by tedunangst on Tuesday August 01, 2017 @03:37PM (#14904530)

jarjar?

[ Parent | on HN ]

Re:App sizes are out of control by wooter on Tuesday August 01, 2017 @12:54PM (#14902793)

i don't see why any of this is a problem

[ Parent | on HN ]

Re:App sizes are out of control by lsv1 on Tuesday August 01, 2017 @12:36PM (#14902564)

This is why code coverage is so important as part of the general development cycle.

[ Parent | on HN ]

Re:App sizes are out of control by djKianoosh on Tuesday August 01, 2017 @01:05PM (#14902899)

Wait, code coverage? How does that address the number of libraries used or duplicate versions of the same library?

[ Parent | on HN ]