<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>pieroxy.netwindows</title>
    <link>https://pieroxy.net/blog/tags/windows/</link>
    <description>tech, dev, web &amp; other stuff</description>
    <language>en</language>
    <copyright>Pieroxy</copyright>
    <pubDate>Thu, 25 Aug 2022 14:06:00 GMT</pubDate>
    <dc:creator>Pieroxy</dc:creator>
    <dc:date>2022-08-25T14:06:00Z</dc:date>
    <dc:language>en</dc:language>
    <dc:rights>Pieroxy</dc:rights>
    <image>
      <title>pieroxy.netwindows</title>
      <url>https://pieroxy.net/blog/tags/windows/</url>
    </image>
    <item>
      <title>Migration of Arbitrage from Windows to Mesos</title>
      <link>https://pieroxy.net/blog/2020/09/07/1599482220000.html</link>
      <content:encoded>&lt;p&gt;Note: Arbitrage is a "big" application in our ecosystem. Read further to see how big.

&lt;p&gt;This article is the last piece of our series about migrating apps at scale from .net (so, on Windows) to .netCore, on Mesos. It recaps the whole process:

&lt;a class="longLink" href="https://medium.com/criteo-labs/migration-of-arbitrage-from-windows-to-mesos-eddd4dbba732"&gt;https://medium.com/criteo-labs/migration-of-arbitrage-from-windows-to-mesos-eddd4dbba732&lt;/a&gt;</content:encoded>
      <category domain="https://pieroxy.net/blog/categories/general-rambling/">General rambling</category>
      <category domain="https://pieroxy.net/blog/tags/dev/">dev</category>
      <category domain="https://pieroxy.net/blog/tags/dotnet/">dotnet</category>
      <category domain="https://pieroxy.net/blog/tags/marathon/">marathon</category>
      <category domain="https://pieroxy.net/blog/tags/mesos/">mesos</category>
      <category domain="https://pieroxy.net/blog/tags/migration/">migration</category>
      <category domain="https://pieroxy.net/blog/tags/windows/">windows</category>
      <pubDate>Mon, 07 Sep 2020 12:37:00 GMT</pubDate>
      <guid isPermaLink="false">tag:pieroxy.net,2020-09-07:pieroxy.net/1599482220000</guid>
      <dc:date>2020-09-07T12:37:00Z</dc:date>
    </item>
    <item>
      <title>Chrome and Arial Narrow</title>
      <link>https://pieroxy.net/blog/2014/10/15/1413378480000.html</link>
      <content:encoded>&lt;img src="https://pieroxy.net/images/nuvola/128x128/apps/stylesheet.png" style="float: left; margin-right:20px;margin-bottom:10px;height:64px;width:64px"&gt;
&lt;p&gt;As you discovered with &lt;a href="https://pieroxy.net/blog/2014/10/11/the_quest_for_a_condensed_web_font.html"&gt;my previous entry&lt;/a&gt;, I was looking for nice condensed web fonts (read: native) for my headings. Well, I found plenty for everyone but for Chrome on Windows. Chrome issue is troublesome for me because this combination represent 30% of my traffic right now, by far outweighing other combinations of browser/OS. 

&lt;p&gt;How come I couldn't do it? I could do it with IE, Firefox on all platforms and Safari on all its platforms. Even Chrome on non-Windows platforms. It turns out that &lt;a href="http://caniuse.com/#search=font-stretch"&gt;Chrome does not support&lt;/a&gt; the &lt;span class="code"&gt;font-stretch: condensed&lt;/span&gt; CSS attribute. On other platforms, there are fonts that are condensed and can be targeted by using their name, but alas, &lt;b&gt;Arial Narrow&lt;/b&gt; is not a font you can target with Chrome (nor with Firefox), even though IE can target it. Note that &lt;b&gt;Franklin Gothic&lt;/b&gt; is in the same situation. 

&lt;p&gt;It's the first time Chrome is lagging in terms of features behind IE and Firefox (at least on something I use). 

&lt;p&gt;Let's hope Google addresses this problem as Arial Narrow is pretty much everywhere. And it's a pretty nice font, even though &lt;b&gt;Helvetica&lt;/b&gt; people have probably left my website by now.

&lt;p&gt;Edit on October 16: &lt;a href="https://code.google.com/p/chromium/issues/detail?id=410940"&gt;It is an issue with Chrome 37&lt;/a&gt;. So hopefully it'll get patched soon.
&lt;p&gt;Edit on October 21: Chrome 38 is out. This is fixed.</content:encoded>
      <category domain="https://pieroxy.net/blog/categories/css/">CSS</category>
      <category domain="https://pieroxy.net/blog/categories/web-design/">Web Design</category>
      <category domain="https://pieroxy.net/blog/categories/html/">html</category>
      <category domain="https://pieroxy.net/blog/tags/chrome/">chrome</category>
      <category domain="https://pieroxy.net/blog/tags/css/">css</category>
      <category domain="https://pieroxy.net/blog/tags/design/">design</category>
      <category domain="https://pieroxy.net/blog/tags/html/">html</category>
      <category domain="https://pieroxy.net/blog/tags/web/">web</category>
      <category domain="https://pieroxy.net/blog/tags/windows/">windows</category>
      <pubDate>Wed, 15 Oct 2014 13:08:00 GMT</pubDate>
      <guid isPermaLink="false">tag:pieroxy.net,2014-10-15:pieroxy.net/1413378480000</guid>
      <dc:date>2014-10-15T13:08:00Z</dc:date>
    </item>
  </channel>
</rss>

