<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: phire</title><link>https://news.ycombinator.com/user?id=phire</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 01 Jun 2026 18:13:26 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=phire" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by phire in "Microcode inside the Intel 8087 floating-point chip: register exchange"]]></title><description><![CDATA[
<p>IMO, the <i>way</i> the error bars combine is very intuitive. You are really just rounding to 6 or 12 sig-figs after every operation.<p>People just seem to get really hung up on the point that error bars exist in the first place, and combine.<p>I suspect it has a lot to do with the way that rounding is taught in school. It's absolutely hammered into use that you should never round until the very end, otherwise you lose precision.</p>
]]></description><pubDate>Sun, 31 May 2026 09:53:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=48344364</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=48344364</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48344364</guid></item><item><title><![CDATA[New comment by phire in "A successful Japanese trial of a ramjet engine designed for Mach‑5 aircraft"]]></title><description><![CDATA[
<p>That was only an issue because they were fired pretty much straight up; They only went 500km down range.<p>You can also reduce peek deceleration forces by using aerodynamic lift to stretch out the reentry over a longer period.</p>
]]></description><pubDate>Tue, 26 May 2026 14:48:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=48280621</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=48280621</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48280621</guid></item><item><title><![CDATA[New comment by phire in "A successful Japanese trial of a ramjet engine designed for Mach‑5 aircraft"]]></title><description><![CDATA[
<p>The individual aircraft could be operationally viable on certain routes, but the whole program was not commercially viable.</p>
]]></description><pubDate>Tue, 26 May 2026 10:28:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=48277694</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=48277694</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48277694</guid></item><item><title><![CDATA[New comment by phire in "A successful Japanese trial of a ramjet engine designed for Mach‑5 aircraft"]]></title><description><![CDATA[
<p>Is a Mach-5 passenger aircraft actually the goal of this project?<p>Seems more likely that Japan is designing this engine for a hypersonic cruise missile program, and the passenger aircraft concept is somewhat of a cover.<p>IMO, there is no point in a Mach-5 Aircraft (other than cruise missiles). There is potentially some point in Mach 2-3 aircraft, (not that we have ever made them commercially viable) but at the boundary to hypersonic, you might as well just switch to a suborbital hop concept.<p>A suborbital hop gets you to anywhere in the world within ~90min, avoids issues of supersonic overflight and you don't need to worry about the massive engineering issues caused by sustaining hypersonic flight. And as a bonus, the passengers get a hour of weightlessness.</p>
]]></description><pubDate>Tue, 26 May 2026 06:45:12 +0000</pubDate><link>https://news.ycombinator.com/item?id=48275951</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=48275951</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48275951</guid></item><item><title><![CDATA[New comment by phire in "z386: An Open-Source 80386 Built Around Original Microcode"]]></title><description><![CDATA[
<p>No contest really: RISCV is a much better ISA, VexRISC is a hyper-optimised implementation of it (for FPGAs), and it's not hindered by trying to be microcode compatible.<p>The roughly equivalent VexRISC configuration (full with MMU) is only 2736 LUTs, running at 124 Mhz (on Cyclone V, which I'm pretty sure is the same arch)</p>
]]></description><pubDate>Sat, 23 May 2026 23:30:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=48252658</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=48252658</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48252658</guid></item><item><title><![CDATA[New comment by phire in "80386 microcode disassembled"]]></title><description><![CDATA[
<p>I wouldn’t say it didn’t have <i>any</i> microcode. It actually had a small PLA for sequencing the multi-cycle instructions. <i>[0]</i><p>I don’t think anyone would actually label it as microcode (not when the entire point of RISC was to avoid microcode) they would call it a sequencer or finite state machine; But really it’s the same thing. It’s certainly much simpler than the full microcode of any contemporary CISC, and the bulk of instructions execute in a single cycle without using it.<p>If you want a design with zero microcode, you really need to look at MIPS, or the original Berkeley RISC. Those ISAs go out of their way to avoid multicycle instructions. Not entirely successfully, but they don't use PLAs <i>[1]</i> to implement any state machines for the few remaining instructions like multiply and divide.<p><i>[0]</i> <a href="http://daveshacks.blogspot.com/2016/01/inside-armv1-instruction-decoding-and.html" rel="nofollow">http://daveshacks.blogspot.com/2016/01/inside-armv1-instruct...</a><p><i>[1]</i> <i>At least on the few MIPS designs I've looked at.</i> <i>And I'm not sure if they deliberately avoided PLAs for doctrine reasons, or it was just more efficient to do so.</i></p>
]]></description><pubDate>Sat, 23 May 2026 23:05:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=48252481</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=48252481</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48252481</guid></item><item><title><![CDATA[New comment by phire in "Bun support is now limited and deprecated"]]></title><description><![CDATA[
<p>It's a bit harder to avoid windows than it is to avoid Bun.<p>More importantly, it's not the same thing at all. All the code in windows (at least until recently) was written by humans, understood by humans and reviewed by humans. And that code has stood the test of time, proven its value and stability in the wild, on billions of systems. The fact that the current maintainers haven't needed to understand or replace the code is some indication of the code's quality.<p>Almost none of Bun's rust code has been even seen by a human, and it's only about two weeks old.<p>I'm somewhat willing to accept vibe-coded code if it's either absolutely non-critical, well reviewed, or maybe in the long term if it's proven itself. But not two week old code.</p>
]]></description><pubDate>Sat, 23 May 2026 01:18:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=48243575</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=48243575</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48243575</guid></item><item><title><![CDATA[New comment by phire in "LLM Policy for Rust Compiler"]]></title><description><![CDATA[
<p>It's a pretty strict ban, with an exception.<p>That exception is experimental and somewhat limited; Only allows "well tested, high-quality" PRs on parts of the codebase that have a low probability of causing soundness issues, and it has a seperate review process with much higher standards.<p>And it requires the reviewer to agree to the use of LLMs ahead of time, before the PR is opened.<p>IMO, it has a high likelihood of degrading to a closed system, where some programmers with a good track record have little issue merging LLM generated PRs, while anyone without a reputation will struggle to even open an ai-assisted PR.</p>
]]></description><pubDate>Sat, 16 May 2026 10:18:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=48158778</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=48158778</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48158778</guid></item><item><title><![CDATA[New comment by phire in "Removing the modem and GPS from my 2024 RAV4 hybrid"]]></title><description><![CDATA[
<p>Yeah, I'm a little suspicious about that claim.<p>Bluetooth tethering is a thing, actually predates wifi tethering. Though it's not enabled unless you enable Personal Hotspot in your phone settings (and Android requires it to be enabled separately).<p>CarPlay complicates things, as it only uses bluetooth to pair, then it switches to using a wifi network (as bluetooth doesn't have anywhere near enough bandwidth). Maybe Apple automatically shares internet over that carplay connection?<p>I have no doubt that the car will use the internet connection if one is exposed, I just doubt it will be exposed automatically.</p>
]]></description><pubDate>Fri, 15 May 2026 04:00:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=48144400</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=48144400</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48144400</guid></item><item><title><![CDATA[New comment by phire in "GNU IFUNC is the real culprit behind CVE-2024-3094"]]></title><description><![CDATA[
<p>This is barking up the wrong tree.<p>Using IFUNC to patch sshd was kind of elegant, it achieved rootkit like behaviour with a pre-existing mechanism. And sure, it might be possible for a secure daemon like sshd to drop enough privileges that it could protect itself from a malicious dynamically linked library.<p>But IFUNC was not required, neither was systemd.  The game was lost as soon as the attacker had arbitrary code installed in a semi-common library. It doesn't have to get linked directly with sshd, it only needed to be linked into any program running as root, at least one time.<p>Most programs make zero effort to sandbox themselves, and as soon as one of those links with the malicious library, it could do anything. Like indirectly targeting sshd by patching its binary on disk (optionally hiding it with a rootkit), or using debug APIs to patch sshd in memory.<p>IFUNC, systemd, and the patched openssh are all irrelevant to the issue, that was simply the route this attacker took to leverage their foothold in libxz. There are thousands of potential routes the attacker could have taken, and we simply can't defend from all of them.</p>
]]></description><pubDate>Fri, 08 May 2026 02:59:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=48057980</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=48057980</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48057980</guid></item><item><title><![CDATA[New comment by phire in "Natural Language Autoencoders: Turning Claude's Thoughts into Text"]]></title><description><![CDATA[
<p>I think this question is easier to answer if you look at the inverse: "Could a model maliciously smuggle intentions through a roundtrip of compressed representation without them being human readable"<p>And skimming through the paper; the answer to this inverse is obviously yes. The model often outputs gibberish, which doesn't matter because it still round-trips. The fact that often lines up near a good english representation of the activation is simply because that's what compresses/roundtrips well.<p>So a malicious LLM/NLA pair could just use gibberish to conceal intentions. Or if it's been forced to avoid gibberish, it can conceal information with stenography.<p>And the experiment where they change "rabbit" to "mouse" in the explanation provides evidence that this might be happening. It was only successful 50% of the time, which might mean they failed to eliminate all "rabbitness" from the activation.<p>However, I suspect this is solvable with future work.<p>During training of the NLA, just munge the textural representation through a 3rd LLM: Have it randomly reorder and reword the explication into various different forms (use synonyms, different dialects), destroying any side-channels that aren't human readable.<p>The NLA would be forced to use human readable representations to get a successful round trip.</p>
]]></description><pubDate>Fri, 08 May 2026 00:45:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=48057048</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=48057048</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48057048</guid></item><item><title><![CDATA[New comment by phire in "Natural Language Autoencoders: Turning Claude's Thoughts into Text"]]></title><description><![CDATA[
<p>The NLA also hallucinates, so it's still not revealing the models actual "thoughts" of the model; The paper also points out that since the NLA is a  full LLM, it can make inferences that aren't actually in the activations.<p>But it's a useful approximation for auditing.</p>
]]></description><pubDate>Thu, 07 May 2026 23:49:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=48056633</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=48056633</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48056633</guid></item><item><title><![CDATA[New comment by phire in "Building the TD4 4-Bit CPU"]]></title><description><![CDATA[
<p>Because they are both well-known and really well documented in a way that's easy for beginners.</p>
]]></description><pubDate>Thu, 07 May 2026 21:44:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=48055517</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=48055517</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48055517</guid></item><item><title><![CDATA[New comment by phire in "The Hearts of the Super Nintendo (2024)"]]></title><description><![CDATA[
<p>Yeah, it might be about isolating the APU as much as possible from potential sources of noise. Not that they ever put optical isolators on the data lines between the APU and CPU, but just keeping them out of phase probably helped a lot.<p>Another bit of evidence for that: While they merged all the audio chips into a single S-APU chip, and both PPUs and the CPU into the 1CHIP, they never went the final step of merging the APU, PPU and CPU into a single chip. And they never shrunk the PCB to move the two chips closer.<p>------------<p>My other theory is that if the audio clock was derived from the video clock, then it would have a different sample rate on NSTC and PAL consoles; By giving it an independent crystal, they can make sure both models have the same audio sample rate.<p>It's probably a combination of many of these small factors prevented them from ever going to the effort of trying to make it work from a single crystal.</p>
]]></description><pubDate>Fri, 01 May 2026 09:40:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=47972816</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=47972816</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47972816</guid></item><item><title><![CDATA[New comment by phire in "The Hearts of the Super Nintendo (2024)"]]></title><description><![CDATA[
<p>I don't understand why Nintendo decided to give the APU a dedicated clock crystal.<p>Was it that important to have an exactly 32000 Hz sample rate?   
They could have used a divide-by-21 to get within 0.2%, which would have been more accurate than that ceramic resonator. Or keep the existing divider and run resample all the audio to 27.97 KHz, which IMO would have been acceptable.</p>
]]></description><pubDate>Fri, 01 May 2026 06:20:03 +0000</pubDate><link>https://news.ycombinator.com/item?id=47971765</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=47971765</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47971765</guid></item><item><title><![CDATA[New comment by phire in "XOR'ing a register with itself is the idiom for zeroing it out. Why not sub?"]]></title><description><![CDATA[
<p>Also, you probably spend much more energy moving the bits around the chip and out to RAM than you do on the actual calculation.</p>
]]></description><pubDate>Sat, 25 Apr 2026 22:27:14 +0000</pubDate><link>https://news.ycombinator.com/item?id=47905202</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=47905202</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47905202</guid></item><item><title><![CDATA[New comment by phire in "XOR'ing a register with itself is the idiom for zeroing it out. Why not sub?"]]></title><description><![CDATA[
<p>Thanks, I suspected there might be something from the minicomputer era.<p>I've only really looked at a single AM2900 implementation (and it was far from optimal). Guess I need to dig deeper at some point.<p><i>> The ONES operation forces all the carry chain to 1 (ignoring operand) (you can do a ONES+1 to get arithmetic 0, but why?)</i><p>Forcing all carries to 1 inverts the output.<p>If I'm understanding the ALU correctly, (the datasheet doesn't show that part) it only implements OR and XOR. When combined with the ability to invert both inputs, AND can be implemented as <i>!(!A OR !B)</i>, NAND is <i>(!A OR !B)</i> and so on.<p>Or maybe the ALU implements NOR and XNOR, and all the carry logic is physically inverted from what the documentation says.</p>
]]></description><pubDate>Wed, 22 Apr 2026 23:32:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=47870593</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=47870593</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47870593</guid></item><item><title><![CDATA[New comment by phire in "XOR'ing a register with itself is the idiom for zeroing it out. Why not sub?"]]></title><description><![CDATA[
<p>I'm not actually aware of any CPUs that preform a XOR faster than a SUB. And more importantly, they have identical timings on the 8086, which is where this pattern comes from.</p>
]]></description><pubDate>Wed, 22 Apr 2026 07:53:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=47860455</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=47860455</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47860455</guid></item><item><title><![CDATA[New comment by phire in "Why Japan has such good railways"]]></title><description><![CDATA[
<p>I agree that if you put a high-speed line between Auckland and Wellington, and get the travel time down to 3-4 hours, people would use it. It would actually be faster than going to the airport for central Auckland, or anything further north.<p>But high speed lines are expensive, and NZ just doesn't have anywhere near the population density to justify it.<p>As for night trains, I'm pretty sure they can only exist where they are bridging multiple viable day train routes. Which is why that huge gap between Hamilton and Palmerston North is an issue.<p>And the route might actually be a bit short for a night train. If they electrified the entire distance (instead of using a diesel the whole way despite the fact 80% of the route is electrified) and did some improvements, they could probably get it down to an 8 hour trip.<p><i>> What about options for those living up north?</i><p>TBH, I'm not a fan of Auckland and don't really know what's going on with local public transport.</p>
]]></description><pubDate>Mon, 20 Apr 2026 01:55:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=47829508</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=47829508</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47829508</guid></item><item><title><![CDATA[New comment by phire in "Why Japan has such good railways"]]></title><description><![CDATA[
<p>The railway services NZ are trying to bring back are regional commuter services. Auckland to Hamilton (now in operation); Auckland to Tauranga; Wellington to Palmerston North (Capital Connection, has been in operation for 35 years, about to be upgraded to battery-electric trains, since only half the route is electrified).<p>And also the vague idea of local rail service around Christchurch (interestingly, a private company bought the old DMUs from Auckland's local fleet after electrification and are just starting to run special trains for Rugby games).<p>Part of the problem is that there is only really only three metro areas in New Zealand. Auckland, Wellington and Christchurch. Everything else isn't really large enough to provide enough demand for a proper intercity route. And Christchurch isn't even on the same island, so you can't have a proper intercity train with the ferry getting in the way.<p>So the only potentially viable intercity route is Auckland to Wellington.<p>And apart from Hamilton and Palmerston North, (which already have commuter trains) there is absolutely nothing in the middle. The same distance in Europe or the US's eastern corridor would service 4-6 decently sized metro areas, and provide plenty of extra demand.<p>There just isn't enough potential demand to put a high-speed rail line through there. And without the high-speed rail, it's a 10 hour train trip that has zero chance of competing with a 1 hour plane ride.<p>Christchurch to Wellington is even worse. 6 hour train ride, at least an hour waiting for the ferry, 3.5 hour ferry ride. The plane does it in at little as 25 min in the air, there isn't enough time to reach cruising altitude. There is a reason why the route used to be serviced by an overnight ferry.<p><i>> And to be fair, looks like you can more or less cross the country, as long as you don't plan to get all the way to Invercargill</i><p>Yeah... but those aren't "intercity trains". They are scenic tourist trains that just so happen to be running along old intercity routes. Not bad as a tourism experience, but overpriced and not optimised for transportation needs.<p>The fact that you can't book both the Interislander ferry and costal pacific on the same website is very telling. They are literally run by the same company.<p>----------------------<p>If you are serious about the Christchurch to Invercargill, there is now a private company offering the occasional weekend trip: <a href="https://www.mainlander.co.nz/train-trips/the-mainlander-rail-stay-packages" rel="nofollow">https://www.mainlander.co.nz/train-trips/the-mainlander-rail...</a><p>Same company that's providing the Rugby special trains, but this is using the old Capital Connection rolling stock. The train usually runs day trips up to Arthur's pass for cruise ships, but when there is a gap in that schedule they are running these Christchurch to Dunedin and Christchurch to Invercargill excursions.<p>Even more touristy than great journeys.</p>
]]></description><pubDate>Sun, 19 Apr 2026 05:45:45 +0000</pubDate><link>https://news.ycombinator.com/item?id=47822083</link><dc:creator>phire</dc:creator><comments>https://news.ycombinator.com/item?id=47822083</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47822083</guid></item></channel></rss>