Initially tonight’s episode was going to be called “The Patch Is All” (guess whose been enjoying the new season of Killjoys?) — with a discussion about pre code-review practises, however with Peter’s absence, the discussion centred mostly around the 2017 Java Language Summit which was taking place around the recording period.

Upcoming Events

• DevOpsDays Auckland - 3/4th October
• Pacific C++ - 26/27th October in Christchurch, NZ

JVM Topics

• Java 8u144 Released - release notes - download
• New Java Style Guideline for OpenJDK ( draft 6 ) - not everyone seems to like it.
  • Not embracing 2 space indents maketh me sad :(
  • Interesting to see how much conflicts with Googles standard, whose structural wrapping rules, whilst clearly delineating structural elements, can be a bit unsightly )
• Java Language Summit 2017
  • Agenda - lots on value types, surprisingly little on modularity
  • Videos already going live
  • Project Sulong - After watching the JLS video - colour me (Mark) highly impressed.
• Nobody puts Java in the container - Ken Sipe Video, JavaZone
• Introduction to Java multitenancy - Learn about a new feature for cloud systems in the IBM SDK Java Technology Edition, Version 7 Release 1
• Ceylon on Java 9 + Jigsaw
• Clojure Dependency Heaven(pdf) - introducing tools.deps.alpha
• edit cough at 18:42
• JEP 307: Parallel Full GC for G1
• How Compatibility Breeds Complexity - The module system gone awry
• Java Style Guidelines - Draft v6
• Developers Who Use Spaces Make More Money Than Those Who Use Tabs
• The best Java books as voted by Reddit r/java ( reddit thread here )

General

• Do people write insane code with multiple overlapping side effects with a straight face?
• Some History of Functional Programming Languages - David Turner (Lambda Days 2017) (youtube video)
  • Miranda language
• IntelliJ Rust Plugin now officially supported by Jetbrains
  • Autocomplete for macros
  • Minimum version is 2017.1
• Rust: The server trick - The semver trick refers to publishing a breaking change to a Rust library without requiring a coordinated upgrade across its downstream dependency graph. The trick is built around having one version of your library declare a dependency on a newer version of the same library ( reddit thread )

Contact Us

• Google Group Mailing List
• Google+ Page
• Facebook Group
• Twitter