<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jep126 on Devops Monk</title><link>https://blog.devops-monk.com/tags/jep126/</link><description>Recent content in Jep126 on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.devops-monk.com/tags/jep126/index.xml" rel="self" type="application/rss+xml"/><item><title>Lambda Expressions (JEP 126): Syntax, Closures, and Target Typing</title><link>https://blog.devops-monk.com/tutorials/java8/lambdas/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://blog.devops-monk.com/tutorials/java8/lambdas/</guid><description>The Problem Lambdas Solve Every Java 7 developer has written the same five lines of boilerplate to sort a list or run a background task. Lambda expressions eliminate that ceremony entirely — and once you understand target typing, closures, and composition, you will find yourself reaching for them in every layer of a codebase: validation pipelines, event systems, retry logic, and beyond.
Before Java 8, passing behaviour as a value required an anonymous inner class:</description></item></channel></rss>