frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Rust in the kernel is no longer experimental

https://lwn.net/Articles/1049831/
367•rascul•4h ago•174 comments

Revisiting "Let's Build a Compiler"

https://eli.thegreenplace.net/2025/revisiting-lets-build-a-compiler/
33•cui•1h ago•1 comments

Show HN: Gemini Pro 3 hallucinates the HN front page 10 years from now

https://dosaygo-studio.github.io/hn-front-page-2035/news
2428•keepamovin•17h ago•746 comments

PeerTube is recognized as a digital public good by Digital Public Goods Alliance

https://www.digitalpublicgoods.net/r/peertube
496•fsflover•15h ago•86 comments

Dependable C

https://dependablec.org/
37•RossBencina•3h ago•28 comments

Very Important People

https://dirt.fyi/article/2025/11/very-important-people
25•gmays•4d ago•10 comments

Django: what’s new in 6.0

https://adamj.eu/tech/2025/12/03/django-whats-new-6.0/
249•rbanffy•11h ago•54 comments

If you're going to vibe code, why not do it in C?

https://stephenramsay.net/posts/vibe-coding.html
437•sramsay•14h ago•430 comments

When a video codec wins an Emmy

https://blog.mozilla.org/en/mozilla/av1-video-codec-wins-emmy/
93•todsacerdoti•4d ago•12 comments

Mistral releases Devstral2 and Mistral Vibe CLI

https://mistral.ai/news/devstral-2-vibe-cli
572•pember•17h ago•279 comments

Handsdown one of the coolest 3D websites

https://bruno-simon.com/
540•razzmataks•16h ago•126 comments

Italy's longest-serving barista reflects on six decades behind the counter

https://www.reuters.com/lifestyle/culture-current/anna-possi-six-decades-behind-counter-italys-ba...
150•NaOH•5d ago•66 comments

Pebble Index 01 – External memory for your brain

https://repebble.com/blog/meet-pebble-index-01-external-memory-for-your-brain
472•freshrap6•17h ago•454 comments

10 Years of Let's Encrypt

https://letsencrypt.org/2025/12/09/10-years
609•SGran•13h ago•259 comments

Writing our own Cheat Engine in Rust

https://lonami.dev/blog/woce-1/
52•hu3•4d ago•6 comments

Donating the Model Context Protocol and establishing the Agentic AI Foundation

https://www.anthropic.com/news/donating-the-model-context-protocol-and-establishing-of-the-agenti...
206•meetpateltech•15h ago•98 comments

Are We over the "Jaws Effect?"

https://nautil.us/are-we-finally-over-the-jaws-effect-1253001/
16•fleahunter•4d ago•16 comments

Putting email in its place with Emacs and Mu4e

https://eamonnsullivan.co.uk/posts-output/email-setup/2025-12-3-putting-email-in-its-place/
5•eamonnsullivan•6d ago•0 comments

Distributed ID Formats Are Architectural Commitments, Not Just Data Types

https://piljoong.dev/posts/distributed-id-generation-complicated/
29•mnahkies•3d ago•5 comments

So you want to speak at software conferences?

https://dylanbeattie.net/2025/12/08/so-you-want-to-speak-at-software-conferences.html
157•speckx•13h ago•77 comments

Cloudflare error page generator

https://github.com/donlon/cloudflare-error-page
31•sawirricardo•5h ago•6 comments

The stack circuitry of the Intel 8087 floating point chip, reverse-engineered

https://www.righto.com/2025/12/8087-stack-circuitry.html
100•elpocko•13h ago•47 comments

Qt, Linux and everything: Debugging Qt WebAssembly

http://qtandeverything.blogspot.com/2025/12/debugging-qt-webassembly-dwarf.html
62•speckx•10h ago•15 comments

A supersonic engine core makes the perfect power turbine

https://boomsupersonic.com/flyby/ai-needs-more-power-than-the-grid-can-deliver-supersonic-tech-ca...
101•simonebrunozzi•16h ago•156 comments

'Source available' is not open source (and that's okay)

https://dri.es/source-available-is-not-open-source-and-that-is-okay
75•geerlingguy•4h ago•64 comments

Kaiju – General purpose 3D/2D game engine in Go and Vulkan with built in editor

https://github.com/KaijuEngine/kaiju
174•discomrobertul8•17h ago•86 comments

Linux CVEs, more than you ever wanted to know

http://www.kroah.com/log/blog/2025/12/08/linux-cves-more-than-you-ever-wanted-to-know/
53•voxadam•9h ago•29 comments

Operando interlayer expansion of curved graphene for dense supercapacitors

https://www.nature.com/articles/s41467-025-63485-0
21•westurner•5d ago•0 comments

30 Year Anniversary of WarCraft II: Tides of Darkness

https://www.jorsys.org/archive/december_2025.html#newsitem_2025-12-09T07:42:19Z
217•sjoblomj•22h ago•148 comments

Agentic AI Foundation

https://block.xyz/inside/block-anthropic-and-openai-launch-the-agentic-ai-foundation
104•thinkingkong•12h ago•21 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?