frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

80386 Microcode Disassembled

https://www.reenigne.org/blog/80386-microcode-disassembled/
23•nand2mario•26m ago•1 comments

Making Deep Learning Go Brrrr from First Principles

https://horace.io/brrr_intro.html
14•tosh•48m ago•4 comments

Shipping a laptop to a refugee camp in Uganda

https://notesbylex.com/shipping-a-laptop-to-a-refugee-camp-in-uganda
532•lexandstuff•15h ago•184 comments

US tech firms share Dutch regulator officials' names with Senate

https://www.dutchnews.nl/2026/05/us-tech-firms-share-dutch-regulator-officials-names-with-senate/
70•zqna•1h ago•37 comments

Rubish: A Unix shell written in pure Ruby

https://github.com/amatsuda/rubish
72•winebarrel•6h ago•31 comments

Why Japanese companies do so many different things

https://davidoks.blog/p/why-japanese-companies-do-so-many
730•d0ks•21h ago•342 comments

BambuStudio has been violating PrusaSlicer AGPL license since their fork

https://xcancel.com/josefprusa/status/2054602354851254330
144•Tomte•4h ago•41 comments

The quadratic sandwich

https://fedemagnani.github.io/math/2026/04/08/the-quadratic-sandwich.html
73•cpp_frog•3d ago•4 comments

DHS Quits Granting Green Cards–Almost

https://www.cato.org/blog/dhs-quits-granting-green-cards-almost-entirely
23•malshe•1h ago•6 comments

Improving C# Memory Safety

https://devblogs.microsoft.com/dotnet/improving-csharp-memory-safety/
25•soheilpro•1d ago•3 comments

Microsoft starts canceling Claude Code licenses

https://www.theverge.com/tech/930447/microsoft-claude-code-discontinued-notepad
322•robertkarl•19h ago•267 comments

ArcBrush – Node-based 2D image editor

https://arcbrush.com/
27•NatKarmios•2d ago•8 comments

Project Glasswing: An Initial Update

https://www.anthropic.com/research/glasswing-initial-update
463•louiereederson•17h ago•279 comments

Yeunjoo Choi from Igalia on Chromium

https://theconsensus.dev/p/2026/05/20/yeunjoo-choi-from-igalia-on-chromium.html
33•eatonphil•2d ago•3 comments

Blood Pumping Mechanism of the Hoof (2020)

https://horses.extension.org/blood-pumping-mechanism-of-the-hoof/
99•thunderbong•3d ago•29 comments

Fast Factorial Algorithms

http://www.luschny.de/math/factorial/FastFactorialFunctions.htm
10•nill0•3d ago•3 comments

Sleep research led to a new sleep apnea drug

https://temertymedicine.utoronto.ca/news/how-decades-sleep-research-led-new-sleep-apnea-drug
182•colinprince•14h ago•105 comments

CISA tries to contain data leak

https://krebsonsecurity.com/2026/05/lawmakers-demand-answers-as-cisa-tries-to-contain-data-leak/
224•speckx•19h ago•51 comments

Deno 2.8

https://deno.com/blog/v2.8
377•roflcopter69•1d ago•158 comments

Experience: We found a baby on the subway – now he's our 26-year-old son

https://www.theguardian.com/lifeandstyle/2026/may/22/experience-found-baby-subway-now-26-year-old...
133•Michelangelo11•5h ago•36 comments

What is the history of the ERROR_ARENA_TRASHED error code?

https://devblogs.microsoft.com/oldnewthing/20260519-00/?p=112339
41•supermatou•2d ago•12 comments

A Wayland Compositor in Minecraft

https://modrinth.com/mod/waylandcraft
235•Jotalea•2d ago•52 comments

Antigravity 2.0 Tops the OpenSCAD Architectural 3D LLM Benchmark

https://modelrift.com/blog/openscad-llm-benchmark/
394•jetter•1d ago•153 comments

Neutron scattering explains why gluten-free pasta falls apart (2025)

https://phys.org/news/2025-09-science-spaghetti-neutron-gluten-free.html
78•layer8•2d ago•28 comments

Open source Kanban desktop app that runs parallel agents on every card

https://www.kanbots.dev/
229•vitriapp•18h ago•136 comments

Comparing an LZ4 Decompressor on Four Legacy CPUs

https://bumbershootsoft.wordpress.com/2026/05/09/comparing-an-lz4-decompressor-on-four-legacy-cpus/
80•tosh•3d ago•5 comments

A Forth-inspired language for writing websites

https://robida.net/entries/2026/05/21/a-forth-inspired-language-for-writing-websites
152•speckx•21h ago•17 comments

I’m writing again

https://www.cringely.com/2026/05/21/im-writing-again/
154•dan_hawkins•22h ago•39 comments

Wi-Wi is wireless time sync at 1 nanosecond

https://www.jeffgeerling.com/blog/2026/wi-wi-is-wireless-time-sync-less-than-5ns/
127•Brajeshwar•2d ago•32 comments

1940 Air Terminal Museum Begins Liquidation

https://www.1940airterminal.org/news/liquidation-of-simulators
121•weaponeer•19h ago•30 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?