frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Estimates are difficult for developers and product owners

https://thorsell.io/2025/12/07/estimates.html
61•todsacerdoti•1h ago•39 comments

I failed to recreate the 1996 Space Jam Website with Claude

https://j0nah.com/i-failed-to-recreate-the-1996-space-jam-website-with-claude/
131•thecr0w•3h ago•88 comments

Google Titans architecture, helping AI have long-term memory

https://research.google/blog/titans-miras-helping-ai-have-long-term-memory/
276•Alifatisk•8h ago•90 comments

Scala 3 slowed us down?

https://kmaliszewski9.github.io/scala/2025/12/07/scala3-slowdown.html
122•kmaliszewski•5h ago•52 comments

An Interactive Guide to the Fourier Transform

https://betterexplained.com/articles/an-interactive-guide-to-the-fourier-transform/
71•pykello•5d ago•8 comments

Build a DIY magnetometer with a couple of seasoning bottles

https://spectrum.ieee.org/listen-to-protons-diy-magnetometer
34•nullbyte808•1w ago•2 comments

Dollar-stores overcharge cash-strapped customers while promising low prices

https://www.theguardian.com/us-news/2025/dec/03/customers-pay-more-rising-dollar-store-costs
77•bookofjoe•5h ago•93 comments

The state of Schleswig-Holstein is consistently relying on open source

https://www.heise.de/en/news/Goodbye-Microsoft-Schleswig-Holstein-relies-on-Open-Source-and-saves...
454•doener•7h ago•215 comments

Java Hello World, LLVM Edition

https://www.javaadvent.com/2025/12/java-hello-world-llvm-edition.html
145•ingve•8h ago•47 comments

The Anatomy of a macOS App

https://eclecticlight.co/2025/12/04/the-anatomy-of-a-macos-app/
130•elashri•8h ago•31 comments

Using LLMs at Oxide

https://rfd.shared.oxide.computer/rfd/0576
623•steveklabnik•19h ago•245 comments

Over fifty new hallucinations in ICLR 2026 submissions

https://gptzero.me/news/iclr-2026/
411•puttycat•7h ago•306 comments

Kilauea erupts, destroying webcam [video]

https://www.youtube.com/watch?v=TK2N99BDw7A
535•zdw•20h ago•116 comments

A geothermal amoeba sets a new upper temperature limit for eukaryotes

https://www.biorxiv.org/content/10.1101/2025.11.24.690213v1.full
16•wjb3•1h ago•1 comments

Vanity Activities

https://quarter--mile.com/vanity-activities
31•surprisetalk•6d ago•23 comments

Semantic Compression (2014)

https://caseymuratori.com/blog_0015
25•tosh•3h ago•2 comments

Z2 – Lithographically fabricated IC in a garage fab

https://sam.zeloof.xyz/second-ic/
311•embedding-shape•17h ago•71 comments

The programmers who live in Flatland

https://blog.redplanetlabs.com/2025/11/24/the-programmers-who-live-in-flatland/
53•winkywooster•1w ago•55 comments

Nested Learning: A new ML paradigm for continual learning

https://research.google/blog/introducing-nested-learning-a-new-ml-paradigm-for-continual-learning/
24•themgt•5h ago•0 comments

The past was not that cute

https://juliawise.net/the-past-was-not-that-cute/
364•mhb•22h ago•443 comments

Building a Toast Component

https://emilkowal.ski/ui/building-a-toast-component
58•FragrantRiver•4d ago•22 comments

Screenshots from developers: 2002 vs. 2015 (2015)

https://anders.unix.se/2015/12/10/screenshots-from-developers--2002-vs.-2015/
417•turrini•22h ago•188 comments

How the Disappearance of Flight 19 Fueled the Legend of the Bermuda Triangle

https://www.smithsonianmag.com/history/how-the-disappearance-of-flight-19-a-navy-squadron-lost-in...
40•pseudolus•8h ago•7 comments

Show HN: Spotify Wrapped but for LeetCode

https://github.com/collinboler/leetcodewrapped
8•collinboler2•1h ago•1 comments

The AI wildfire is coming. it's going to be painful and healthy

https://ceodinner.substack.com/p/the-ai-wildfire-is-coming-its-going
59•LordAtlas•3h ago•74 comments

The end of the road for Kafka-delta-ingest

https://brokenco.de/2025/10/30/kafka-delta-ingest-was-fun.html
7•alex_hirner•1w ago•1 comments

Should CSS be a constraint system instead?

https://pavpanchekha.com/blog/why-css-bad.html
21•fanf2•1h ago•16 comments

Discovering the indieweb with calm tech

https://alexsci.com/blog/calm-tech-discover/
191•todsacerdoti•17h ago•17 comments

What is “literate programming”? (2024)

https://pqnelson.github.io/2024/05/29/literate-programming.html
68•joecobb•5d ago•39 comments

Eurydice: a Rust to C compiler

https://jonathan.protzenko.fr/2025/10/28/eurydice.html
166•todsacerdoti•18h ago•100 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•6mo ago

Comments

balloob•6mo ago
Founder Home Assistant here. Want to chime in that I always love to see write ups like these to see the great things what people achieve with Home Assistant.

Not everyone might know, but last year we started the Open Home Foundation[1] as a non-profit in Switzerland and I donated Home Assistant to it[2]. It's fully funded by users. There are no investors involved.

We are fully committed to building out a smart home that focuses on local control and privacy. Yes there are rough edges, but we're actively working on it in the open, with progress being released every month.

~Paulus Founder Home Assistant & President Open Home Foundation https://github.com/balloob

[1]: https://www.openhomefoundation.org [2]: https://www.openhomefoundation.org/blog/announcing-the-open-...

pabs3•6mo ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•6mo ago
Comments moved thither. Thanks!
pabs3•6mo ago
They are two different articles, I don't think that was correct.
tomhow•6mo ago
The problem is we can’t have two closely-related threads (i.e., threads where there is significant subject/discussion overlap) active at once.

When that happens it just gets confusing, because it’s hard for people know which thread to comment in, if the comment they want to make is somewhere in the overlap. And then whichever one they choose to comment in, people who only see the other thread won’t see that comment. Then sometimes, anticipating this, people will copy and paste their comment in both threads (which happened in this case). But then each one gets different replies.

So each thread ends up being incomplete and duplicated all at once, and it all becomes a big confusing mess.

The fact that these two articles were by the same author, had the same title, were published just a week apart and could easily have been published as one, longer article, says to me that merging the threads was the right thing to do.

The other option would have been to bury the second thread and consider another thread about that second article a few months later, but that didn’t seem like the best option, given how much the two articles are so related and continuous.

Edit: Just thought I'd add that a major factor in deciding to merge the threads was this opening to the second part by the author:

The first article in this series provided an overview of Home Assistant, its community, and its capabilities. It was deliberately short on descriptions of interesting things that can be done with Home Assistant, though — the reasons why one might actually want to use this program. In this closing article, we'll look at how Home Assistant was used to solve some real problems.

To me it makes all the difference that the first part is introductory/high-level whilst the second part goes deeper into usage-scenarios. We'd treat it differently if each part went deeply into different aspects on the project.

pabs3•6mo ago
Thanks for the response, guess that makes sense.
pabs3•6mo ago
BTW, on lobste.rs, they can merge threads into one, and all the URLs are shown at the top. That might be a useful change to adopt for HN too?