<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Pete Bacon Darwin on Medium]]></title>
        <description><![CDATA[Stories by Pete Bacon Darwin on Medium]]></description>
        <link>https://medium.com/@petebd?source=rss-ece7b098dce2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*H02C2-oYlIgXX0aT.</url>
            <title>Stories by Pete Bacon Darwin on Medium</title>
            <link>https://medium.com/@petebd?source=rss-ece7b098dce2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:22:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@petebd/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Angular localization with Ivy]]></title>
            <link>https://blog.angular.dev/angular-localization-with-ivy-4d8becefb6aa?source=rss-ece7b098dce2------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d8becefb6aa</guid>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[localisation]]></category>
            <category><![CDATA[i18n]]></category>
            <dc:creator><![CDATA[Pete Bacon Darwin]]></dc:creator>
            <pubDate>Wed, 09 Sep 2020 15:30:09 GMT</pubDate>
            <atom:updated>2020-09-11T13:54:10.694Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Angular i18n logo with colored circles featuring Hello in different languages." src="https://cdn-images-1.medium.com/max/960/1*tMHsCh8xsw_RE59bo-EvqA.png" /></figure><p>Part of the new Angular rendering engine, Ivy, includes a new approach to localizing applications — specifically extracting and translating text. This article explains the benefits and some of the implementation of this new approach.</p><p>Prior to Ivy, the only way to add localizable messages to an Angular application was to mark them in component templates using the i18n attribute:</p><pre>&lt;div i18n&gt;Hello, World!&lt;/div&gt;</pre><p>The Angular compiler would replace this text when compiling the template with different text if a set of translations was provided in the compiler configuration. The i18n tags are very powerful — they can be used in attributes as well as content; they can include complex nested <a href="http://userguide.icu-project.org/formatparse/messages">ICU (International Components for Unicode) expressions</a>; they can have metadata attached to them. See our <a href="https://angular.io/guide/i18n#prepare-templates-for-translations">i18n guide</a> for more information.</p><p>But there were some shortcomings to this approach.</p><p>The most significant concern was that translation had to happen during template compilation, which occurs right at the start of the build pipeline. The result of this is that that full build, compilation-bundling-minification-etc, had to happen for each locale that you wanted to support in your application.</p><figure><img alt="The build pipeline of a translated Angular application — pre-Ivy" src="https://cdn-images-1.medium.com/max/1024/1*kBX_aNeRPHqgpjLceM-3Ow.png" /><figcaption>(build times will vary based on project size)</figcaption></figure><p>If a single build took 3 minutes, then the total build time to support 9 locales would be 3 mins x 9 locales = 27 mins.</p><p>Moreover, it was not possible to mark text in application code for translation, only text in component templates. This resulted in awkward workarounds where artificial components were created purely to hold text that would be translated.</p><p>Finally, it was not possible to load translations at runtime, which meant it was not possible for applications to be provided to an end-user who might want to provide translations of their own, without having to build the application themselves.</p><p>The new localization approach is based around the concept of tagging strings in code with a <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals#Tagged_templates">template literal tag handler</a> called $localize. The idea is that strings that need to be translated are “marked” using this tag:</p><pre>const message = $localize `Hello, World!`;</pre><p>This $localize identifier can be a real function that can do the translation at runtime, in the browser. But, significantly, it is also a global identifier that survives minification. This means it can act simply as a marker in the code that a static post-processing tool can use to replace the original text with translated text before the code is deployed. For example, the following code:</p><pre>warning = $localize `${this.process} is not right`;</pre><p>could be replace with:</p><pre>warning = &quot;&quot; + this.process + &quot;, ce n&#39;est pas bon.&quot;;</pre><p>The result is that all references to $localize are removed, and there is <strong>zero runtime cost</strong> to rendering the translated text.</p><p>The Angular template compiler, for Ivy, has been redesigned to generate $localize tagged strings rather than doing the translation itself. For example the following template:</p><pre>&lt;h1 i18n&gt;Hello, World!&lt;/h1&gt;</pre><p>would be compiled to something like:</p><pre>ɵɵelementStart(0, &quot;h1&quot;);                //  &lt;h1&gt;<br>ɵɵi18n(1, $localize`Hello, World!`);    //  Hello, World!<br>ɵɵelementEnd();                         //  &lt;/h1&gt;</pre><p>This means that after the Angular compiler has completed its work all the template text marked with i18n attributes have been converted to $localize tagged strings which can be processed just like any other tagged string.</p><p>Notice also that the $localize tagged strings can occur in any code (user code or generated from templates in both applications or libraries) and are not affected by minification, so while the post-processing tool might receive code that looks like this</p><pre>...var El,kl=n(&quot;Hfs6&quot;),Sl=n.n(kl);El=<strong>$localize`Hello, World!`</strong>;let Cl=(()=&gt;{class e{constructor(e)...</pre><p>it is still able to identify and translate the tagged message. The result is that we can reorder the build pipeline to do translation at the very end of the process, resulting in a considerable build time improvement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nF_C-K05HC8TSAVcfn0DIg.png" /><figcaption>(build times will vary based on project size)</figcaption></figure><p>Here you can see that the build time is still 3 minutes, but since the translation is done as a post-processing step, we only incur that build cost once. Also the post-processing of the translations is very fast since the tool only has to parse the code for $localize tagged strings. In this case around 5 seconds.</p><p>The result is that the total build time for 9 locales is now 3 minutes + ( 9 x 5 seconds) = 3 minutes 45 seconds. Compared to 27 minutes for the pre-Ivy translated builds.</p><p>Similar improvements have been seen in real life by teams already using this approach:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RkunbzivjJHS4WZ2SaPlSQ.png" /></figure><p>The post-processing of translations is already built into the Angular CLI and if you have configured your projects according to our <a href="https://angular.io/guide/i18n#merge-translations-into-the-app">i18n guide</a> you should already be benefitting from these faster build times.</p><p>Currently the use of $localize in application code is not yet publicly supported or documented. We will be working on making this fully supported in the coming months. It requires new message extraction tooling — the current (pre-Ivy) message extractor does not find $localize text in application code. This is being integrated into the CLI now and should be released as part of 10.1.0.</p><p>We are also looking into how we can better support translations in 3rd party libraries using this new approach. Since this would affect the Angular Package Format (APF) we expect to run a Request for Comment (RFC) before implementing that.</p><p>In the meantime, enjoy the improved build times and keep an eye out for full support of application level localization of text.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d8becefb6aa" width="1" height="1" alt=""><hr><p><a href="https://blog.angular.dev/angular-localization-with-ivy-4d8becefb6aa">Angular localization with Ivy</a> was originally published in <a href="https://blog.angular.dev/">Angular Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stable AngularJS and Long Term Support]]></title>
            <link>https://blog.angular.dev/stable-angularjs-and-long-term-support-7e077635ee9c?source=rss-ece7b098dce2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e077635ee9c</guid>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[angularjs]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Pete Bacon Darwin]]></dc:creator>
            <pubDate>Fri, 26 Jan 2018 20:57:30 GMT</pubDate>
            <atom:updated>2020-08-11T19:07:14.646Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>AngularJS</strong> is planning one more significant release, version 1.7, and on July 1, 2018 it will enter a 3 year Long Term Support period.</p><blockquote><strong>UPDATE (2020–07–27):</strong><em><br>Due to COVID-19 affecting teams migrating from AngularJS, we are extending the LTS by six months (until December 31, 2021).</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dZTUzApSBnybrynw9bwKVQ.png" /><figcaption>AngularJS Panel at Angular Connect 2015</figcaption></figure><h3>Background</h3><p><a href="https://angularjs.org/">AngularJS</a> is an extremely stable framework for building web applications, and has been used by millions of developers across the web. <a href="https://angular.io/">Angular</a> is its successor and uses the same philosophies such as declarative templates and dependency injection.</p><p>Angular has been growing more than 5x faster than AngularJS did since its original release. In October of 2017, the user base of Angular passed 1 million developers (based on 30 day users to our documentation), and became larger than the user base of AngularJS. We have many exciting Angular releases planned in 2018 and beyond.</p><p>We understand that many developers are still using AngularJS, and that the migration process to Angular takes time and energy, but we also are aware that developers want clarity on the future AngularJS development plans.</p><h3>Schedule</h3><p>The team is currently working towards a release of AngularJS 1.7.0 and we will continue development of 1.7 through June 30, 2018. On July 1, we will enter a 3 year period of Long Term Support (LTS).</p><ul><li><strong>January 1 — June 30, 2018 </strong><a href="https://github.com/angular/angular.js/milestone/128">AngularJS 1.7</a> Active Development</li><li><strong>July 1, 2018 — December 31, 2021 </strong>AngularJS 1.7 LTS Period</li></ul><p><strong>All AngularJS applications that work now, will continue to work in the future. </strong>All published versions of AngularJS, on <a href="https://www.npmjs.com/package/angular">npm</a>, bower, <a href="https://ajax.googleapis.com/ajax/libs/angularjs/1.6.6/angular.min.js">CDNs</a>, etc will continue to be available. Our data indicates that the majority of AngularJS developers are not adopting the latest version updates, so the transition to LTS will be inconsequential to those developers.</p><h3>AngularJS 1.7 development</h3><p><strong>After the release of 1.7.0 the team does not intend to merge any feature or fix that will require even a minor breaking change.</strong></p><p>After 1.7.0 we will continue to develop AngularJS, publishing patch releases, 1.7.1, 1.7.2 etc, through Jun 30, 2018. These releases will only include non-breaking change features and fixes to the framework.</p><p>If there is a feature or fix that you believe should land in AngularJS 1.7.0, please report it via an <a href="https://github.com/angular/angular.js/issues?utf8=%E2%9C%93&amp;q=is%3Aopen">already open issue or PR</a>, or <a href="https://github.com/angular/angular.js/issues/new">create a new issue</a>.</p><h3>Long Term Support</h3><p><strong>On July 1st 2018, we will enter a Long Term Support period for AngularJS</strong>.</p><p>At this time we will focus exclusively on providing fixes to bugs that satisfy at least one of the following criteria:</p><ul><li>A security flaw is detected in the 1.7.x branch of the framework</li><li>One of the major browsers releases a version that will cause current production applications using AngularJS 1.7.x to stop working</li><li>The jQuery library releases a version that will cause current production applications using AngularJS 1.7.x to stop working.</li></ul><h3>Continuing the journey</h3><p>The Angular team and community have benefited so much from the countless people in the community who have provided feedback, bug fixes, new features, educational resources, built amazing libraries, run awesome conferences, and created fantastic applications. Thank you!</p><p>We look forward to joining you on the next exciting part of our journey together on the <a href="https://angular.io/">Angular platform</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e077635ee9c" width="1" height="1" alt=""><hr><p><a href="https://blog.angular.dev/stable-angularjs-and-long-term-support-7e077635ee9c">Stable AngularJS and Long Term Support</a> was originally published in <a href="https://blog.angular.dev/">Angular Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>