Hacker News: assbuttbuttass

New comment by assbuttbuttass in "Since Linux 6.9, LUKS suspend stopped wiping disk-encryption keys from memory"

assbuttbuttass — Fri, 03 Jul 2026 12:59:06 +0000

> I must admit I'm a little surprised how many people seem to disable secure boot.

To me, secure boot is the setting that I need to remember to turn off before installing the OS, but I would be willing to be convinced otherwise

New comment by assbuttbuttass in "Go: Support for Generic Methods"

assbuttbuttass — Thu, 28 May 2026 12:52:57 +0000

Hmm I wasn't familiar with join, but it looks like you still need join + fmap for the construction? I believe fmap would also need a generic method

New comment by assbuttbuttass in "Go: Support for Generic Methods"

assbuttbuttass — Thu, 28 May 2026 00:21:09 +0000

It's (sadly) still not possible to express monads with this change, since generic methods can't implement interfaces. You'd probably want something like:

    type Monad[T any] interface {
        Bind[U any](func(T) Monad[U])
    }

However this requires the Bind method to be generic, which still isn't allowed in an interface

New comment by assbuttbuttass in "What color is your function? (2015)"

assbuttbuttass — Tue, 26 May 2026 19:07:37 +0000

> Why would there be paranoia when writing blocking code with async?

In languages like JavaScript, you have to be careful to avoid blocking the event loop, and use something like worker threads for CPU-intensive tasks. Otherwise you will end up with long tail latencies. In Go, the runtime automatically manages this and can suspend and resume long-running goroutines.

> naively accessing a global value can lead to race conditions

Fair point that the language doesn't automatically catch this, but that's what a mutex is for. In return you get actual parallelism that can use all your CPU cores

New comment by assbuttbuttass in "What color is your function? (2015)"

assbuttbuttass — Tue, 26 May 2026 17:34:19 +0000

> Your entire codebase is now a surface area that is at risk of being blocked

The point of goroutines is that they can freely block when needed. It's not like async where you have to be paranoid at every moment about writing blocking code

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

assbuttbuttass — Thu, 21 May 2026 21:00:19 +0000

Interesting, thanks

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

assbuttbuttass — Thu, 21 May 2026 15:40:07 +0000

Also C++/Java static initialization, C# static constructors, or Rust global variable initialization, ...

Most languages have this feature Afaik

New comment by assbuttbuttass in "Why are there both TMP and TEMP environment variables? (2015)"

assbuttbuttass — Sat, 02 May 2026 13:56:35 +0000

I use lowercase for my personal environment variables. It works well since most programs only depend on variables in all caps. Hadn't thought of using MY_

New comment by assbuttbuttass in "Helix: A post-modern text editor"

assbuttbuttass — Sat, 07 Mar 2026 17:30:32 +0000

I really want to like Helix, but I wish the developers paid more attention to performance, or were more receptive to outside contributions. Helix can really chug, even on small files, and the perception in the community seems to be "it's written in Rust so therefore it's blazingly fast :rocket-ship-emoji:"

New comment by assbuttbuttass in "Why Go Can't Try"

assbuttbuttass — Mon, 02 Mar 2026 20:51:38 +0000

Which aspects of Rust syntax are adapted from ML? Semantics sure, but to me the syntax seems a lot more similar to C++ (e.g. semicolons, type parameters using <>, etc.)

New comment by assbuttbuttass in "Pentagon Adopts Incel-Speak"

assbuttbuttass — Sun, 01 Mar 2026 14:48:59 +0000

The incels have grown up and now work at the Pentagon

New comment by assbuttbuttass in "LLMs as the new high level language"

assbuttbuttass — Sun, 08 Feb 2026 15:10:31 +0000

This still doesn't help when you update your compiler to use a newer model

New comment by assbuttbuttass in "Guix System First Impressions as a Nix User"

assbuttbuttass — Sun, 01 Feb 2026 13:28:28 +0000

Just a personal anecdote, but the errors from Guix are terrible. I had to reinstall because I couldn't figure out the scheme errors for my system config

New comment by assbuttbuttass in "Guix System First Impressions as a Nix User"

assbuttbuttass — Sun, 01 Feb 2026 13:25:11 +0000

> the thing I hate by far the most in NixOS is .. nix

nix has a pretty steep learning curve, sure

> scheme? Aka Lisp? Seriously???

No nix, no scheme, got it. I wonder which language you would use?

> YAML files exist for a reason.

LMAO

New comment by assbuttbuttass in "Claude Code's GitHub page auto closes issues after 60 days"

assbuttbuttass — Sat, 31 Jan 2026 15:11:01 +0000

Yeah, it only checks whether the last bot comment is older than 30 days, completely ignoring any human comment

    if (botCommentDate < oneMonthAgo) {
        // Close the issue - it's been stale for 60+ days

Hard to imagine how this got past code review...

https://github.com/anthropics/claude-code/blob/5e3e9408feea9...

New comment by assbuttbuttass in "Finding and Fixing a 50k Goroutine Leak That Nearly Killed Production"

assbuttbuttass — Sat, 17 Jan 2026 14:02:21 +0000

> Writers kept sending to sub.messages. The channel grew. Memory grew.

Channels are buffered in Go, they will not grow unbounded.

> Tickers Are Not Garbage Collected

It used to be necessary in older versions to call ticker.Stop(), but in recent versions it's no longer necessary.

    // Start goroutines
    go s.pumpMessages(ctx, sub)
    go s.heartbeat(ctx, sub)
    
    // Monitor the connection
    go s.monitorConnection(ctx, sub)

The "fixed" code is still using the fire-and-forget pattern for goroutines which encourages this kind of leak. Go makes it easy to add concurrency on the caller side, so it's usually better to write blocking functions that clean up all their goroutines before returning.

In general this article screams AI with most of the conclusions being hallucinated. Goroutine leaks are real, but it's hard to trust any of the article's conclusions

New comment by assbuttbuttass in "Investigating and fixing a nasty clone bug"

assbuttbuttass — Tue, 06 Jan 2026 10:31:19 +0000

I fixed an almost identical bug at work a few months ago: an internal service was calling some network device, and would only fail for IPv6-only devices. Turns out it was trying IPv4 first, and then when it failed, it would retry the request with IPv6, but the request body was already consumed so the retry failed with a cryptic error

New comment by assbuttbuttass in "Can I start using Wayland in 2026?"

assbuttbuttass — Sun, 04 Jan 2026 16:26:50 +0000

Screen sharing works in Zoom now, you'll have to find a new cherry-picked example

ProjectM – Cross-Platform Music Visualization Library

assbuttbuttass — Sat, 20 Dec 2025 16:20:32 +0000

Article URL: https://github.com/projectM-visualizer/projectm

Comments URL: https://news.ycombinator.com/item?id=46337235

Points: 2

# Comments: 0

New comment by assbuttbuttass in "Avoid UUID Version 4 Primary Keys in Postgres"

assbuttbuttass — Mon, 15 Dec 2025 15:13:12 +0000

At least for the Spanner DB, it's good to have a randomly-distributed primary key since it allows better sharding of the data and avoids "hot shards" when doing a lot of inserts. UUIDv4 is the typical solution, although a bit-reversed incrementing integer would work too

https://cloud.google.com/blog/products/databases/announcing-...