3 ms·
Why laugh? We were already using proguard heavily. We eventually hit build perf issues and had to patch it too (https://github.com/facebook/proguard https://git
by LegNeato 11y ago
Why laugh? We were already using proguard heavily. We eventually hit build perf issues and had to patch it too (https://github.com/facebook/proguard https://github.com/facebook/proguard)
Do you think we wanted to do a crazy runtime patch and didn't explore every other short/medium-term option? Do you think we wanted to write our own build system (Buck)? Or our own JS view layer (React)? Our own PHP virtual machine (HHVM)? Our own database (Presto/RocksDB)? Our own IDE (Nuclide)?
You "laughing" tells me you have never worked on a large codebase with hundreds of engineers shipping very quickly, so you can't empathize with the sort of problems that come up.
Btw, every time Google Apps hit the limit they merely bumped the limit in AOSP and dropped support for old OS versions...
- nitwit005 11y agoYou had hundreds of engineers cramming stuff into a mobile app, till it didn't fit. Then you apparently had to make an entirely new version of it since people in much of the world couldn't even download the thing. That sounds laugh worthy to me. I also work at a large company that has had its own mobile development "issues", and I found those plenty humorous as well.
- jayd16 11y agoYou're right. I've never worked or will work in a place where a PHP virtual machine is the correct answer. I'm certain I can't empathize with that situation.