frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Don't be a meat proxy

https://gruhn.me/blog/2026-08-03/
375•ngruhn•2h ago•171 comments

Qwen3.8-Max: A New Bar for Coding and Cowork

https://qwen.ai/blog?id=qwen3.8
518•ai2027•6h ago•242 comments

Rust project goals: Immobile types and guaranteed destructors

https://github.com/rust-lang/rust-project-goals/blob/main/src/2026/move-trait.md
45•paavohtl•2h ago•13 comments

More German than many Germans

https://mertbulan.com/more-german-than-many-germans/
203•mertbio•2h ago•103 comments

Show HN: Isopolis – Isometric pixel map of SF

https://sf.isopolis.city/
207•nuwandavek•8h ago•45 comments

Bonsai: Janestreet's UI Library

https://github.com/janestreet/bonsai
3•KolmogorovComp•21m ago•0 comments

Karpathy’s Pelican

https://twitter.com/karpathy/status/2083749667410727319
559•delichon•1d ago•388 comments

Octane – React's programming model, compiled

https://octanejs.dev
3•nnx•47m ago•0 comments

Show HN: ssh ssh.place

https://ssh.place
108•jeninh•8h ago•63 comments

Why we write our own C and C++ inference engines

https://localai.io/blog/why-we-write-our-own-engines/
48•eatonphil•2d ago•23 comments

AI migrated legacy COBOL programs to Java, bugs included

https://arxiv.org/abs/2607.28271
58•felineflock•5h ago•44 comments

CP/M-386 – CP/M for 386 protected mode, derived from CP/M‑68K

https://github.com/johnsonjh/cpm386
64•TMWNN•8h ago•27 comments

Convergence is not enough

https://www.inkandswitch.com/livelymerge/notebook/lm-02/
30•zdw•6d ago•3 comments

Autoregressive Language Model on the 6502 Processor

https://mattbeton.com/blog/bitnet-6502.html
105•nmstoker•2d ago•10 comments

Show HN: A Handwritten Blogging Platform

https://handwritten.blog/
96•emilesilvis•3d ago•48 comments

Note-Taking and Personal Knowledge Management

https://unattributed.cc/note-taking-and-personal-knowledge-management
193•surprisetalk•5d ago•57 comments

Show HN: Kakehashi – Experimental userspace to run macOS binaries on Linux ARM

https://github.com/wie-project/kakehashi
214•vlad_kalinkin•16h ago•55 comments

Developers are attached to tools because tools encode trust

https://stackoverflow.blog/2026/07/29/developers-are-attached-to-tools-because-tools-encode-trust/
208•HieronymusBosch•4d ago•110 comments

SwiftUI After 7 Years

https://ykvm.com/2026/07/swiftui-a-story-of-mediocrity/
189•mpweiher•13h ago•168 comments

The Shape of Things to Come

https://yegge.ai/essays/the-shape-of-things-to-come/
6•tosh•1h ago•1 comments

Why Book Corners won't sync contributions back to OpenStreetMap

https://www.andreagrandi.it/posts/why-book-corners-wont-sync-contributions-back-to-openstreetmap/
87•pizzaiolo•8h ago•54 comments

How do you rewrite C/C++ projects to Rust?

https://blog.jetbrains.com/rust/2026/07/27/cpp-to-rust-migration/
3•smokeeaasd•5d ago•0 comments

The AI Productivity Gap

https://bjorg.bjornroche.com/management/ai-productivity-gap/
3•kiyanwang•1h ago•0 comments

Situational Awareness and the Impending Stock Market Volatility

https://www.emergingtrajectories.com/lh/situational-awareness-bigger-picture/
5•cl42•2h ago•3 comments

Read the novels and forget everything else

https://hedgehogreview.com/web-features/thr/posts/read-the-novels-and-forget-everything-else
96•samclemens•2d ago•79 comments

The myth of Snow Leopard

https://www.rubenerd.au/the-myth-of-snow-leopard/
94•speckx•14h ago•77 comments

Show HN: I created a project management system

https://is.team
5•spotlayn•2h ago•1 comments

Norway became a global salmon behemoth. Now it's facing the consequences

https://www.abc.net.au/news/2026-07-28/how-norway-s-salmon-industry-became-a-global-behemoth/1069...
150•CHB0403085482•6d ago•114 comments

RFC 9851: TLS 1.2 is in Feature Freeze

https://www.rfc-editor.org/rfc/rfc9851.html
34•Jimmc414•7h ago•14 comments

How the words we teach English language learners changed

https://pudding.cool/2026/07/essential-words/
214•c-oreills•17h ago•164 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?