> But it also makes it harder to write software that has to be complex for legitimate reasons. Might have stolen this quote somewhere, but imho: Simple things

> But it also makes it harder to write software that has to be complex for legitimate reasons. Might have stolen this quote somewhere, but imho: Simple things should be easy, complex things should be possible. Related: software (binary) size should reflect the complexity of the problem domain. Some time ago, ran down the size of apps on my phone. Smallest one? ~2MB. What does that app do? Calculate some hash on a file. Select a file, it does its thing, shows the hash (and/or copy to clipboard). What the ..!?!#$ 2,000,000+ bytes for that? This is on Android, 'batteries included'. Selecting / opening a file should be a couple (or couple dozen) lines of source code, a function call to the OS, and presto. Same with reading file contents, and display output / clipboard copy. Which leaves... computing the hash. I'm not an expert, but what hash functions are so complex that you'd need a MB+ of code to calculate? (answer: none). Note that this app was the least worse offender. Conclusion: Android app model is broken. Or SDKs used to build Android apps are crap. Or other reasons / some combination thereoff. Regardless, ~2MB to compute a file hash is ridiculous. Full-blown Graphical User Interfaces (GUI) have been done in less. I'd be interested to know what that 2MB consists of, though. And where the hash function is at. And what (minute) % of overall binary size. And what all the rest of that binary does.