frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Claude Opus 5

https://www.anthropic.com/claude-opus-5-system-card
283•alvis•36m ago•152 comments

As of JDK 27, Oracle engineers will thus stop maintaining the macOS/x64 port

https://openjdk.org/jeps/541
50•pmg1991•41m ago•26 comments

My security camera shipped a GitHub admin token in its login page

https://hhh.hn/hanwha-github-token/
345•hhh•5h ago•130 comments

India's first privately-developed rocket reaches orbit on dramatic debut launch

https://arstechnica.com/space/2026/07/indias-first-privately-developed-rocket-reaches-orbit-on-dr...
301•sohkamyung•4d ago•79 comments

Half-Life 2 running natively on HaikuOS

https://discuss.haiku-os.org/t/haiku-nvidia-porting-nvidia-driver-for-turing-gpus/16520?page=18
143•m0do1•4h ago•16 comments

The front end framework for correctness: built on Effect, architected like Elm

https://foldkit.dev/
42•plucafs•2h ago•20 comments

Micro-SaaS Is Dead. Service With A Software Replaces It

https://adriengonin.com/writing/service-with-a-software/
21•Adrig•1h ago•18 comments

The rise and fall of language diversity through the Holocene

https://www.science.org/doi/10.1126/science.adx4343
14•delichon•52m ago•1 comments

Unitree As2-W

https://www.unitree.com/As2-W/
19•MehrdadKhnzd•1h ago•6 comments

Flux 3 X Mimic: The Next Generation of Video-Action Models

https://bfl.ai/blog/flux-3-mimic
276•kensai•8h ago•45 comments

It's getting harder to focus every day

https://glyphack.com/attention/
557•peykar•9h ago•312 comments

Making Xen's dom0 I/O path NUMA aware

https://edera.dev/stories/numa-part-4-closing-the-xen-dom0-i-o-gap
15•virtio_vixen•2d ago•0 comments

Be skeptical of OpenAI's rogue hacker agent story

https://www.theguardian.com/technology/2026/jul/24/openai-rogue-hacker
67•rwmj•1h ago•20 comments

Online Historical Encyclopaedia of Programming Languages

https://hopl.info/
10•gregsadetsky•46m ago•1 comments

Claude Opus 5

https://www.anthropic.com/news/claude-opus-5
47•meetpateltech•38m ago•7 comments

Government orders GitHub to remove Bluetooth-based chat app Bitchat: Jack Dorsey

https://www.thehindu.com/news/national/government-orders-github-to-remove-bluetooth-based-chat-ap...
210•rootkea•2h ago•118 comments

Plants vs. Zombies for PlayStation 2

https://github.com/OptiJuegos/pvz-ps2
38•Jotalea•3h ago•3 comments

Flux 3

https://bfl.ai/blog/flux-3
510•ThouYS•11h ago•121 comments

WebGPU Unleashed: A Practical Tutorial

https://shi-yan.github.io/webgpuunleashed/
27•ibobev•3h ago•1 comments

Em dashes are fucking amazing

https://psychotechnology.substack.com/p/em-dashes-are-fucking-amazing
247•surprisetalk•4h ago•219 comments

3GPP Version 19

https://www.3gpp.org/specifications-technologies/releases/release-19
36•mlhpdx•3h ago•9 comments

Co-Opting Linux Processes for High-Performance Network Simulation (2022)

https://www.usenix.org/conference/atc22/presentation/jansen
17•teleforce•3h ago•0 comments

Apple won't let me show my app

https://wisedayplanner.com/blog/apple-wont-let-me-show-my-app/
14•codersfocus•52m ago•13 comments

My Emacs Configuration (Dired)

https://eugene-andrienko.com/2026-07-05-my-emacs-configuration-dired.html
23•meysamazad•3h ago•4 comments

Proving a Human Wrote Something

https://gjtorikian.online/posts/proving-a-human-wrote-something/
9•gjtorikian•1h ago•12 comments

Claude Cookbook

https://platform.claude.com/cookbook/
265•saikatsg•12h ago•132 comments

Writing a Debugger from Scratch

https://www.timdbg.com/posts/writing-a-debugger-from-scratch-part-1/
29•ibobev•3h ago•5 comments

Buz – A fork of Bun using modern Zig, with sub-1s incremental builds

https://ziggit.dev/t/buz-a-drop-in-replacement-for-bun-using-modern-zig-with-sub-1s-incremental-b...
189•kristoff_it•8h ago•137 comments

The IBM PC, Part 1: Arrival

https://technicshistory.com/2026/07/24/the-ibm-pc-part-1-arrival/
60•cfmcdonald•6h ago•19 comments

Mag Computer: A Mag History of RAM (1960–2025)

https://magworld.pw/episodes/computer/
12•evakhoury•3h ago•2 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•1y ago

Comments

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

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

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