Timeline for How to justify migration from Java 6 to Java 7?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 14, 2013 at 13:38 | comment | added | Martijn Verburg | Less boiler-plate and correct closing smeantics. They discovered that inside the OpenJDK they were doing it manually wrong about 2/3 of the time.... I suspect other high percentages of this in other corpuses of code. | |
| Jul 14, 2013 at 1:50 | comment | added | Tyler | I think the idea is that less boilerplate means it's easier to get right. | |
| Jul 14, 2013 at 1:34 | comment | added | jhewlett | Isn't try-with-resources the same as a try-finally but with less boilerplate? | |
| Jul 13, 2013 at 13:16 | comment | added | Andrew T Finnell | They are also reducing the amount of PermGen needed and using either Heap or native memory instead, I'm not sure on where it will be stored now. This means by Java 8 you won't need to set two max memory parameters. | |
| Jul 13, 2013 at 13:12 | history | answered | Martijn Verburg | CC BY-SA 3.0 |