<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: l3000</title><link>https://news.ycombinator.com/user?id=l3000</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 10 Sep 2026 19:18:24 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=l3000" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by l3000 in "Jellyfin 12.0"]]></title><description><![CDATA[
<p>Moonfin?</p>
]]></description><pubDate>Tue, 08 Sep 2026 08:39:07 +0000</pubDate><link>https://news.ycombinator.com/item?id=49607415</link><dc:creator>l3000</dc:creator><comments>https://news.ycombinator.com/item?id=49607415</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49607415</guid></item><item><title><![CDATA[New comment by l3000 in "How the brain processes German and Arabic"]]></title><description><![CDATA[
<p>The thing is, when you become accustomed to the language there is no such thing as keeping stuff in the working memory. I think that’s just a convoluted way of explaining the processes that are behind speaking/understanding a language. As a native speaker of German I pretty much know at the first few words of the sentence which verb/words will have to follow and how the sentence will have to end. The meaning or information is not necessarily encoded in the verb or in those words that are moved to the end of the sentence. It’s just the shell of the sentence that is so common and you‘ll see/hear so often, you don‘t think about it anymore. Ultimately it‘s just pattern recognition that doesn’t require a lot of effort, IF you know the sentence structures that go with it.<p>That’s also why I guess learning a language with a lot of input goes a long way to absorb the structure of a language, because at some point you‘ve seen everything and only the important bits (the real information) remain if you look at a sentence.</p>
]]></description><pubDate>Fri, 16 Jun 2023 06:50:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=36352472</link><dc:creator>l3000</dc:creator><comments>https://news.ycombinator.com/item?id=36352472</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36352472</guid></item><item><title><![CDATA[New comment by l3000 in "Could your gut bacteria influence how intelligent you are?"]]></title><description><![CDATA[
<p><a href="https://archive.is/0N0lX" rel="nofollow noreferrer">https://archive.is/0N0lX</a></p>
]]></description><pubDate>Sun, 11 Jun 2023 08:44:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=36279463</link><dc:creator>l3000</dc:creator><comments>https://news.ycombinator.com/item?id=36279463</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36279463</guid></item><item><title><![CDATA[New comment by l3000 in "Korean as a Concatenative, Stack-Oriented Language (2017)"]]></title><description><![CDATA[
<p>I may want to add that as a person who had a lot of exposure to Korean (but is not native). Directly translating for instance “나는 라면” with the example context you mentioned, feels like „in my case, Ramen“. The 는/은 is describing the 나 in a way that is contrasting whatever was said in the current context. It is certainly used for saying something that is different from the other. „Well in MY case, it is …“, but it may work for other cases too, I am not totally sure.</p>
]]></description><pubDate>Sun, 16 Apr 2023 20:03:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=35593778</link><dc:creator>l3000</dc:creator><comments>https://news.ycombinator.com/item?id=35593778</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=35593778</guid></item></channel></rss>