frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

SQLite is all you need for durable workflows

https://obeli.sk/blog/sqlite-is-all-you-need-for-durable-workflows/
529•tomasol•15h ago•259 comments

Algebraic Effects for the Rest of Us

https://overreacted.io/algebraic-effects-for-the-rest-of-us/
50•satvikpendem•3d ago•23 comments

Danish pension fund excludes SpaceX citing governance and valuation

https://www.reuters.com/legal/transactional/danish-pension-fund-excludes-spacex-citing-governance...
62•vrganj•1h ago•25 comments

Snowboard Kids 2 is 100% Decompiled

https://blog.chrislewis.au/snowboard-kids-2-is-100-decompiled/
195•GaggiX•3d ago•72 comments

Notes from the Mistral AI Now Summit

https://koenvangilst.nl/lab/mistral-ai-now-summit
370•vnglst•17h ago•150 comments

What It Takes to Preserve Floppy Disks

https://spectrum.ieee.org/floppy-disk-data-preservation-archives
47•pseudolus•2d ago•12 comments

Print with dozens of colors: Our new open-source ColorMix for PrusaSlicer

https://blog.prusa3d.com/our-new-open-source-colormix-model-in-prusaslicer-and-easyprint_136079/
151•rented_mule•3d ago•32 comments

MCP is dead?

https://www.quandri.io/engineering-blog/mcp-is-dead
228•nadis•10h ago•197 comments

Perry Compiles TypeScript directly to executables using SWC and LLVM

https://www.perryts.com/
91•0x1997•6h ago•73 comments

Iron-rich immune cells help homing pigeons navigate

https://www.science.org/content/article/mind-blowing-iron-rich-immune-cells-help-homing-pigeons-n...
21•XzetaU8•1h ago•0 comments

A new register allocator for ZJIT

https://railsatscale.com/2026-05-27-a-new-register-allocator-for-zjit/
39•tenderlove•2d ago•1 comments

Rsync 3.4.3 has hundreds of Claude commits

https://mastodon.gamedev.place/@JeremiahFieldhaven/116654345332213390
49•fooker•57m ago•29 comments

Quantum dot qubit using High NA EUV lithography

https://www.imec-int.com/en/press/world-first-imec-presents-quantum-dot-qubit-device-using-high-n...
9•luu•3d ago•0 comments

Shift will clean homes for free to train future robots

https://www.theverge.com/ai-artificial-intelligence/939765/ai-training-data-startup-shift-free-cl...
139•evilsimon•14h ago•189 comments

Naphtha shortages in Japan

https://www.nippon.com/en/japan-data/h02783/
113•takakaze•7h ago•76 comments

Citing 'severe' math deficits, UC faculty demand a return to SAT tests for STEM

https://www.latimes.com/california/story/2026-05-27/uc-math-professors-demand-return-of-sat-for-s...
591•brandonb•1d ago•787 comments

It's hard to justify buying a Framework 12

https://www.jeffgeerling.com/blog/2026/its-hard-to-justify-framework-12/
295•watermelon0•18h ago•493 comments

The dead economy theory

https://www.owenmcgrann.com/p/the-dead-economy-theory
989•WillDaSilva•17h ago•1131 comments

OpenRCT2 v0.5.1 "Swamp Castle" released Last version to support Windows 7

https://openrct2.io/blog/2026/05/openrct2-v0.5.1-released
14•jandeboevrie•3h ago•2 comments

The Last Technical Interview

https://steve-yegge.medium.com/the-last-technical-interview-bc13ddcf4564
111•headalgorithm•13h ago•92 comments

Show HN: Tiny-vLLM – high performance LLM inference engine in C++ and CUDA

https://github.com/jmaczan/tiny-vllm
147•yu3zhou4•13h ago•12 comments

Liquid AI reveals 8B-A1B MoE trained on 38T

https://www.liquid.ai/blog/lfm2-5-8b-a1b
186•simjnd•17h ago•72 comments

Is AI causing a repeat of frontend’s lost decade?

https://mastrojs.github.io/blog/2026-05-23-is-AI-causing-a-repeat-of-frontends-lost-decade/
346•xyzal•22h ago•293 comments

Bijou64: A variable-length integer encoding

https://www.inkandswitch.com/tangents/bijou64/
226•justinweiss•18h ago•79 comments

Show HN: Open-source private home security camera system (end-to-end encryption)

https://github.com/secluso/core
60•arrdalan•10h ago•15 comments

Math-to-Manim

https://github.com/HarleyCoops/Math-To-Manim
49•georgewsinger•2d ago•6 comments

The mysterious Hy3 LLM is topping OpenRouter Model Rankings by a large margin

https://minimaxir.com/2026/05/openrouter-hy3/
130•freediver•1d ago•103 comments

On Rendering Diffs

https://pierre.computer/writing/on-rendering-diffs
172•amadeus•14h ago•57 comments

What Is a Dickover?

https://daringfireball.net/2026/05/what_is_a_dickover
340•tambourine_man•9h ago•132 comments

Ho-scale slot car racing in the Santa Cruz Mountains

https://stewartraceway.org/
6•HoldOnAMinute•3d ago•1 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?