<?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: Andrey Hugh</title>
    <description>The latest articles on DEV Community by Andrey Hugh (@huston007).</description>
    <link>https://dev.to/huston007</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F346909%2F6ae4db04-e626-40f4-a624-9ac12fe42d0e.jpg</url>
      <title>DEV Community: Andrey Hugh</title>
      <link>https://dev.to/huston007</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/huston007"/>
    <language>en</language>
    <item>
      <title>That's why I can't use Svelte</title>
      <dc:creator>Andrey Hugh</dc:creator>
      <pubDate>Fri, 06 Mar 2020 16:03:21 +0000</pubDate>
      <link>https://dev.to/huston007/that-s-why-i-would-not-use-svelte-5959</link>
      <guid>https://dev.to/huston007/that-s-why-i-would-not-use-svelte-5959</guid>
      <description>&lt;p&gt;Since the OpenSource era beginning, the modern developing environment is built from small and independent pieces. This is our power and our weakness. An average Web app can contain dozens or even hundreds of separate technologies. And this brings the power to replace some parts of it without touching another.&lt;/p&gt;

&lt;p&gt;This is especially true for the React related ecosystem: you are supposed to pick every single piece yourself and then build them up. This is hard, but this is powerful.&lt;/p&gt;

&lt;p&gt;Say, you are not tied to Babel to compile JSX, you can pick some another transpiler/compiler or even language such as Kotlin. Or you can use no JSX with &lt;a href="https://github.com/hyperhype/hyperscript"&gt;hyperscript&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;But, in Svelte it looks like you don't have the freedom to control every part of your stack. You &lt;a href="https://github.com/sveltejs/svelte/issues/1639"&gt;can't even use TypeScript&lt;/a&gt;, which gains popularity every day, and is de facto standard in some companies. There is some work is in progress on it, but &lt;a href="https://gist.github.com/orta/ce05553de3fa9ba847ab410f29f874a4"&gt;is far from finish&lt;/a&gt; I'm afraid.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--o0yO99uv--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/oazjx8w1z8un98zrvb9e.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--o0yO99uv--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/oazjx8w1z8un98zrvb9e.png" alt="Svelte TS issue"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I hope this will change in the future, but today it feels a deal-breaking thing.&lt;/p&gt;

</description>
      <category>svelte</category>
      <category>typescript</category>
    </item>
  </channel>
</rss>
