Hacker News: ghusbands

New comment by ghusbands in "Servo is now available on crates.io"

ghusbands — Tue, 14 Apr 2026 07:38:43 +0000

I wonder why most of the "g" characters are cropped.

New comment by ghusbands in "Creating the Futurescape for the Fifth Element (2019)"

ghusbands — Sun, 12 Apr 2026 20:04:11 +0000

True, but that’s using “effects” in a broader sense than people seem to mean here. The discussion seems to be about the visible effects the audience experiences as effects, and whether those age well, not invisible digital cleanup, compositing, or set extension.

New comment by ghusbands in "Issue: Claude Code is unusable for complex engineering tasks with Feb updates"

ghusbands — Tue, 07 Apr 2026 14:55:27 +0000

Even with high effort, the adaptive thinking can just choose no thinking. See bcherny's post they were replying to: https://news.ycombinator.com/item?id=47668520

New comment by ghusbands in "A Recipe for Steganogravy"

ghusbands — Fri, 03 Apr 2026 18:14:30 +0000

Steganography is (hopefully invisibly) hiding information in an image, not creating an image that so obviously encodes information.

New comment by ghusbands in "The future of version control"

ghusbands — Mon, 23 Mar 2026 16:09:43 +0000

A common misconception is that git works with diffs as a primary representation of patches, and that's the implied reading of "stores diffs". Yes, git uses diffs as an optimisation for storage but the underlying model is always that of storing whole trees (DAGs of trees, even), so someone talking about it storing diffs is missing something fundamental. Even renames are rederived regularly and not stored as such.

However, context would matter and wasn't provided - without it, we're just guessing.

New comment by ghusbands in "Zero-day CSS: CVE-2026-2441 exists in the wild"

ghusbands — Thu, 19 Feb 2026 07:19:58 +0000

Yes, once you use 'unsafe' to bypass the safety model, you don't get safety.

Edit: If you reply with a reply, rather than edits, you don't get such confusion.

New comment by ghusbands in "The first new compass since 1936"

ghusbands — Sun, 18 Jan 2026 17:32:01 +0000

The comments on this site (HN) may be what most people are talking about. Youtube comments are too easily censored, so they probably will never manage to stick around.

New comment by ghusbands in "OLED, Not for Me"

ghusbands — Sat, 10 Jan 2026 16:22:31 +0000

I would probably see text quality issues on that setup. It depends on how far away the monitor is. PPI on phone screens tends to be much higher than PPI on laptops which tends to be higher than PPI on monitors, because each is typically used at a different distance.

If you're not using text around 9 pixels tall, as in the article, you're probably going to be okay. On a 27 inch screen at a typical office screen distance, I'd probably want 6k, but 4k is pretty good and 1080p is terrible.

New comment by ghusbands in "OLED, Not for Me"

ghusbands — Sat, 10 Jan 2026 16:04:49 +0000

In my experience, it seems to. My astigmatism (or other eye stuff) seems to move different colours different amounts, leading to wider RGB pixels and making things like Cleartype so much worse. So people were enjoying Cleartype and I was hating the obvious colour-changes and fringes that somehow they weren't seeing. I assume some people are lucky enough to have aberrations that actually make cleartype more pleasant.

New comment by ghusbands in "OLED, Not for Me"

ghusbands — Sat, 10 Jan 2026 14:17:03 +0000

It's not like the Cleartype tuner actually does what the pages claim - you can go through and use the magnifier to choose the grayscale-only outcomes and still see Windows doing RGB stripe cleartype throughout. People literally have to install third-party tools like MacType or GDI-PlusPlus to get solid font rendering. So blaming users for using it wrong (especially when they're not even on Windows) is odd.

Also, many people can see and are bothered by particular non-rectangular pixel layouts - it doesn't require doing odd things.

New comment by ghusbands in "Samsung Galaxy Z TriFold hands-on"

ghusbands — Sat, 10 Jan 2026 14:04:43 +0000

I had the same experience (Z Fold 4, screen protector at hinge broke at the five month mark - I replaced it with a third-party one to avoid a long repair period and another such breakage - the screen itself is now faulty at just beyond the two year mark).

If anyone were to buy a modern Samsung folding phone, I'd suggest you make sure you get the two-year coverage for the screen and assume it will break soon after that, so treat it like you're going to buy one every 2-3 years. But remember that warranty repairs sometimes involve sending the phone away for weeks, and Android's phone transfer story is still incomplete. That's merely my experience, of course.

New comment by ghusbands in "The first new compass since 1936"

ghusbands — Wed, 07 Jan 2026 14:11:17 +0000

The inhibition of movement via eddy currents works best while the needle is moving fast, so you can still end up with smaller oscillations for a while - the apparent jump-cut to a stationary needle could be hiding that.

It's far easier to just use a compass with a needle brake - manually dampen the oscillation using the brake (and let go to ensure you aren't holding an incorrect reading) and you get a reading quickly.

New comment by ghusbands in "Show HN: One clean, developer-focused page for every Unicode symbol"

ghusbands — Tue, 30 Dec 2025 19:57:48 +0000

Your site still says "HOW TO ADD ALMOST EQUAL TO IN HTML? Use an HTML entity, a decimal code, or a hex code."

That is incorrect. As you say, you should just write the character in your HTML and ensure it's served with the correct encoding. If it's just for legacy cases, debugging or such, say so on the site.

New comment by ghusbands in "Periodic Spaces"

ghusbands — Tue, 09 Dec 2025 10:58:11 +0000

A simpler way: You can avoid sampling neighbours by clamping the ray-march step so it never moves further than the current cell's boundary (plus a tiny epsilon). That way, you only cross into adjacent cells at the edge and avoid the 8 to maybe 26 extra SDF samples. (This only works if the geometry is entirely contained within each cell.)

New comment by ghusbands in "Time travel? Or, just clever technology"

ghusbands — Sun, 28 Sep 2025 18:33:31 +0000

> This sort of stuff is actually doable just with just video chat and OBS.

If what each person is hearing is 100-400ms delayed from what each person is producing, how can they possibly mutually react or even get their music in time? If B plays in time with what they hear from C, C hears what B did 200-800ms later - that's far too much and will sound terrible.

Jamming would seem to require incredibly low latency audio just for the rhythm to work between two performers.

New comment by ghusbands in "EPA tells some scientists to stop publishing studies"

ghusbands — Sun, 28 Sep 2025 18:24:59 +0000

You could post that comment on every article. (Please don't.)

New comment by ghusbands in "A tiny (1000 lines), fastish, embeddable scripting language can be AOT compiled"

ghusbands — Sat, 30 Aug 2025 10:12:34 +0000

> garbage collection, I just link the Boehm GC. Not ideal, but good enough

It's worth noting that on 32-bit, the Boehm GC can have consistent issues [1] [2] [3] that make it worth avoiding for anything long-running. The Mono team implemented their own GC due to this. If a runtime is aiming to be useful on such systems, it may be worth implementing or using a less conservative GC.

[1] https://en.wikipedia.org/wiki/Mono_%28software%29#Garbage_co...

[2] https://news.ycombinator.com/item?id=3576396

[3] https://stackoverflow.com/questions/8152374/

New comment by ghusbands in "Learning from the Amiga API/ABI"

ghusbands — Mon, 02 Jun 2025 10:00:24 +0000

Try to notice how you're avoiding answering the points I raised and jumping at any chance to defend the Amiga (it was only 4-channel 8-bit built in and nobody achieved 14-bit sound before 1991). The Amiga vs X wars were decades ago at this point - you could just let it go.

New comment by ghusbands in "Learning from the Amiga API/ABI"

ghusbands — Sun, 01 Jun 2025 22:22:01 +0000

I don't think there's intentional dishonesty in it - the author is just biased to seeing everything Amiga very positively.

New comment by ghusbands in "Learning from the Amiga API/ABI"

ghusbands — Sun, 01 Jun 2025 22:19:07 +0000

Stereo 14-bit sound didn't really happen until the 1990s and needs quite a lot of CPU time and careful hacking, as Amiga sound chips are 8-bit, 4-channel. 4096 colors via weird hold-and-modify modes was never useful outside of demos and vanishingly few games. Nobody used 640x400 because interlacing was far too flickery, and such resolutions certainly didn't support 4096 colors.

The Amiga was ahead of its time in many ways, and the pre-emptive multitasking was fantastic, but claiming it was some paragon doesn't help anyone. If you wanted a fun home machine attached to a TV, it was great. Even a fun home machine attached to a monitor. If you wanted a business machine with a monitor, it wasn't the safest or best choice, if only due to a lack of software.