<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Language-Features on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/language-features/</link>
		<description>Recent content in Language-Features on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 07 Oct 2024 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/language-features/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Java 9 to 17: The Language Features You Should Actually Be Using</title>
				<link>https://dplabs.tech/blog/java-9-to-17-features/</link>
				<pubDate>Mon, 07 Oct 2024 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/java-9-to-17-features/</guid>
				<description>&lt;p&gt;Java 8 was a turning point. Lambdas and streams changed the language substantially. Then came a long stretch where each release felt like maintenance work — modules in 9 were important but painful, and the subsequent releases improved the language incrementally without a clear headline.&lt;/p&gt;&#xA;&lt;p&gt;That changed with Java 14–17. The features that landed in this window — records, sealed classes, pattern matching for &lt;code&gt;instanceof&lt;/code&gt;, text blocks, switch expressions — are not conveniences. They change how you model domains and reason about code.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
