frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

We've created the first vectorized Quicksort

https://opensource.googleblog.com/2022/06/Vectorized%20and%20performance%20portable%20Quicksort.html
30•mococa•27m ago•4 comments

Small Programming Tricks

https://will-keleher.com/posts/small-programming-tricks-matter/
183•signa11•3h ago•111 comments

Dream-RSI: Recursive Self-Improvement through Evolving Worlds

https://arxiv.org/abs/2609.14858
130•bananaflag•5h ago•41 comments

Mistral X Mozilla: Private, Multilingual AI Browsing

https://mistral.ai/news/mistral-x-mozilla/
431•vertigoruntime•10h ago•157 comments

Tell the speakers that you liked their talks

https://ohhelloana.blog/tell-the-speakers/
173•whisper2020•1d ago•43 comments

Show HN: An e-ink frame that hears birds and draws them as 1800s illustrations

https://github.com/arnegiacomo/fugleramme
1916•arnemunthekaas•1d ago•225 comments

The DeepMind Institute

https://institute.deepmind.com/
57•vertigoruntime•4h ago•17 comments

Claude Cowork and chat are now one Claude

https://claude.com/blog/cowork-is-now-claude
110•vertigoruntime•2h ago•141 comments

How big are factorials?

https://eli.thegreenplace.net/2026/how-big-are-factorials/
53•ibobev•1d ago•16 comments

Apple Reference Image: A New Approach for Verified Photography

https://security.apple.com/blog/apple-reference-image/
471•imwally•16h ago•309 comments

The Siberian Ice Maiden and the Scythian World

https://patrickwyman.substack.com/p/the-siberian-ice-maiden-and-the-scythian
15•NaOH•23h ago•0 comments

Learning Programming in an Age of LLMs

https://blog.ploeh.dk/2026/09/16/on-learning-programming-in-an-age-of-llms/
184•moneroloop2018•9h ago•136 comments

Hackers Got Inside a Flock Camera

https://www.wired.com/story/hackers-flock-camera-data-shows-how-system-works/
345•driverdan•5h ago•170 comments

The Google Play app review process now regularly takes longer than a week

https://gultsch.social/@daniel/117280438824908947
296•inputmice•7h ago•283 comments

ER visits for gambling disorders doubled after expanded online gambling market

https://temertymedicine.utoronto.ca/news/emergency-room-visits-gambling-disorders-nearly-doubled-...
65•geox•1h ago•52 comments

GitHub Is Having Trouble Counting Things

https://chuckgreenman.com/2026/09/16/counting-at-github
8•chuckgreenman•1h ago•1 comments

Anecdotally, Programmers Dislike "Reduce"

https://evanhahn.com/posts/2026-09-13-programmers-dislike-reduce/
29•praptak•2d ago•34 comments

Kyber (YC W23) Is Hiring a Forward Deployed Engineer

https://www.ycombinator.com/companies/kyber/jobs/eturrAR-forward-deployed-engineer
1•asontha•6h ago

Can we stop with the uptime percentages?

https://blog.jim-nielsen.com/2026/stop-with-the-uptime-percentage/
91•surprisetalk•3h ago•73 comments

Show HN: How Stale Is Your AI? Release age and training cutoff for 20 models

https://stale.jock.pl/
50•joozio•5h ago•36 comments

Salesforce Global Outage

https://status.salesforce.com/products/all
240•mabil•8h ago•146 comments

A warning about 'model welfare'

https://mustafa-suleyman.ai/a-warning-about-model-welfare
102•andsoitis•4h ago•263 comments

This Code Is CRAP (2011)

https://testing.googleblog.com/2011/02/this-code-is-crap.html
61•luispa•2h ago•40 comments

Anatomy of a Texture

https://agentlien.github.io/texture/
34•Agentlien•4h ago•9 comments

Original Sony PlayStation 2 security chip 'broken wide open' after 26 years

https://www.tomshardware.com/video-games/playstation/26-year-old-sony-ps2-security-chip-broken-wi...
225•rbanffy•7h ago•63 comments

Scaling Golang CI by Replacing actions/setup-go

https://www.cloudx.ai/posts/setup-go
56•peterldowns•5h ago•14 comments

Show HN: I made a flight simulator, except you're just a passenger

https://inflightsimulator.com
372•rkotcher•2d ago•193 comments

Introducing System One Models and Jev

https://typesafe.ai/blog/introducing-system-one-models-and-jev
1753•albelfio•23h ago•467 comments

Gemini 3.8 Live and 3.8 Live Extended Thinking

https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-3-8-live-gemini-3-...
479•leumon•1d ago•316 comments

Why I'm still bearish on LLMs after Navier-Stokes

https://dank.systems/posts/2026-09-15-ai-bear.html
420•jaykru•1d ago•548 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?