Hacker News: 63stack

New comment by 63stack in "Can we have the day off?"

63stack — Thu, 28 May 2026 08:46:13 +0000

"the market" is literally the arena of competition, it's not a surprise it's more competitive than ever

New comment by 63stack in "Migrating from Go to Rust"

63stack — Wed, 27 May 2026 10:17:50 +0000

I feel like we are talking past each other, because you ignored the whole part about "it is already tied to an env var, and it would be still tied to an env var" that you would only enable on demand, so who cares if it's a hefty operation? Also what about other languages that capture stacktraces all the time with exceptions, or scripting languages with type errors, where you can't even turn it off? Rust is somehow different?

It is a specific problem, so what? You see that you are sending 500 from an axum handler, and you are logging "serde deserialization error: line 4 invalid", wouldn't it be nice to see where that came from, without instrumenting all the places you are deserializing something?

New comment by 63stack in "Migrating from Go to Rust"

63stack — Wed, 27 May 2026 07:52:57 +0000

Ideally (in my ideal world), it would be Result that holds the backtrace. The value is that I don't know up front which method call is going to cause an error that is hard to track down, which is why I don't see how "instrument your calls with backtrace yourself" helps. It requires that I already have some idea about the execution path, otherwise I don't know where to put the backtrace instrumentation.

Since Backtrace::capture() is already tied to an env var, we could have the backtrace on Result without affecting performance, since you would only enable it for debugging. This would allow you to eg. easily track down a situation where you see in your prod logs that you are encountering a lot of "validation error: string is too long" but you can't tell where it is coming from. Flip the env var, redeploy the application, read the backtrace, turn off the env var, fix the problem.

New comment by 63stack in "Migrating from Go to Rust"

63stack — Tue, 26 May 2026 11:08:31 +0000

I see a very opinionated explanation, not a "this is why the language does not" explanation.

>Stack traces are only useful for errors that indicate a bug in the program, i.e. something a programmers has to respond to. It's not useful for the vast class of bugs that are a result of wrong input, wrong external state, or infrastructure issues.

This is a personal opinion, not something you can declare as the objective truth. There is a lot of value in seeing what path the program took before it encountered a eg. validation error.

>but there are cases where an error coming from a library are truly, actually unexpected, so both `anyhow` and `thiserror` do provide support for attaching a stack trace in those situations.

This is wrong because it's up to the library to attach the stacktrace, not the userland code using the library, so saying "you can get them if you want them" is not true. If the author of the library did not decide to attach the stacktrace, your only option is wrapping it yourself, which you can only do if you already know up front all the paths that can fail. Also, you are not supposed to expose errors from a library with anyhow, they are only for application/top level code.

New comment by 63stack in "Migrating from Go to Rust"

63stack — Mon, 25 May 2026 13:14:57 +0000

See? You get people explaining to you that you actually don't want a stack trace because xyz.

New comment by 63stack in "Migrating from Go to Rust"

63stack — Mon, 25 May 2026 07:28:49 +0000

Any time I mention "but I would like stacktraces with my errors" I get told I'm doing it wrong.

New comment by 63stack in "Python 3.15: features that didn't make the headlines"

63stack — Thu, 21 May 2026 20:33:04 +0000

100k lines is huge, I don't know what these jokers are on

New comment by 63stack in "GitHub is investigating unauthorized access to their internal repositories"

63stack — Wed, 20 May 2026 06:51:03 +0000

I'd say northwest

New comment by 63stack in "Remove-AI-Watermarks – CLI and library for removing AI watermarks from images"

63stack — Tue, 19 May 2026 23:15:12 +0000

Nobody said that?

New comment by 63stack in "Toxicity on Social Media"

63stack — Tue, 12 May 2026 10:52:25 +0000

This is my question as well, especially about the "community check". How will it be ensured that the "community check" is not going to be dominated by bots pushing an agenda? How is that different from "just another comment section hidden behind a green button"?

New comment by 63stack in "Postmortem: TanStack NPM supply-chain compromise"

63stack — Tue, 12 May 2026 08:05:21 +0000

The last time I looked at this, using ignore-scripts = true with npm results in "npm run xyz" getting blocked as well, is that still the case?

New comment by 63stack in "Hardware Attestation as Monopoly Enabler"

63stack — Mon, 11 May 2026 14:42:29 +0000

I don't see why we couldn't have both better education around this, and the freedom to opt out of surveillance

New comment by 63stack in "Mythos Finds a Curl Vulnerability"

63stack — Mon, 11 May 2026 11:52:01 +0000

I'm pretty sure mythos is just a new unreleased version of Opus + marketing + a different system prompt.

New comment by 63stack in "Hardware Attestation as Monopoly Enabler"

63stack — Mon, 11 May 2026 11:18:56 +0000

And one of the threat models that police use in the US is tracking women suspected of going for abortions through the use of road cameras, and other surveillance methods.

Once you have the attestation in place you have no guarantee who is going to get access to data like what apps are present on your device, and there will be nothing you can do to stop it.

Meanwhile, we could educate people against common scams.

How is this not just trading one smaller bad for a bigger bad? Why is this touted as an improvement?

New comment by 63stack in "Podman rootless containers and the Copy Fail exploit"

63stack — Fri, 08 May 2026 22:33:14 +0000

There is also net.ipv4.ip_unprivileged_port_start

New comment by 63stack in "Programming Still Sucks"

63stack — Thu, 07 May 2026 08:42:57 +0000

The first 3 hits on any search engine weren't relevant?

New comment by 63stack in "The fun has been optimized out of the Internet"

63stack — Tue, 05 May 2026 22:00:11 +0000

But nobody said that apart from you?

New comment by 63stack in "DeepClaude – Claude Code agent loop with DeepSeek V4 Pro"

63stack — Mon, 04 May 2026 11:18:27 +0000

The established culture on a lot of projects is that you open an issue, and then you have to keep pinging it every week otherwise the stale bot closes it with "this issue is stale, closing, but your contribution is very important to us".

It's crap either way.

New comment by 63stack in "DeepClaude – Claude Code agent loop with DeepSeek V4 Pro"

Hacker News: 63stack

New comment by 63stack in "Can we have the day off?"

New comment by 63stack in "Migrating from Go to Rust"

New comment by 63stack in "Migrating from Go to Rust"

New comment by 63stack in "Migrating from Go to Rust"

New comment by 63stack in "Migrating from Go to Rust"

New comment by 63stack in "Migrating from Go to Rust"

New comment by 63stack in "Python 3.15: features that didn't make the headlines"

New comment by 63stack in "GitHub is investigating unauthorized access to their internal repositories"

New comment by 63stack in "Remove-AI-Watermarks – CLI and library for removing AI watermarks from images"

New comment by 63stack in "Toxicity on Social Media"

New comment by 63stack in "Postmortem: TanStack NPM supply-chain compromise"

New comment by 63stack in "Hardware Attestation as Monopoly Enabler"

New comment by 63stack in "Mythos Finds a Curl Vulnerability"

New comment by 63stack in "Hardware Attestation as Monopoly Enabler"

New comment by 63stack in "Podman rootless containers and the Copy Fail exploit"

New comment by 63stack in "Programming Still Sucks"

New comment by 63stack in "The fun has been optimized out of the Internet"

New comment by 63stack in "DeepClaude – Claude Code agent loop with DeepSeek V4 Pro"

New comment by 63stack in "DeepClaude – Claude Code agent loop with DeepSeek V4 Pro"

New comment by 63stack in "DeepSeek V4 – almost on the frontier"