<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: lucasacosta_</title><link>https://news.ycombinator.com/user?id=lucasacosta_</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 06 May 2026 21:42:06 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=lucasacosta_" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by lucasacosta_ in "The bottleneck was never the code"]]></title><description><![CDATA[
<p>same</p>
]]></description><pubDate>Wed, 06 May 2026 17:00:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=48038588</link><dc:creator>lucasacosta_</dc:creator><comments>https://news.ycombinator.com/item?id=48038588</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48038588</guid></item><item><title><![CDATA[New comment by lucasacosta_ in "E-paper display reaches the realm of LCD screens"]]></title><description><![CDATA[
<p>That sounds like the way to go. In terms of reading books (my normal usage of e-ink readers) you don't need 60hz when flipping a page, but it's a must when trying to use an app menu, or using Google Drive for example.<p>Identifying when to increase the refresh rate may be a challenge but I can see it pretty doable for this kind of "limited" scenarios where you either read or navigate a storage app.</p>
]]></description><pubDate>Wed, 10 Sep 2025 13:01:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=45197004</link><dc:creator>lucasacosta_</dc:creator><comments>https://news.ycombinator.com/item?id=45197004</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45197004</guid></item><item><title><![CDATA[New comment by lucasacosta_ in "Implementing a Foil Sticker Effect"]]></title><description><![CDATA[
<p>I stood amazed at how real it looks. Incredible job!!</p>
]]></description><pubDate>Tue, 02 Sep 2025 12:54:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=45102494</link><dc:creator>lucasacosta_</dc:creator><comments>https://news.ycombinator.com/item?id=45102494</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45102494</guid></item><item><title><![CDATA[New comment by lucasacosta_ in "Gemini Diffusion"]]></title><description><![CDATA[
<p>Definitely. For now the "frontier-level" papers (working with repository-level coding maintenance) need to necessarily depend on previously (and statically) generated Code Knowledge Graphs or Snippet-Retrieval systems, which makes the <i>scalable</i> and <i>fast</i> aspects complicated, as any change in the code would represent a change in the graph, hence requiring a rebuild.
But given the context limit, you need to rely on Graph queries to give relevant parts and then at the end of the day it just reads snippets instead of the full code, which makes the <i>consistent</i> an issue, as it can't learn from the entirety of the code.<p>Papers I'm referring to (just some as example, as there're more):<p>- CodexGraph [<a href="https://arxiv.org/abs/2408.03910" rel="nofollow">https://arxiv.org/abs/2408.03910</a>] - Graph<p>- Agentless [<a href="https://arxiv.org/abs/2407.01489" rel="nofollow">https://arxiv.org/abs/2407.01489</a>] - Snippet-Retrieval</p>
]]></description><pubDate>Thu, 22 May 2025 12:46:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=44061525</link><dc:creator>lucasacosta_</dc:creator><comments>https://news.ycombinator.com/item?id=44061525</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44061525</guid></item><item><title><![CDATA[New comment by lucasacosta_ in "Show HN: Aberdeen – An elegant approach to reactive UIs"]]></title><description><![CDATA[
<p>Considering there's no written html and no server side, how do you deal with SEO? (taking into account the possibility of non-JS agents)</p>
]]></description><pubDate>Mon, 12 May 2025 14:29:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=43963402</link><dc:creator>lucasacosta_</dc:creator><comments>https://news.ycombinator.com/item?id=43963402</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43963402</guid></item><item><title><![CDATA[New comment by lucasacosta_ in "Show HN: Aberdeen – An elegant approach to reactive UIs"]]></title><description><![CDATA[
<p>At first glance and on a syntax level, Vue from the start had part of its code in html syntax and the rest on JS. Aberdeen goes fully into JS.<p>So if I get it right, in Aberdeen there would not be any pure html written at all, right? Is that the "ideal"? Or it would be more of a hybrid with Aberdeen accompanying plain html?</p>
]]></description><pubDate>Fri, 09 May 2025 14:30:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=43937206</link><dc:creator>lucasacosta_</dc:creator><comments>https://news.ycombinator.com/item?id=43937206</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43937206</guid></item><item><title><![CDATA[New comment by lucasacosta_ in "Show HN: I made a app that uses NFC as a physical switch to block distractions"]]></title><description><![CDATA[
<p>I'll be waiting for it over here in Argentina too!</p>
]]></description><pubDate>Wed, 22 Jan 2025 13:15:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=42792457</link><dc:creator>lucasacosta_</dc:creator><comments>https://news.ycombinator.com/item?id=42792457</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=42792457</guid></item></channel></rss>