Compiling Firefox on NetBSD (dynamically) takes longer than compiling the kernel, maybe even longer than compiling an entire base system. It's been a long time since I tried it but it just took far too long so I lost interest. Granted, the computers I use have limited resources. Anyway, I gave up on graphical browsers many years ago. There are many programs I can compile statically because I prefer smaller software.^1 For example, the text-only browser, the TCP clients, the forward proxy, tmux, tinysshd, nvi, lua, stunnel, djbdns, daemontools, clockspeed, openssl, bssl, ffmpeg and various other programs I use are all static binaries. I also prefer crunched binaries on BSD to save space. These are static.

Whether a program can be compiled statically is a factor in whether I choose to use it. That effectively screens out many large programs that have numerous dependencies because compiling them statically often becomes too much hassle and the binaries are too large. For example, I compiled dnsdist statically using musl. Of course, "large" is subjective. I consider an 11M C program to be large but some HN commenters using memory-safe languages might think 11M is nothing.

1. Some have dependencies other than libc.