Skip to main content

Timeline for How to decide what library to use?

Current License: CC BY-SA 3.0

11 events
when toggle format what by license comment
May 6, 2015 at 19:10 history tweeted twitter.com/#!/StackProgrammer/status/596029387121754113
Apr 29, 2015 at 5:37 comment added bigstones ProGuard's shrink feature can remove from the libraries all the unused code, so size should still not matter.
Apr 29, 2015 at 1:38 history edited Kevin Krumwiede CC BY-SA 3.0
edited for clarity
Apr 29, 2015 at 0:58 answer added user22815 timeline score: 2
Apr 29, 2015 at 0:46 answer added Evorlor timeline score: 2
Apr 29, 2015 at 0:31 comment added Kevin Krumwiede @Telastyn It adds up. I'm thinking like the backpackers who cut the handles off their toothbrushes.
Apr 29, 2015 at 0:23 comment added Telastyn Why include the library sizes? At 1MB or smaller, that's insignificant, even for mobile devices.
Apr 29, 2015 at 0:09 comment added Kevin Krumwiede @rwong I think you should flesh out your comment as an answer for proper discussion.
Apr 28, 2015 at 23:59 review Close votes
Apr 29, 2015 at 13:12
Apr 28, 2015 at 23:44 comment added rwong Architecture don't stay forever. No matter what choice you make today, the software written on it will eventually wear out and be replaced. Quote 1: "If you don’t end up regretting your early technology decisions ...", Quote 2: "The best code you can write now is code you'll ...". Both quotes can be found here (slideshare.net). That will stay true until you finally have a multi-million-dollar company which can invest in the longer term.
Apr 28, 2015 at 23:35 history asked Kevin Krumwiede CC BY-SA 3.0