Hacker News: correct_horse

New comment by correct_horse in ".NET (OK, C#) finally gets union types"

correct_horse — Sat, 23 May 2026 21:40:05 +0000

Haskell, OCaml, Erlang lead the way and Rust, Zig and Go get all the mindshare. I feel like its a common pattern for more experimental languages to pioneer features and other languages to copy the features and bring them to a C style syntax that the majority of devs are familiar with.

New comment by correct_horse in "Claws are now a new layer on top of LLM agents"

correct_horse — Sun, 22 Feb 2026 05:30:49 +0000

Mac minis are particularly suited to running AI models because they can have a pretty good quantity of RAM (64GB) assigned to the GPU at a reasonable price compared to Nvidia offerings. Mac minis have unified memory which means it can be split between CPU and GPU in a configurable way. I think apple didn’t price mac minis with AI stuff in mind, so they end up being good value.

New comment by correct_horse in "When if is just a function"

correct_horse — Sat, 18 Oct 2025 09:54:27 +0000

Just here to point out that the actor’s name is Bob Odenkirk not Odendirk. In a statically typed language this would be an error at compile time not hacker news comment time.

New comment by correct_horse in "DARPA project for automated translation from C to Rust (2024)"

correct_horse — Fri, 03 Oct 2025 06:06:07 +0000

Safe rust can leak memory, so a better question is "If someone wrote C code that made an invalid read or write, would rust do the same?" I can't answer the question, but ideally if the translated was safe, it would somehow eliminate the bug while keeping the desired behavior. That scenario seems a bit too optimistic though, so probably it'll have an unsafe block that does the invalid read/write and a human can come in and add runtime checks or refactor it further.

New comment by correct_horse in "I only use Google Sheets"

correct_horse — Wed, 01 Oct 2025 23:25:06 +0000

for when not to use a spreadsheet, see https://news.ycombinator.com/item?id=34968457 tl;dr when it involves automated processes

New comment by correct_horse in "A WebGL game where you deliver messages on a tiny planet"

correct_horse — Sun, 28 Sep 2025 01:10:15 +0000

I also got nausea from this game and I've never gotten nausea from a video game before. The style is amazing, but the camera controls need some work. I don't know what the camera needs besides a more standard mouse control.

New comment by correct_horse in "Systemd can be a cause of restrictions on daemons"

correct_horse — Sat, 20 Sep 2025 16:38:04 +0000

I think I agree. I’m curious what software would be in places 2-10. If we’re talking about HN, maybe excel/google sheets? Maybe C++? Recent versions of macOS always seem to get hate, but I think macOS is in a different category.

New comment by correct_horse in "Safepoints and Fil-C"

correct_horse — Fri, 19 Sep 2025 19:15:40 +0000

Fil-C seems interesting, and I didn’t understand the details of how multi-threaded garbage collectors worked before reading it (I still don’t but I’m closer!). The tradeoff between a compacting garbage collector (Java) vs what you can bolt on to C without forking LLVM is particularly interesting.

New comment by correct_horse in "Impressions from a first-time Mac user"

correct_horse — Mon, 11 Apr 2022 20:29:00 +0000

> Disable spotlight for everything except what you want to use it for

My friend's mac would "take off" (fan spun up crazy fast) after every boot/login and I disabled full-text search of documents to fix it. There was probably a weird, maybe not-to-spec pdf/docx on the filesystem that spotlight couldn't parse and got stuck. Kinda dumb that it would waste a 100% usage on one CPU core for a couple minutes every boot though.

New comment by correct_horse in "Improving first impressions on Signal"

correct_horse — Mon, 01 Nov 2021 22:28:15 +0000

Do you think an eventually open style spam filter could work? One where the implemntation is released say 2 years after it was first written (including modifications)

New comment by correct_horse in "Overly analytical guide to escorting"

correct_horse — Wed, 20 Oct 2021 01:54:29 +0000

The funniest part of this article (in the context of being posted on HN) is that the author separately mentions engineer and software engineer in her list of client professions. That settles it - normal people think they're different.

New comment by correct_horse in "Call of Duty Adds Kernel Level Driver for Anti-Cheat"

correct_horse — Thu, 14 Oct 2021 04:33:24 +0000

Cloud gaming would lose practical consumers' control much more than Netflix did. At the very least, one could always point a video camera at the screen to copy video (suppose for one's own records). But with games, there is no chance to do anything like this. Netflix had an interactive Black Mirror episode called Bandersnatch(2018) that I speculated at the time was appealing from a business perspective because copying interactive content is much harder than straight video.

New comment by correct_horse in "Joe Rogan, confined to Spotify, is losing influence"

correct_horse — Wed, 25 Aug 2021 20:14:47 +0000

Memory hole is from 1984. It is where they put papers to be incinerated and forgotten. Spotify removed a few Joe Rogan episodes IIRC.

New comment by correct_horse in "How Actors Work Internally in Swift"

correct_horse — Sat, 14 Aug 2021 02:15:08 +0000

I'm not sure if the author of this blog visits hacker news to read this, but your code blocks are unreadable without javascript. They're black highlighted black text.

New comment by correct_horse in "How Actors Work Internally in Swift"

correct_horse — Sat, 14 Aug 2021 02:09:49 +0000

Unsurprising, since the creator of rust, Graydon Hoare now works for apple on swift[0] in "a non-leadership position".

[0] https://old.reddit.com/r/rust/comments/7qels2/i_wonder_why_g...

New comment by correct_horse in "GNU nano is my editor of choice"

correct_horse — Fri, 13 Aug 2021 22:27:43 +0000

Most non-copyleft (permissive free software and proprietary software) tries to stay as far away as possible from the GPLv3 license. Because of this, macOS ships gnu nano 2.0.6 whereas the latest is 5.8. FreeBSD doesn't even have nano installed by default.

New comment by correct_horse in "The journey to controlling external monitors on M1 Macs"

correct_horse — Fri, 30 Jul 2021 23:51:53 +0000

Display Data Channel generally doesn't work through dongles. I'm not really sure how usb-c dongles work (block diagram, etc.), so I don't know why this is the case.

New comment by correct_horse in "Is Rust Used Safely by Software Developers?"

correct_horse — Fri, 16 Jul 2021 22:06:46 +0000

I like rust, but don't use it for embedded. Here's a blog I read on how to make GPIO access safe https://www.ecorax.net/macro-bunker-2/.

In that article, they have three goals: verify that the pin is correctly configured, use atomic reads and writes, make sure only one thread (including interrupts) can write to a pin at a time.

Spoiler alert, the way they avoid interrupts screwing everything up is with `cortex_m::interrupt::free(|_| {/*read/write pin*/})`, which executes the passed closure in an interrupt-free context. The author's solution isn't atomic, but the borrow checker and the fact that they target single threaded MCU means no one else can be writing to the port at the same time.

New comment by correct_horse in "Writing a SQLite clone from scratch in C (2017)"

correct_horse — Mon, 05 Jul 2021 00:10:50 +0000

I haven't found a good solution to a fallible constructor without exceptions. You might want this if you have a C++ wrapper around a file or some other OS primitive. I would love some allowance for constructors returning std::optional. One problem with this is that child classes' constructors would have to return optional too or else they might throw an exception when they call optional::value.

New comment by correct_horse in "Reverse Engineering Bumble’s API (2020)"

correct_horse — Sat, 12 Jun 2021 19:45:29 +0000

The way tinder dealt with it, as I understand, is by dividing the world into a coarse grid. Users were placed in the grid, then distances calculated from the centers of the grid squares. Basically rounding of position, not rounding of distance. They tried rounding distance (calculated from exact positions) but one can exploit that by exploring for the boundary where the distance changes from one integer to another.