frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Windows 9x Subsystem for Linux

https://social.hails.org/@hailey/116446826733136456
381•sohkamyung•4h ago•102 comments

GitHub CLI now collects pseudoanonymous telemetry

https://cli.github.com/telemetry
148•ingve•2h ago•87 comments

3.4M Solar Panels

https://tech.marksblogg.com/american-solar-farms-v2.html
105•marklit•2h ago•56 comments

The eighth-generation TPU: An architecture deep dive

https://cloud.google.com/blog/products/compute/tpu-8t-and-tpu-8i-technical-deep-dive
47•meetpateltech•1h ago•6 comments

Our eighth generation TPUs: two chips for the agentic era

https://blog.google/innovation-and-ai/infrastructure-and-cloud/google-cloud/eighth-generation-tpu...
101•xnx•2h ago•67 comments

Another Day Has Come

https://daringfireball.net/2026/04/another_day_has_come
42•ndr42•17h ago•32 comments

Kernel code removals driven by LLM-created security reports

https://lwn.net/Articles/1068928/
45•edward•2h ago•19 comments

How the heck does GPS work?

https://perthirtysix.com/how-the-heck-does-gps-work
110•alfanick•5h ago•20 comments

Making RAM at Home [video]

https://www.youtube.com/watch?v=h6GWikWlAQA
467•kaipereira•1d ago•130 comments

ChatGPT Images 2.0

https://openai.com/index/introducing-chatgpt-images-2-0/
922•wahnfrieden•19h ago•797 comments

Nobody Got Fired for Uber's $8M Ledger Mistake?

https://news.alvaroduran.com/p/nobody-got-fired-for-ubers-8-million
71•ohduran•3h ago•41 comments

Columnar Storage Is Normalization

https://buttondown.com/jaffray/archive/columnar-storage-is-normalization/
16•ibobev•1h ago•10 comments

Why Musicians Are Manufacturing Sold-Out Shows

https://www.bloomberg.com/news/articles/2026-04-17/how-bands-like-cameron-winter-s-geese-are-manu...
37•helsinkiandrew•3d ago•28 comments

XOR'ing a register with itself is the idiom for zeroing it out. Why not sub?

https://devblogs.microsoft.com/oldnewthing/20260421-00/?p=112247
96•ingve•7h ago•110 comments

All your agents are going async

https://zknill.io/posts/all-your-agents-are-going-async/
89•zknill•2d ago•54 comments

Treetops glowing during storms captured on film for first time

https://www.psu.edu/news/earth-and-mineral-sciences/story/treetops-glowing-during-storms-captured...
3•t-3•53m ago•0 comments

Prefill-as-a-Service:KVCache of Next-Generation Models Could Go Cross-Datacenter

https://arxiv.org/abs/2604.15039
22•matt_d•3d ago•1 comments

Contact Lens Uses Microfluidics to Monitor and Treat Glaucoma

https://spectrum.ieee.org/smart-contact-lens-glaucoma-microfluidics
73•pseudolus•3d ago•2 comments

MuJoCo – Advanced Physics Simulation

https://github.com/google-deepmind/mujoco
65•modinfo•3d ago•12 comments

Garbage Collection Without Unsafe Code

https://fitzgen.com/2024/02/06/safe-gc.html
80•foota•3d ago•21 comments

Monitor your Pi / OMP sessions

https://github.com/BlackBeltTechnology/pi-agent-dashboard
6•ankitg12•3d ago•0 comments

Drunk post: Things I've learned as a senior engineer (2021)

https://luminousmen.substack.com/p/drunk-post-things-ive-learned-as
207•zdw•14h ago•147 comments

Windows Server 2025 Runs Better on ARM

https://jasoneckert.github.io/myblog/server-2025-arm64/
155•jasoneckert•3d ago•120 comments

The Vercel breach: OAuth attack exposes risk in platform environment variables

https://www.trendmicro.com/en_us/research/26/d/vercel-breach-oauth-supply-chain.html
340•queenelvis•21h ago•112 comments

CATL's new LFP battery can charge from 10 to 98% in less than 7 minutes

https://arstechnica.com/cars/2026/04/catls-new-lfp-battery-can-charge-from-10-to-98-in-less-than-...
63•PotatoNinja•3h ago•27 comments

Acetaminophen vs. ibuprofen

https://asteriskmag.com/issues/14/the-mystery-in-the-medicine-cabinet
537•nkurz•1d ago•338 comments

SpaceX says it has agreement to acquire Cursor for $60B

https://twitter.com/spacex/status/2046713419978453374
697•dmarcos•16h ago•871 comments

Meta to start capturing employee mouse movements, keystrokes for AI training

https://www.reuters.com/sustainability/boards-policy-regulation/meta-start-capturing-employee-mou...
682•dlx•20h ago•452 comments

Britannica11.org – a structured edition of the 1911 Encyclopædia Britannica

https://britannica11.org/
322•ahaspel•20h ago•107 comments

Diverse organic molecules on Mars revealed by the first SAM TMAH experiment

https://www.courthousenews.com/preserved-for-billions-of-years-organic-compounds-found-on-mars/
89•geox•1d ago•6 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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