Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Small Programming Tricks(will-keleher.com ↗)
    74comments
  2. Dream-RSI: Recursive Self-Improvement through Evolving Worlds(arxiv.org ↗)
    33comments
  3. Mistral X Mozilla: Private, Multilingual AI Browsing(mistral.ai ↗)
    138comments
  4. Introducing System One Models and Jev(typesafe.ai ↗)
    461comments
  5. Tell the speakers that you liked their talks(ohhelloana.blog ↗)
    33comments
  6. Claude Cowork and chat are now one Claude(claude.com ↗)
    81comments
  7. Show HN: An e-ink frame that hears birds and draws them as 1800s illustrations(github.com/arnegiacomo ↗)
    223comments
  8. How big are factorials?(thegreenplace.net ↗)
    14comments
  9. Apple Reference Image: A New Approach for Verified Photography(security.apple.com ↗)
    294comments
  10. Can we stop with the uptime percentages?(jim-nielsen.com ↗)
    58comments
  11. Hackers Got Inside a Flock Camera(wired.com ↗)
    144comments
  12. The Google Play app review process now regularly takes longer than a week(gultsch.social ↗)
    257comments
  13. The DeepMind Institute(deepmind.com ↗)
    4comments
  14. This Code Is CRAP (2011)(googleblog.com ↗)
    39comments
  15. Show HN: How Stale Is Your AI? Release age and training cutoff for 20 models(stale.jock.pl ↗)
    26comments
  16. Scaling Golang CI by Replacing actions/setup-go(cloudx.ai ↗)
    7comments
  17. An update on Wayback Machine access(blog.archive.org ↗)
    339comments
  18. Kyber (YC W23) Is Hiring a Forward Deployed Engineer(ycombinator.com ↗)
    discuss
  19. Original Sony PlayStation 2 security chip 'broken wide open' after 26 years(tomshardware.com ↗)
    58comments
  20. Prisma's pgbouncer=true on Supabase made every query 4 round-trips (postmortem)(simbastack.com ↗)
    4comments
  21. Measuring Gauss-Seidel loop-carried dependency and fixing it via loop unrolling(loiseaujc.github.io ↗)
    4comments
  22. The Siberian Ice Maiden and the Scythian World(patrickwyman.substack.com ↗)
    discuss
  23. Salesforce Global Outage(salesforce.com ↗)
    136comments
  24. Show HN: I made a flight simulator, except you're just a passenger(inflightsimulator.com ↗)
    191comments
  25. Gemini 3.8 Live and 3.8 Live Extended Thinking(blog.google ↗)
    314comments
  26. Why I'm still bearish on LLMs after Navier-Stokes(dank.systems ↗)
    515comments
  27. Doing Everyone Else's Job(yosefk.com ↗)
    84comments
  28. Anatomy of a Texture(agentlien.github.io ↗)
    4comments
  29. Intelligence per Watt: Measuring Intelligence Efficiency of Local AI(arxiv.org ↗)
    46comments
  30. DeepSeek v4.1 Flash Is Now Our Best Hacking Model(enclave.ai ↗)
    46comments

How big are factorials?

40 pointsby 1d agoeli.thegreenplace.net
14 comments
19h agoHN ↗

Factorial (n) for n > 24 is greater than 10^n.

3h agoHN ↗

Reminds me of: Professor asked us to find the biggest factorial using C programming language. And then using LISP. You can imagine our surprise.

2h agoHN ↗

There is a algorithm call Prime Swing Factorial that can compute large factorials exactly in arbitrary precision math using prime factorization. Like 10000000! in under second depending of how optimized the math library it. Probably like 100x faster than the normal method.

10m agoHN ↗

With Lisp you can use iterative algos and get that under a second too. SBCL can be ridiculously fast; and if you optimize the compilation for integers... the speed gets really close to your solution.

3h agoHN ↗

Stirling's approximation is also used a lot in statistical mechanics, because you often have to calculate logs of state space sizes, which means lots of combinatorics and thus lots of factorials. Plus it's continuous so you can do calculus.

2h agoHN ↗

The author's casual mention of 52! at the opening of the article triggered an OLD webpage that I saw many years ago

https://czep.net/weblog/52cards.html

Anyone know how to determine the age of this page (it's got be at least 20yrs old)

2h agoHN ↗

The main.css file it imports dates itself to March 9 of 2005, and is housed in an "ancient history" section of the website that covers everything before October 26, 2010, so: "sometime between those two years" =P

1h agoHN ↗

Its first appearance on the WayBack Machine is October 13, 2009, which narrows the range somewhat.

2h agoHN ↗

52 cards is the first thing I think of when I think factorials. It's such a great and relatable way to convey the subject to people, plus it usually ends up blowing their minds like it did mine when I first learned of it. Not from this page, but from a YT vid many moons ago.

2h agoHN ↗

It was made during the brief XHTML craze. (And it's also invalid XHTML)

2h agoHN ↗

A quick and dirty approximation of the number of digits in n! is n lg n, which approximates n! from above, via the inequality

  1 * 2 * … * n ≤ n * … * n.

(This approximation should be familiar to many from an algorithmics class.)

For a tighter bound, use n lg n - n/2, or a better approximation of ln 10 in place of 1/2 if you wish. This comes from Stirling's approximation which notes that

  ln n! = n ln n - n + O(ln n).
1h agoHN ↗

(This approximation should be familiar to many from an algorithmics class.)

You need both sides though :)

What makes it interesting for estimating algorithmic complexity is that \log{n!} \in \Theta(n \log n). One side is obvious as you note, the other less so, but there's a famous trick to do both at once:

\log{n!} = \log{\prod_{h=0}^{n} h} = \sum_{h=0}^{n} \log{h}

Therefore,

\int_0^n \log{x} dx \le \log{n!} \le \int_0^n \log{x+1} dx

with both integrals trivial by parts.

1h agoHN ↗

lg(n!) grows roughly as (n lg n). Constants matter, of course, but to that's the rough estimate.

As an aside, if you take numbers from 0 to (n-1) in an array, there are n! configurations, so representing each configuration or differentiating each configuration take n lg n bits. So, in some sense, taking a mapping that's able to differentiate the input state to map to the ordered state takes at least O(n lg n) time, the standard runtime of a basic sorting algorithm.

Any additional assumptions (n larger than maximum element, distribution of elements) helps reduce this.