<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: hydroteur</title><link>https://news.ycombinator.com/user?id=hydroteur</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 25 Apr 2026 21:41:36 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=hydroteur" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by hydroteur in "Leaving Neovim for Zed"]]></title><description><![CDATA[
<p>It depends on what you work with. If you debug a complex issue you need to check many different setups to see whether your suspicions are right. Then, having a nice workflow where you sticky edit  and run your code is quite important.<p>It's not always the case. Quite often the only way to investigate the issue is to run a cloud workload that takes several minutes to start. Still, if you write good code, you can try to isolate the issue for local debugging at some point.</p>
]]></description><pubDate>Mon, 19 Aug 2024 08:51:12 +0000</pubDate><link>https://news.ycombinator.com/item?id=41289162</link><dc:creator>hydroteur</dc:creator><comments>https://news.ycombinator.com/item?id=41289162</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41289162</guid></item></channel></rss>