<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Writing on Maciej Zawieja</title><link>http://maciejzawieja.dev/blog/</link><description>Recent content in Writing on Maciej Zawieja</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 15 Nov 2024 09:00:00 +0100</lastBuildDate><atom:link href="http://maciejzawieja.dev/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Flutter in 2024/2025: The Evolution of Cross-Platform Development</title><link>http://maciejzawieja.dev/blog/flutter-in-2024-evolution-of-cross-platform-development/</link><pubDate>Fri, 15 Nov 2024 09:00:00 +0100</pubDate><guid>http://maciejzawieja.dev/blog/flutter-in-2024-evolution-of-cross-platform-development/</guid><description>&lt;p&gt;Flutter has undergone remarkable transformations since its initial release, and 2024/2025 marks a pivotal era in its evolution. With Google&amp;rsquo;s continued investment and a thriving community, Flutter has matured into a powerful framework for building beautiful, high-performance applications across multiple platforms.&lt;/p&gt;&#10;&lt;h2 id="the-new-architecture-impeller-rendering-engine"&gt;The New Architecture: Impeller Rendering Engine&lt;/h2&gt;&#10;&lt;p&gt;Perhaps the most significant advancement in Flutter&amp;rsquo;s recent history is the full rollout of the Impeller rendering engine. Initially introduced in beta, Impeller has now become the default rendering engine for both iOS and Android platforms. This change addresses one of Flutter&amp;rsquo;s historical pain points - inconsistent rendering performance, especially on iOS.&lt;/p&gt;</description></item><item><title>Node.js in 2024: The Performance Revolution</title><link>http://maciejzawieja.dev/blog/nodejs-2024-performance-revolution/</link><pubDate>Tue, 05 Nov 2024 09:00:00 +0100</pubDate><guid>http://maciejzawieja.dev/blog/nodejs-2024-performance-revolution/</guid><description>&lt;p&gt;Node.js continues to evolve as one of the most popular runtime environments for server-side JavaScript development. The release of Node.js 22 in April 2024 (with LTS status in October) marks a significant milestone in its journey, introducing groundbreaking performance improvements and feature enhancements that cement its position as a leading technology for building high-performance backend applications.&lt;/p&gt;&#10;&lt;h2 id="v8-engine-updates-the-maglev-compiler"&gt;V8 Engine Updates: The Maglev Compiler&lt;/h2&gt;&#10;&lt;p&gt;At the heart of Node.js 22&amp;rsquo;s performance leap is the updated V8 JavaScript engine (version 12.4.254.14), which introduces the revolutionary Maglev compiler. This just-in-time (JIT) compiler sits between the existing TurboFan and Sparkplug compilers in the V8 optimization pipeline.&lt;/p&gt;</description></item><item><title>Spring Boot 3.x: Embracing Modern Java for Cloud-Native Applications</title><link>http://maciejzawieja.dev/blog/spring-boot-3-embracing-modern-java/</link><pubDate>Tue, 22 Oct 2024 09:00:00 +0100</pubDate><guid>http://maciejzawieja.dev/blog/spring-boot-3-embracing-modern-java/</guid><description>&lt;p&gt;Spring Boot has revolutionized Java application development since its introduction, and its latest versions continue to push the boundaries of what&amp;rsquo;s possible with the platform. Spring Boot 3.x represents a significant evolution, embracing modern Java features, cloud-native paradigms, and performance optimizations that make it more relevant than ever in today&amp;rsquo;s development landscape.&lt;/p&gt;&#10;&lt;h2 id="java-21-and-22-support-the-new-foundation"&gt;Java 21 and 22 Support: The New Foundation&lt;/h2&gt;&#10;&lt;p&gt;Spring Boot 3.3+ fully supports Java 21 and 22, allowing developers to leverage the latest language features and performance improvements. This support brings numerous benefits:&lt;/p&gt;</description></item><item><title>Microservices and Cloud-Native Architecture in 2024: Trends and Best Practices</title><link>http://maciejzawieja.dev/blog/microservices-cloud-native-architecture-2024/</link><pubDate>Tue, 08 Oct 2024 09:00:00 +0100</pubDate><guid>http://maciejzawieja.dev/blog/microservices-cloud-native-architecture-2024/</guid><description>&lt;p&gt;The landscape of application architecture continues to evolve rapidly, with microservices and cloud-native approaches firmly established as the dominant paradigm for building scalable, resilient, and maintainable software systems. As we progress through 2024, several key trends and best practices have emerged that are reshaping how organizations design, deploy, and operate distributed systems. This article explores the current state of microservices and cloud-native architecture, highlighting emerging patterns, technologies, and challenges.&lt;/p&gt;&#10;&lt;h2 id="the-evolution-of-microservices-architecture"&gt;The Evolution of Microservices Architecture&lt;/h2&gt;&#10;&lt;p&gt;Microservices architecture has matured beyond its initial hype cycle into a nuanced approach with established patterns and practices. In 2024, we&amp;rsquo;re seeing several important evolutions:&lt;/p&gt;</description></item><item><title>React Native vs Flutter in 2024: Choosing the Right Cross-Platform Framework</title><link>http://maciejzawieja.dev/blog/react-native-vs-flutter-in-2024/</link><pubDate>Wed, 18 Sep 2024 09:00:00 +0100</pubDate><guid>http://maciejzawieja.dev/blog/react-native-vs-flutter-in-2024/</guid><description>&lt;p&gt;In the ever-evolving landscape of mobile app development, cross-platform frameworks have become increasingly sophisticated, offering compelling alternatives to native development. Two frameworks stand out in this space: React Native, developed by Meta (formerly Facebook), and Flutter, created by Google. As we progress through 2024, both have made significant strides, but which one is right for your next project? Let&amp;rsquo;s explore their current state, latest features, performance characteristics, and development experience to help you make an informed decision.&lt;/p&gt;</description></item></channel></rss>