frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

What an unprocessed photo looks like

https://maurycyz.com/misc/raw_photo/
193•zdw•1h ago•36 comments

Stepping down as Mockito maintainer after 10 years

https://github.com/mockito/mockito/issues/3777
177•saikatsg•3h ago•83 comments

Unity's Mono problem: Why your C# code runs slower than it should

https://marekfiser.com/blog/mono-vs-dot-net-in-unity/
60•iliketrains•2h ago•24 comments

PySDR: A Guide to SDR and DSP Using Python

https://pysdr.org/content/intro.html
75•kklisura•4h ago•4 comments

Spherical Cow

https://lib.rs/crates/spherical-cow
11•Natfan•1h ago•1 comments

62 years in the making: NYC's newest water tunnel nears the finish line

https://ny1.com/nyc/all-boroughs/news/2025/11/09/water--dep--tunnels-
24•eatonphil•1h ago•6 comments

MongoBleed Explained Simply

https://bigdata.2minutestreaming.com/p/mongobleed-explained-simply
54•todsacerdoti•3h ago•14 comments

Slaughtering Competition Problems with Quantifier Elimination

https://grossack.site/2021/12/22/qe-competition.html
8•todsacerdoti•1h ago•0 comments

Researchers Discover Molecular Difference in Autistic Brains

https://medicine.yale.edu/news-article/molecular-difference-in-autistic-brains/
21•amichail•1h ago•5 comments

Growing up in “404 Not Found”: China's nuclear city in the Gobi Desert

https://substack.com/inbox/post/182743659
670•Vincent_Yan404•17h ago•291 comments

Time in C++: Inter-Clock Conversions, Epochs, and Durations

https://www.sandordargo.com/blog/2025/12/24/clocks-part-5-conversions
12•ibobev•2d ago•0 comments

Remembering Lou Gerstner

https://newsroom.ibm.com/2025-12-28-Remembering-Lou-Gerstner
57•thm•5h ago•27 comments

Building a macOS app to know when my Mac is thermal throttling

https://stanislas.blog/2025/12/macos-thermal-throttling-app/
215•angristan•12h ago•96 comments

CEOs are hugely expensive. Why not automate them?

https://www.newstatesman.com/business/companies/2023/05/ceos-salaries-expensive-automate-robots
98•nis0s•56m ago•76 comments

Doublespeak: In-Context Representation Hijacking

https://mentaleap.ai/doublespeak/
40•surprisetalk•6d ago•5 comments

Show HN: Pion SCTP with RACK is 70% faster with 30% less latency

https://pion.ly/blog/sctp-and-rack/
32•pch07•6h ago•4 comments

Dolphin Progress Report: Release 2512

https://dolphin-emu.org/blog/2025/12/22/dolphin-progress-report-release-2512/
51•akyuu•2h ago•3 comments

Software engineers should be a little bit cynical

https://www.seangoedecke.com/a-little-bit-cynical/
95•zdw•2h ago•73 comments

Learn computer graphics from scratch and for free

https://www.scratchapixel.com
162•theusus•13h ago•19 comments

John Malone and the Invention of Liquid-Based Engines

https://permalink.lanl.gov/object/tr?what=info:lanl-repo/lareport/LA-UR-93-1350-25
12•akshatjiwan•4d ago•1 comments

As AI gobbles up chips, prices for devices may rise

https://www.npr.org/2025/12/28/nx-s1-5656190/ai-chips-memory-prices-ram
24•geox•1h ago•10 comments

Show HN: Phantas – A browser-based binaural strobe engine (Web Audio API)

https://phantas.io
12•AphantaZach•3h ago•5 comments

One year of keeping a tada list

https://www.ducktyped.org/p/one-year-of-keeping-a-tada-list
215•egonschiele•6d ago•60 comments

Why I Disappeared – My week with minimal internet in a remote island chain

https://www.kenklippenstein.com/p/why-i-disappeared
11•eh_why_not•2h ago•0 comments

Show HN: LoongArch Userspace Emulator

https://github.com/libriscv/libloong
14•fwsgonzo•4d ago•3 comments

Langfuse (YC W23) Is Hiring in Berlin, Germany

https://langfuse.com/careers
1•clemo_ra•12h ago

Oral History of Richard Greenblatt (2005) [pdf]

https://archive.computerhistory.org/resources/text/Oral_History/Greenblatt_Richard/greenblatt.ora...
7•0xpgm•3d ago•0 comments

Calendar

https://neatnik.net/calendar/?year=2026
944•twapi•19h ago•115 comments

2D Signed Distance Functions

https://iquilezles.org/articles/distfunctions2d/
82•nickswalker•4d ago•12 comments

Designing Predictable LLM-Verifier Systems for Formal Method Guarantee

https://arxiv.org/abs/2512.02080
52•PaulHoule•9h ago•11 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

balloob•7mo 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•7mo ago
Discussion for the other article in the series:

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

tomhow•7mo ago
Comments moved thither. Thanks!
pabs3•7mo ago
They are two different articles, I don't think that was correct.
tomhow•7mo 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•7mo ago
Thanks for the response, guess that makes sense.
pabs3•7mo 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?