Welcome to the second ##java podcast.
We have lots of interesting things to cover, so letâ€™s dive in.
- Java EE development has moved to the Eclipse Foundation, under the project name “Eclipse Enterprise for Java“, or “EE4J.” Java EE is still the branding for enterprise Java. This move makes Java EE more open; weâ€™ll have to see how well it works under the Eclipse Foundation. Weâ€™ll survive either way; itâ€™s a good move for everyone.
- RebelLabs’ Developer Productivity Report 2017 is here, almost 72% of the developers said their main programming language is Java 8 â€“ and about time, considering Java 7â€™s been dead for two years; IntelliJ IDEA is the most popular Java IDE at 54% with the respondents, and one of the survey questions says that 91% of the people who like it said itâ€™s because of superior functionality, as compared to 13% of Eclipse users and 73% of NetBeans users. Some other things that stood out: small teams are the norm, with teams of three to nine people making up half the teams, with medium-sized teams (10-19) coming in at 22%. Hmm, maybe a team of nine people isnâ€™t actually all that small. Itâ€™s a great report; you should check it out.
- Given Java 9â€™s release and new features, itâ€™s expected that a lot of migration articles are coming up. Sure enough, DZoneâ€™s in play with one that shows migrating a Spring app to Java 9. It has some module-based concerns and walks through fixing them; itâ€™s not exhaustive, but itâ€™s likely to be representative of early adoption efforts.
- Nicholas Frankel discusses some clean coding standards around lambdas. Itâ€™s easy to decide that a tool is available and thus must be used everywhere, he says â€“ actually, he says that developers act like children and we have to play with our new toys, which is probably a pretty appropriate description. He shows a fairly ugly way to use lambdas primitively, then shows how it can be made a lot more developer-friendly. Itâ€™s not exhaustive, but still worth looking at.
- According to InfoWorld, Java 9 is not going to receive long-term support. That doesnâ€™t mean itâ€™s not supported, but that the long-term support plans are different than what weâ€™ve seen in the past. Long-term support releases are going to be made every three years, so thatâ€™s the baseline for support plans; weâ€™ll have to see if (and how) this affects Java in the long run.
- Up next: another DZone link, this time on Javaâ€™s
Optional. The author, Eugen Paraschiv (from Baeldung) offers Optional as a tool for functional programming, and I suppose heâ€™s right, in a way. The article does a good job of walking through most, if not all, of what
Optionalcan do for your code, including with Java 9, and he does say that
Optionalis meant as a return type and not a property type, which is â€¦ better than he could have done. The articleâ€™s worth reading, and is done at much more depth than many similar articles.
- We also saw mention of OpenTableâ€™s embedded PostgreSQL container. This allows us to treat PostgreSQL as if it were an embedded database (well, sort of); considering that PostgreSQL is a lot stronger for production use than, say, H2 or Derby, this is a nice way to do database-oriented integration tests on a â€œreal database.â€ Thatâ€™s not to say that H2 or Derby arenâ€™t real databases, but theyâ€™re anecdotally used in the Java ecosystem more as embedded databases to help with integration testing than as production databases. Of course, now that Iâ€™ve made that assertion, I expect RebelLabs to ask something about this on their next survey and completely demolish my statement. Thanks ahead of time, guys.
- A bit more on Java 9. RankRed has “What’s new in Java 9,” covering a bird’s-eye view of the changes: the module system, new versioning, the Java Shell, a better mechanism for compiling for older versions of Java, JLink, compact strings, high definition graphics, new factory methods for collections â€“ catching up to Kotlin and Scala, better networking and serialization security, Nashorn changes, a new random generator, segmented code caches, dynamic linking of object models, and an enhanced garbage collector. Whew, thatâ€™s a lot â€“ and I left some out. It gets better, though: The Java 9 readme points out that the default JCE policy files now allow for unlimited cryptographic strengths, a feature that the RankRed list left off.
- Spring 5.0 has gone to general availability â€“ itâ€™s been released, in other words. Support for Java 9, Java EE 8, functional variants, Kotlin, a new reactive web frameworkâ€¦ all kinds of goodies for Spring fans.
- Kotlin 1.2 Beta is out. Kotlin is another JVM language; this oneâ€™s from IntelliJ, the people who bring you the IDEA editor family. There are a lot of little improvements here, including some things that can drive you crazy during normal development â€“ thereâ€™s also multiplatform support, which is important even if youâ€™re like me and only really deploy on the JVM.
- We mentioned ZeroTurnaround early in the podcast â€“ the RebelLabs report â€“ but itâ€™s worth noting that in addition to the developer survey, they also released JRebel 7.1, with Java 9 support, Spring 5 support, and a bunch of other things too.
Okay, thatâ€™s this weekâ€™s podcast â€“ thanks for listening.