<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gui on Rowanto Luo</title><link>https://log.rowanto.com/categories/gui/</link><description>Recent content in Gui on Rowanto Luo</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 13 Jun 2021 22:32:38 +0200</lastBuildDate><atom:link href="https://log.rowanto.com/categories/gui/index.xml" rel="self" type="application/rss+xml"/><item><title>KDE in wsl2</title><link>https://log.rowanto.com/posts/kde-in-wsl2/</link><pubDate>Sun, 13 Jun 2021 22:32:38 +0200</pubDate><guid>https://log.rowanto.com/posts/kde-in-wsl2/</guid><description>
&lt;p&gt;Cheers 🍻 to those who owns a surface pro x and tries to do some development work on it.&lt;/p&gt;
&lt;p&gt;By now, most is probably regretting why they didn&amp;rsquo;t buy a normal non-ARM surface pro or just an M1. Although wsl2 is very nice, it is not really mature enough. It has some nasty bugs such as &lt;a href="https://github.com/microsoft/WSL/issues/4946"&gt;slow network&lt;/a&gt; and &lt;a href="https://github.com/microsoft/WSL/issues/4197"&gt;slow filesystem&lt;/a&gt;, which leads to a big pain when development code is running on WSL while being accessed from a browser or IDE in windows. This pain explodes further by the fact that almost no IDE except VS Code runs on the windows ARM platform.&lt;/p&gt;</description></item></channel></rss>