<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Rahul Muraleedharan</title>
    <description>The latest articles on DEV Community by Rahul Muraleedharan (@frpboy).</description>
    <link>https://dev.to/frpboy</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4246127%2Fffe5bce6-a7ed-460b-ba90-da34217516c8.jpg</url>
      <title>DEV Community: Rahul Muraleedharan</title>
      <link>https://dev.to/frpboy</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/frpboy"/>
    <language>en</language>
    <item>
      <title>Flutter 3.50 is out: Material and Cupertino are deprecated - here's the migration path</title>
      <dc:creator>Rahul Muraleedharan</dc:creator>
      <pubDate>Sat, 21 Nov 2026 13:30:12 +0000</pubDate>
      <link>https://dev.to/frpboy/flutter-350-is-out-material-and-cupertino-are-deprecated-heres-the-migration-path-43k6</link>
      <guid>https://dev.to/frpboy/flutter-350-is-out-material-and-cupertino-are-deprecated-heres-the-migration-path-43k6</guid>
      <description>&lt;p&gt;Flutter 3.50 shipped on 11 November with Dart 3.14. The headline change is not a widget or a performance graph - it is a structural one: the Material and Cupertino libraries bundled with the framework are now formally deprecated, and their future lives in standalone packages.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Material/Cupertino split
&lt;/h2&gt;

&lt;p&gt;Flutter's bundled &lt;code&gt;material&lt;/code&gt; and &lt;code&gt;cupertino&lt;/code&gt; libraries are deprecated in 3.50. The replacements are the standalone &lt;code&gt;material_ui&lt;/code&gt; and &lt;code&gt;cupertino_ui&lt;/code&gt; packages, versioned independently of the framework. That decoupling means design-library updates can ship without waiting for a framework release - and the framework team can evolve without carrying them.&lt;/p&gt;

&lt;p&gt;The migration is meant to be mostly mechanical: &lt;code&gt;dart fix&lt;/code&gt; applies the bulk of the changes, and a &lt;code&gt;MaterialUiCompatibilityBridge&lt;/code&gt; exists for code that straddles both worlds during the transition. The official migration guide on docs.flutter.dev walks through it. If you maintain a package that depends on &lt;code&gt;package:flutter/material.dart&lt;/code&gt;, expect your users to start asking about this soon.&lt;/p&gt;

&lt;h2&gt;
  
  
  What else is in the release
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Native interop, finally consolidated.&lt;/strong&gt; A new Native interop documentation section pulls together the guides for calling native code on every platform: Pigeon, &lt;code&gt;package:ffigen&lt;/code&gt; for C and Objective-C, &lt;code&gt;package:jnigen&lt;/code&gt; for Java and Kotlin, and build hooks for bundling native code. If you have ever hunted these across five different READMEs, this is welcome.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Web keeps maturing.&lt;/strong&gt; A new &lt;code&gt;--web-content-hash&lt;/code&gt; build flag adds cache-busting hashes to web assets, and the Wasm documentation now covers real production concerns: server headers, pre-compression, cold-start latency, CDN asset loading, and profiling Core Web Vitals in Chrome DevTools.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Apple platform readiness.&lt;/strong&gt; The platform-integration docs now cover iOS 27, macOS 27 and Xcode 27, with expanded Swift Package Manager migration guidance for apps and plugins.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;AI tooling docs.&lt;/strong&gt; The AI section has been reorganized around a unified get-started guide, custom agents, and &lt;code&gt;package:skills_lint&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Should you upgrade now?
&lt;/h2&gt;

&lt;p&gt;As always with Flutter stable releases: run your test suite, read the breaking-changes page, and check your plugin stack first. The Material/Cupertino deprecation is not a removal - your app will keep building - but starting the migration early, while &lt;code&gt;dart fix&lt;/code&gt; and the compatibility bridge are fresh and documented, is cheaper than doing it under deadline later.&lt;/p&gt;

&lt;p&gt;Have you run &lt;code&gt;dart fix&lt;/code&gt; against a real codebase yet? Curious how clean the migration actually is in practice.&lt;/p&gt;

&lt;p&gt;Sources:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Flutter 3.50 release notes: &lt;a href="https://docs.flutter.dev/release/release-notes/release-notes-3.50.0" rel="noopener noreferrer"&gt;https://docs.flutter.dev/release/release-notes/release-notes-3.50.0&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;What's new (docs and migration guides): &lt;a href="https://docs.flutter.dev/release/whats-new" rel="noopener noreferrer"&gt;https://docs.flutter.dev/release/whats-new&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Breaking changes: &lt;a href="https://docs.flutter.dev/release/breaking-changes" rel="noopener noreferrer"&gt;https://docs.flutter.dev/release/breaking-changes&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>flutter</category>
      <category>dart</category>
      <category>mobiledev</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Python 3.16.0 alpha 2: faster UUIDs, richer regex, ECH</title>
      <dc:creator>Rahul Muraleedharan</dc:creator>
      <pubDate>Wed, 18 Nov 2026 13:30:05 +0000</pubDate>
      <link>https://dev.to/frpboy/python-3160-alpha-2-faster-uuids-richer-regex-ech-51jg</link>
      <guid>https://dev.to/frpboy/python-3160-alpha-2-faster-uuids-richer-regex-ech-51jg</guid>
      <description>&lt;p&gt;The second alpha of Python 3.16 landed on 10 November. It's an early developer preview - features can change until beta 1 in May 2027 and the final release is planned for October 2027 - but it's a good time to run your test suite against it.&lt;/p&gt;

&lt;p&gt;What's landing so far, compared with 3.15:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;More expressive regular expressions.&lt;/strong&gt; The &lt;code&gt;re&lt;/code&gt; module now supports nested character sets, set operations such as intersection and difference, and matching characters by Unicode properties (for example, uppercase letters).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Faster startup.&lt;/strong&gt; Python starts faster, and several common operations were optimised, including garbage collection and the construction of built-in objects.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Faster UUID generation.&lt;/strong&gt; &lt;code&gt;uuid4()&lt;/code&gt; and &lt;code&gt;uuid7()&lt;/code&gt; now have C implementations, making generation about 15-30x faster than the pure Python implementations in microbenchmarks.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Encrypted Client Hello.&lt;/strong&gt; The &lt;code&gt;ssl&lt;/code&gt; module adds support for ECH when built with OpenSSL 4.0 or later.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;More Apple platforms.&lt;/strong&gt; CPython can now be built for tvOS, watchOS and visionOS (not yet in the PEP 11 supported tiers).&lt;/p&gt;

&lt;p&gt;The next alpha, 3.16.0a3, is scheduled for 15 December. If you maintain a library, alpha season is the cheapest time to catch breakage - a CI job against the preview costs little and surfaces deprecations months before users hit them.&lt;/p&gt;

&lt;p&gt;Are you testing against the 3.16 alphas yet?&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://blog.python.org/2026/11/python-3160-alpha-2-is-now-available/" rel="noopener noreferrer"&gt;https://blog.python.org/2026/11/python-3160-alpha-2-is-now-available/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>python</category>
    </item>
  </channel>
</rss>
