<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>WebDev on Dmitry Sheiko&#39;s Web Development Blog</title>
    <link>https://dsheiko.com/tags/webdev/</link>
    <description>Recent content in WebDev on Dmitry Sheiko&#39;s Web Development Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 20 Aug 2014 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://dsheiko.com/tags/webdev/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Harmony with TypeScript</title>
      <link>https://dsheiko.com/weblog/harmony-with-typescript/</link>
      <pubDate>Fri, 16 Nov 2012 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/harmony-with-typescript/</guid>
      <description>On the way to harmony Not so long ago Microsoft announced a new language targeting front-end developers. Everybody&amp;rsquo;s first reaction was &amp;ldquo;Why on Earth?!&amp;rdquo; Is it just Microsoft taking a shot at Google? Is that a trick to promote Visual Studio?&#xA;But anyway, what&amp;rsquo;s wrong with JavaScript? Why is everybody so keen to replace it? For a language designed in just two weeks, JavaScript is freakishly powerful and flexible. It was released in December 1995 and standardized as ECMA-262 in June 1997.</description>
    </item>
  </channel>
</rss>
