<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: potatolicious</title><link>https://news.ycombinator.com/user?id=potatolicious</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 16 Apr 2026 03:15:50 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=potatolicious" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by potatolicious in "Gas Town's agent patterns, design bottlenecks, and vibecoding at scale"]]></title><description><![CDATA[
<p>> <i>"If you say two different and contradictory things, and do not very explicitly resolve them, and say which one is the final answer, you will get blamed for both things you said, and you will not be entitled to complain about it, because you did it to yourself."</i><p>If I can be a bit bold and observe that this tic is also a very old rhetorical trick you see in our industry. Call it Schrodinger's Modest Proposal if you will.<p>In it someone writes something provocative, but casts it as <i>both a joke and deadly serious</i> at various points. Depending on how the audience reacts they can then double down on it being all-in-good-jest or yes-absolutely-totally. People who enjoy the author will explain the nonsensical tension as "nuance".<p>You see it in rationalist writing all the time. It's a tiresome rhetorical "trick" that doesn't fool anyone any more.</p>
]]></description><pubDate>Fri, 23 Jan 2026 21:35:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=46738254</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=46738254</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46738254</guid></item><item><title><![CDATA[New comment by potatolicious in "Valve is running Apple's playbook in reverse"]]></title><description><![CDATA[
<p>Are they actually running the Apple playbook in reverse? It seems to me that they're actually running Apple's playbook pretty squarely, just in another domain.<p>First-gen product that seemed to not know where it's going? Check.<p>Continued quiet iteration behind closed doors despite first-gen being a flop? Check.<p>Sticking with the product line over many years, where most other companies would have written off and thrown in the towel? Check.<p>Multi-pronged GTM strategy where other products prove out key bits of next product? Check. (see: SteamOS and Proton setting the stage for Steam Deck, which in turn sets the stage for Steam Machine 2)<p>Deep software-hardware integration in ways that are highly salient to users? Check (see: foviated streaming for Steam Frame, Steam Deck "just works")</p>
]]></description><pubDate>Thu, 18 Dec 2025 16:57:57 +0000</pubDate><link>https://news.ycombinator.com/item?id=46315285</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=46315285</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46315285</guid></item><item><title><![CDATA[New comment by potatolicious in "Rivian Unveils Custom Silicon, R2 Lidar Roadmap, and Universal Hands Free"]]></title><description><![CDATA[
<p>I share your skepticism. This feels like an attempt to tap the trainloads of money piling into "AI", for a company that is in pretty desperate need of more cash to stay alive.<p>In a vacuum there are potentially some advantages to doing your own silicon, especially if your goal is to sell the platform to other automakers as an OEM.<p>But custom silicon is pricey as hell (if you're doing anything non-trivial, at least), and the payoffs have a long lead time. For a company that's bleeding cash aggressively, with a short runway, to engage in this seems iffy. This sort of move makes a lot more sense if Rivian was an established maker that's cash-flow positive and is looking to cement their long-term lead with free cash flow. Buuuuut they aren't that.</p>
]]></description><pubDate>Thu, 11 Dec 2025 19:03:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=46235625</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=46235625</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46235625</guid></item><item><title><![CDATA[New comment by potatolicious in "Trying out Gemini 3 Pro with audio transcription and a new pelican benchmark"]]></title><description><![CDATA[
<p>You really want to break a task like this down to constituent parts - especially because in this case the "end to end" way of doing it (i.e., raw audio to summary) doesn't actually get you anything.<p>IMO the right way to do this is to feed the audio into a transcription model, specifically one that supports diarization (separation of multiple speakers). This will give you a high quality raw transcript that <i>is</i> pretty much exactly what was actually said.<p>It would be rough in places (i.e., Speaker 1, Speaker 2, etc. rather than actual speaker names)<p>Then you want to post-process with a LLM to re-annotate the transcript and clean it up (e.g., replace "Speaker 1" with "Mayor Bob"), and query against it.<p>I see another post here complaining that direct-to-LLM beats a transcription model like Whisper - I would challenge that. Any modern ASR model will do a very, very good job with 95%+ accuracy.</p>
]]></description><pubDate>Tue, 18 Nov 2025 20:38:45 +0000</pubDate><link>https://news.ycombinator.com/item?id=45971701</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45971701</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45971701</guid></item><item><title><![CDATA[New comment by potatolicious in "Steam Frame"]]></title><description><![CDATA[
<p>Your 2K monitor occupies something like a 20-degree field of view from a normal sitting position/distance. The 2K resolution in a VR headset covers the entire field of view.<p>So effectively your 1080p monitor has ~6x the pixel density of the VR headset.</p>
]]></description><pubDate>Wed, 12 Nov 2025 21:15:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=45906823</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45906823</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45906823</guid></item><item><title><![CDATA[New comment by potatolicious in "Steam Frame"]]></title><description><![CDATA[
<p>Yes but that can create major motion sickness issues - motion that does not correspond top the user's actual physical movements create a dissonance that is expressed as motion sickness for a large portion of the population.<p>This is the main reason many VR games don't let you just walk around and opt for teleportation-based movement systems - your avatar moving while your body doesn't can be quite physically uncomfortable.<p>There are ways of minimizing this - for example some VR games give you "tunnel vision" by blacking out peripheral vision while the movement is happening. But overall there's a <i>lot</i> of ergo considerations here and no perfect solution. The equivalent for a virtual desktop might be to limit the size of the window while the user is zooming/panning.</p>
]]></description><pubDate>Wed, 12 Nov 2025 21:13:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=45906792</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45906792</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45906792</guid></item><item><title><![CDATA[New comment by potatolicious in "Steam Frame"]]></title><description><![CDATA[
<p>Oh yeah for sure. Most people seem to accept that 35ppd is "good enough" but not actually at-par with a high quality high-dpi monitor.<p>I agree with you - I would personally consider 35ppd to be the <i>floor</i> for usability for this purpose. It's good in a pinch (need a nice workstation setup in a hotel room?) but I would not currently consider any extant hardware as full-time replacements for a good monitor.</p>
]]></description><pubDate>Wed, 12 Nov 2025 20:37:55 +0000</pubDate><link>https://news.ycombinator.com/item?id=45906275</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45906275</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45906275</guid></item><item><title><![CDATA[New comment by potatolicious in "Steam Frame"]]></title><description><![CDATA[
<p>There's no precise criteria but the usual measure is ppd (pixels per degree) and it needs to be high enough such that detailed content (such as text) displayed at a reasonable size is clearly legible without eye strain.<p>> <i>"Could you not just move your face closer to the virtual screen to see finer details?"</i><p>Sure, but then you have the problem of, say, using an IMAX screen as your computer monitor. The level of head motion required to consume screen content (i.e., a ton of large head movements) would make the device very uncomfortable quite quickly.<p>The Vision Pro has about ~35ppd and generally people seems to think it hits the bar for monitor replacement. Meta Quest 3 has ~25ppd and generally people seem to think it does not. The Steam Frame is specs-wise much closer to Quest 3 than Vision Pro.<p>There are <i>some</i> software things you can do to increase legibility of details like text, but ultimately you do need physical pixels.</p>
]]></description><pubDate>Wed, 12 Nov 2025 19:37:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=45905175</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45905175</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45905175</guid></item><item><title><![CDATA[New comment by potatolicious in "Steam Frame"]]></title><description><![CDATA[
<p>The Verge reports similarly - can't tell foveated streaming. Seems like Valve really cracked the code with this one.</p>
]]></description><pubDate>Wed, 12 Nov 2025 19:21:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=45904875</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45904875</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45904875</guid></item><item><title><![CDATA[New comment by potatolicious in "EVs are depreciating faster than gas-powered cars"]]></title><description><![CDATA[
<p>Listen, I'm literally just describing basic market dynamics here - my post is not intended as an <i>endorsement</i> of plainly observable phenomena.<p>The depreciation/utility curve has always been aggressive no matter what product you're buying. Is a 2 year-old ICE car twice as bad as a new one? Is a 2 year-old TV? Clearly not, yet they are all worth that in the open market.<p>For EVs the depreciation curve is especially aggressive because of perceived advancements. Are the advancements <i>worth</i> buying new? I dunno! You tell me - but this is clearly being reflected in the market.<p>From a strict utilitarian standpoint, optimizing your depreciation/utility function should mean you're buying almost every single thing used. But yet lots of people don't do that. Humans are empirically not very good utilitarians!</p>
]]></description><pubDate>Fri, 17 Oct 2025 17:53:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=45619699</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45619699</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45619699</guid></item><item><title><![CDATA[New comment by potatolicious in "EVs are depreciating faster than gas-powered cars"]]></title><description><![CDATA[
<p>> <i>"What part of EVs is "rapidly advancing technologically"?"</i><p>Battery capacity, motor efficiency (getting more range out of the same battery), charging rate (800V architectures for example that let you charge > 150kW), battery chemistry (wider operating temp envelope, affects charging and driving efficiency depending on environment)... the list goes on.<p>The batteries are also getting cheaper - which is to say for the same $ you're now (generally) getting a larger battery.<p>> <i>"If so, why aren't used dealers just including a battery swap in the price?"</i><p>Because the batteries are in fact not swappable from one gen to the next, because the power electronics around them are different, peak current draw is different (and that depends on the motor it's mated with!).<p>Like I know it's tempting and attractive to imagine EVs like regular cars with some giant-ass AA batteries installed on them, but that's not how they work! The battery is specced as a unit with the entire electrical system and drive motor options!</p>
]]></description><pubDate>Fri, 17 Oct 2025 17:39:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=45619523</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45619523</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45619523</guid></item><item><title><![CDATA[New comment by potatolicious in "EVs are depreciating faster than gas-powered cars"]]></title><description><![CDATA[
<p>> and get something way better.<p>The last part of OP's statement is the key. In a field that's rapidly advancing technologically, used prices are depressed because the new product is <i>that</i> much better than the used product.<p>Think back to the early smartphone days - every year phones multiplied in performance, in screen resolution, etc. In that environment a used item is less attractive because you feel like you're missing out on features/capability. This keeps used prices down. Nowadays used smartphones are more competitive because the rate of advancement (that buyers care about at least) has slowed.<p>For example there's another post later in this thread that points out that the Nissan Leaf has been the same price forever - except the current-gen Leaf has literally double the range of the last one. Effects like this depress used prices.</p>
]]></description><pubDate>Fri, 17 Oct 2025 16:44:45 +0000</pubDate><link>https://news.ycombinator.com/item?id=45618851</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45618851</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45618851</guid></item><item><title><![CDATA[New comment by potatolicious in "Apple M5 chip"]]></title><description><![CDATA[
<p>Because there's more to "actual user experience" than peak CPU/GPU/NPU workload.<p>Firstly, the M5 isn't 4-6x more powerful than M4 - the claim is only for GPU, only for one narrow workload, not overall performance uplift. Overall performance uplift looks like ~20% over M4, and probably +100% over M1 or so.<p>But there is absolutely a <i>massive</i> sea change in the MacBook since Intel 5 years ago: your peak workloads haven't changed much, but the hardware improvements give you <i>radically</i> different UX.<p>For one thing, the Intel laptops absolutely burned through the battery. Five years ago the notion of the all-day laptop was a fantasy. Even relatively light users were tethered to chargers most of the day. This is now almost fully a thing of the past. Unless your workloads are very heavy, it is now safe to charge the laptop once a day. I can go many hours in my workday without charging. I can go through a long flight without any battery anxiety. This is a <i>massive</i> change in how people use laptops.<p>Secondly is heat and comfort. The Intel Macs spun their fans up at even mild workloads, creating noise and heat - they were often very uncomfortably warm. Similar workloads are now completely silent with the device barely getting warmer than ambient temp.<p>Thirdly is allowing more advanced uses on lower-spec and less expensive machines. For example, the notion of rendering and editing video on a Intel MacBook Air was a total pipe dream. Now a base spec MacBook Air can do... a <i>lot</i> that once forced you into a much higher price point/size/weight.<p>A lot of these HN conversations feel like sports car fans complaining: "all this R&D and why doesn't my car go 500mph yet?" - there are other dimensions being optimized for!</p>
]]></description><pubDate>Wed, 15 Oct 2025 17:12:06 +0000</pubDate><link>https://news.ycombinator.com/item?id=45595636</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45595636</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45595636</guid></item><item><title><![CDATA[New comment by potatolicious in "Why is everything so scalable?"]]></title><description><![CDATA[
<p>Funnily enough prior to this startup I had worked at a rainforest-themed big tech co where we ran <i>all kinds of stuff</i> on MySQL without issue, at scales that dwarfed what this startup was up to by 3-4 orders of magnitude.<p>I feel like that's kind of the other arm of this whole argument: on the one hand, you ain't gonna need that "scalable" thing. On the other hand, the "unscalable" thing scales waaaaaay higher than you are led to believe.<p>A single primary instance with a few read-only mirrors gets you a reaaaaaaally long way before you have to seriously think about doing something else.</p>
]]></description><pubDate>Tue, 14 Oct 2025 13:53:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=45580076</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45580076</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45580076</guid></item><item><title><![CDATA[New comment by potatolicious in "Why is everything so scalable?"]]></title><description><![CDATA[
<p>Ah yes. I once worked at a startup that insisted on Mongo despite not having <i>anywhere</i> near the data volume for it to make any sense at all. Like, we're talking 5 orders of magnitude off of what one would reasonably expect to need a Mongo deployment.<p>I was but a baby engineer then, and the leads would not countenance anything as pedestrian as MySQL/Postgres.<p>Anyway, fast forward a bit and we were tasked with building an in-house messaging service. And at that point Mongo's eventual consistency became a roaring problem. Users would get notifications that they had a new message, and then when they tried to read it it was... well... not yet consistent.<p>We ended up implementing all kinds of ugly UX hacks to work around this, but really we could've run the entire thing off of sqlite on a single box and users would've been able to read messages instantaneously, so...</p>
]]></description><pubDate>Tue, 14 Oct 2025 13:29:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=45579806</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45579806</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45579806</guid></item><item><title><![CDATA[New comment by potatolicious in "Software update bricks some Jeep 4xe hybrids over the weekend"]]></title><description><![CDATA[
<p>This is generally how other devices work as well - for example all Android devices and Android-derivatives (which many of these cars are!) use a similar A/B partition to prevent bricking.<p>It definitely <i>reduces</i> the risk of updates, but it absolutely doesn't eliminate it.<p>The A/B updater itself is a surface area - especially if the logic is complex and there are other child devices that are updated at the same time (likely for cars). In that case you're not just coordinating between two independent partitions, you're coordinating between 2 * N partitions, half of which have dependencies on each other.<p>Also, the key bit of the mechanism is that upon successful boot the new partition is flagged as "good", which causes flags to be set to assert that the update was successful and the backup partition is no longer needed. <i>That</i> logic can (and does) fail - if your failure point occurs after this checkpoint you're hosed still because you're past the point of no return.<p>Making that worse is that in most systems you want the "it's all good" checkpoint to occur early - you don't want to, for example, wait multiple minutes for all user services to come up. But that also means that if a critical failure happens in said services, you're past the checkpoint.</p>
]]></description><pubDate>Mon, 13 Oct 2025 17:07:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=45570775</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45570775</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45570775</guid></item><item><title><![CDATA[New comment by potatolicious in "Superpowers: How I'm using coding agents in October 2025"]]></title><description><![CDATA[
<p>You can measure probabilistic systems that you can't examine! I don't want to throw the baby out with the bathwater here - before LLMs became the all-encompassing elephant in the room we did this routinely.<p>You absolutely can quantify the results of a chaotic black box, in the same way you can quantify the bias of a loaded die without examining its molecular structure.</p>
]]></description><pubDate>Sat, 11 Oct 2025 23:05:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=45553481</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45553481</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45553481</guid></item><item><title><![CDATA[New comment by potatolicious in "Superpowers: How I'm using coding agents in October 2025"]]></title><description><![CDATA[
<p>What you're getting at is the heart of the problem with the LLM hype train though, isn't it?<p>"We should have rigorous evaluations of whether or not [thing] works." seems like an incredibly obvious thought.<p>But in the realm of LLM-enabled use cases they're also <i>expensive</i>. You'd need to recruit dozens, perhaps even hundreds of developers to do this, with extensive observation and rating of the results.<p>So rather than actually try to measure the efficacy, we just get blog posts with cherry-picked example of "LLM does something cool". Everything is just anecdata.<p>This is also the biggest barrier to actual LLM adoption for many, many applications. The gap between "it does something REALLY IMPRESSIVE 40% of the time and shits the bed otherwise" and "production system" is a yawning chasm.</p>
]]></description><pubDate>Sat, 11 Oct 2025 16:28:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=45550404</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45550404</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45550404</guid></item><item><title><![CDATA[New comment by potatolicious in "The great software quality collapse or, how we normalized catastrophe"]]></title><description><![CDATA[
<p>Moore's Law has been dead for a long time. The doubling rate of transistors is now drastically below Moore's prediction.<p>We're adding transistors at ~18%/year. That's waaaaay below the ~41% needed to sustain Moore's law.<p>Even the "soft" version of Moore's law (a description of silicon performance vs. literally counting transistors) hasn't held up. We are absolutely not doubling performance every 24 months at this point.</p>
]]></description><pubDate>Thu, 09 Oct 2025 16:20:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=45529820</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45529820</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45529820</guid></item><item><title><![CDATA[New comment by potatolicious in "McKinsey wonders how to sell AI apps with no measurable benefits"]]></title><description><![CDATA[
<p>> <i>"Why even have employees then? Why not just milk your monopoly, keep the team lean, and let everybody involved have a big share of the profits?"</i><p>So we're seeing this play out. There are two factors that exist in tension here:<p>- The valuation of many of these companies depend on the perception that they are The Future. Part of that is heavy R&D spending and the reputation that they hire The Best. Even if the company mostly just wants to sit and milk its market position, keeping the stock price afloat requires looking like they're also innovative and forging the future.<p>- Some companies <i>are</i> embracing the milk-it-for-all-its-worth life stage of their company. You see this in some of the Mag-7 where compensation targets are scaling down, explicit and implicit layoffs, etc. This gear-shifting takes time but IMO is in fact happening.<p>The tightrope they're all trying to walk is how to do the latter without risking their reputation as the former, because the mythos that they are the engines of future growth is what keeps the stock price ticking.</p>
]]></description><pubDate>Thu, 09 Oct 2025 14:19:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=45528077</link><dc:creator>potatolicious</dc:creator><comments>https://news.ycombinator.com/item?id=45528077</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45528077</guid></item></channel></rss>