The part of this story that isn't about Oracle or AI at all
Every angle above treats this as a story about AI policy or corporate hypocrisy. There's a third, genuinely different way to read it: as a case study in how stories go viral twice. The original reporting traces to The Register on August 3. That's roughly five days before this story reappeared on Hacker News' front page — not through the original Register link, but via a different aggregator (dealroom.co) surfacing the same underlying news to a fresh audience.
Why "evergreen-with-a-news-hook" is a distinct content category
Most viral stories operate on a single 24-48 hour attention window: they break, spike, and fade. This one didn't — it had a first life as a straightforward tech-policy story, went quiet, then had a second life days later when a different distribution channel exposed it to an audience that hadn't seen the first wave.
What made it resurface-able
Not every five-day-old story gets a second wave. This one had two ingredients that made it durable: a genuinely verifiable primary source (the actual openjdk.org policy page, not just reporting about it) and a built-in, easily-restated hook (the Ellison-irony contrast) that works just as well on day five as day one.
The practical implication
If you're trying to understand what's "trending" on any given day, a same-day HN spike doesn't necessarily mean same-day news — it can mean a days-old story just found a new audience.
HomePath covers what's shaping how people think about money and the technology reshaping it. This article is HomePath Editorial commentary, not financial or legal advice.