frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Flash-MoE: Running a 397B Parameter Model on a Laptop

https://github.com/danveloper/flash-moe
191•mft_•5h ago•67 comments

Project Nomad – Knowledge That Never Goes Offline

https://www.projectnomad.us
146•jensgk•4h ago•23 comments

Building an FPGA 3dfx Voodoo with Modern RTL Tools

https://noquiche.fyi/voodoo
74•fayalalebrun•3h ago•14 comments

A Coherent Vision for the Future of Version Control

https://bramcohen.com/p/manyana
28•c17r•1h ago•8 comments

More common mistakes to avoid when creating system architecture diagrams

https://www.ilograph.com/blog/posts/more-common-diagram-mistakes/
68•billyp-rva•5h ago•24 comments

A review of dice that came with the white castle

https://boardgamegeek.com/thread/3533812/a-review-of-dice-that-came-with-the-white-castle
76•doener•3d ago•15 comments

Windows native app development is a mess

https://domenic.me/windows-native-dev/
115•domenicd•6h ago•107 comments

A case against currying

https://emi-h.com/articles/a-case-against-currying.html
47•emih•3h ago•59 comments

I hate: Programming Wayland applications

https://www.p4m.dev/posts/29/index.html
91•dwdz•1h ago•51 comments

Brute-Forcing My Algorithmic Ignorance with an LLM in 7 Days

http://blog.dominikrudnik.pl/my-google-recruitment-journey-part-1
49•qikcik•4h ago•25 comments

25 Years of Eggs

https://www.john-rush.com/posts/eggs-25-years-20260219.html
161•avyfain•4d ago•48 comments

Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

https://radar.cloudflare.com/domains/domain/archive.today
236•winkelmann•13h ago•192 comments

The IBM scientist who rewrote the rules of information just won a Turing Award

https://www.ibm.com/think/news/ibm-scientist-charles-bennett-turing-award
30•rbanffy•4h ago•3 comments

My first patch to the Linux kernel

https://pooladkhay.com/posts/first-kernel-patch/
176•pooladkhay•2d ago•32 comments

Node.js worker threads are problematic, but they work great for us

https://www.inngest.com/blog/node-worker-threads
42•goodoldneon•4d ago•20 comments

Tinybox – A powerful computer for deep learning

https://tinygrad.org/#tinybox
556•albelfio•20h ago•322 comments

Bored of eating your own dogfood? Try smelling your own farts

https://shkspr.mobi/blog/2026/03/bored-of-eating-your-own-dogfood-try-smelling-your-own-farts/
231•ColinWright•3h ago•137 comments

Monuses and Heaps

https://doisinkidney.com/posts/2026-03-03-monus-heaps.html
35•aebtebeten•3d ago•2 comments

Why Lab Coats Turned White

https://www.asimov.press/p/lab-coat
27•mailyk•3d ago•17 comments

A Fuzzer for the Toy Optimizer

https://bernsteinbear.com/blog/toy-fuzzer/
25•surprisetalk•5d ago•4 comments

You Are Not Your Job

https://jry.io/writing/you-are-not-your-job/
7•jryio•1h ago•2 comments

The three pillars of JavaScript bloat

https://43081j.com/2026/03/three-pillars-of-javascript-bloat
409•onlyspaceghost•14h ago•241 comments

How We Synchronized Editing for Rec Room's Multiplayer Scripting System

https://www.tyleo.com/blog/how-we-synchronized-editing-for-rec-rooms-multiplayer-scripting-system
13•tyleo•4h ago•11 comments

iBook Clamshell

https://www.ibook-clamshell.com/index.php/en/
37•polishdude20•2h ago•29 comments

Professional video editing, right in the browser with WebGPU and WASM

https://tooscut.app/
329•mohebifar•19h ago•118 comments

Apple's intentional crippling of Mobile Safari

https://pwa.gripe/
108•xd1936•3h ago•114 comments

Chest Fridge (2009)

https://mtbest.net/chest-fridge/
163•wolfi1•15h ago•87 comments

Ask HN: AI productivity gains – do you fire devs or build better products?

38•Bleiglanz•7h ago•50 comments

HopTab – Open source macOS app switcher and tiler that replaces Cmd+Tab

https://www.royalbhati.com/hoptab
85•robhati•10h ago•26 comments

Floci – A free, open-source local AWS emulator

https://github.com/hectorvent/floci
252•shaicoleman•19h ago•86 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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