3 ms·
8. The app is built by a large consulting company and no-one gives a shit about the package size because the client isn’t paying extra for that (or “we will put
by selfhoster11 4y ago
8. The app is built by a large consulting company and no-one gives a shit about the package size because the client isn’t paying extra for that (or “we will put it on the backlog”, and then it’s never addressed)
- halJordan 4y agoYou didnt really give a new reason, you just said why the above reasons might occur.
- rubatuga 4y agoI guess the reason would be that humans are lazy.
- nikau 4y agoAnd its not a revenue generator if size is smaller - most customers wouldn't know how to determine the app size and wouldn't know what it means even if they saw its size.
- selfhoster11 4y agoNot necessarily. I was implying that part of the problem was that the applications are made cheaply and quickly, which necessitates the use of huge frameworks and libraries that make this possible. And then, because no one with decision making power cares about the size so much, these are just left in place instead of selectively rewriting or stripping the over-large parts to shrink the package. This is distinct from any “feature-enabling” type bloat IMO, because it’s more “development style enabler” type bloat instead.