frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

How fast is a macOS VM, and how small could it be?

https://eclecticlight.co/2026/05/02/how-fast-is-a-macos-vm-and-how-small-could-it-be/
69•moosia•3h ago•19 comments

Why does it take so long to release black fan versions?

https://www.noctua.at/en/expertise/blog/how-can-it-take-so-long-to-release-black-fan-versions
353•buildbot•8h ago•162 comments

Why are there both TMP and TEMP environment variables? (2015)

https://devblogs.microsoft.com/oldnewthing/20150417-00/?p=44213
75•ankitg12•4h ago•41 comments

The Century-Long Pause in Fundamental Physics

https://danieltan.weblog.lol/2026/05/the-century-long-pause-in-fundamental-physics
8•danieltanfh95•47m ago•0 comments

Show HN: DAC – open-source dashboard as code tool for agents and humans

https://github.com/bruin-data/dac
39•karakanb•2d ago•8 comments

Show HN: Piruetas – A self-hosted diary app I built for my girlfriend

https://piruet.app
28•patillacode•2h ago•28 comments

Dotcl: Common Lisp Implementation on .NET

https://github.com/dotcl/dotcl
51•reikonomusha•1d ago•6 comments

Ti-84 Evo

https://education.ti.com/en/products/calculators/graphing-calculators/ti-84-evo
481•thatxliner•16h ago•406 comments

Show HN: Browser-based light pollution simulator using real photometric data

https://iesna.eu/?wasm=skyglow_demo
22•holg•3h ago•6 comments

Show HN: Mljar Studio – local AI data analyst that saves analysis as notebooks

https://mljar.com/
24•pplonski86•2h ago•3 comments

Open Design: Use Your Coding Agent as a Design Engine

https://github.com/nexu-io/open-design
4•steveharing1•44m ago•0 comments

Show HN: Filling PDF forms with AI using client-side tool calling

https://copilot.simplepdf.com/?share=a7d00ad073c75a75d493228e6ff7b11eb3f2d945b6175913e87898ec96ca...
22•nip•4h ago•14 comments

Artemis II Photo Timeline

https://artemistimeline.com/#artemis-ii-walkout-nhq202604010003
243•geerlingguy•2d ago•21 comments

New research suggests people can communicate and practice skills while dreaming

https://www.newyorker.com/culture/annals-of-inquiry/its-possible-to-learn-in-our-sleep-should-we
368•XzetaU8•19h ago•213 comments

Bitmap and tilemap generation from a single example

https://github.com/mxgmn/WaveFunctionCollapse
42•futurecat•2d ago•8 comments

To Restore an Island Paradise, Add Fungi

https://e360.yale.edu/digest/atoll-islands-sea-level-rise-fungi
83•Brajeshwar•2d ago•15 comments

Show HN: Large Scale Article Extract of Newspapers 1730s-1960s

https://snewpapers.com/
17•brettnbutter•4h ago•12 comments

Ask.com has closed

https://www.ask.com/
310•supermdguy•8h ago•167 comments

SFO Gate Explorer

https://www.flysfo.com/passengers/services/gate-explorer
4•CaliforniaKarl•1d ago•6 comments

GameStop Preparing Offer for eBay

https://www.wsj.com/business/deals/gamestop-preparing-offer-for-ebay-1678e6de
22•voisin•2h ago•12 comments

CollectWise (YC F24) Is Hiring

https://www.ycombinator.com/companies/collectwise/jobs/rEWfZ6R-senior-forward-deployed-engineer
1•OBrien_1107•8h ago

I'm Peter Roberts, immigration attorney who does work for YC and startups. AMA

171•proberts•21h ago•224 comments

LFM2-24B-A2B: Scaling Up the LFM2 Architecture

https://www.liquid.ai/blog/lfm2-24b-a2b
48•nateb2022•2d ago•9 comments

DeepSeek V4–almost on the frontier, a fraction of the price

https://simonwillison.net/2026/Apr/24/deepseek-v4/
199•indigodaddy•20h ago•101 comments

A report on burnout in open source software communities (2025) [pdf]

https://mirandaheath.website/static/oss_burnout_report_mh_25.pdf
99•susam•13h ago•38 comments

Lib0xc: A set of C standard library-adjacent APIs for safer systems programming

https://github.com/microsoft/lib0xc
155•wooster•17h ago•60 comments

Ask HN: Who is hiring? (May 2026)

274•whoishiring•22h ago•289 comments

Show HN: Stop playing my matchstick puzzles, start building your own in seconds

https://mathstick.github.io
20•trangram•7h ago•17 comments

Apocalypse Early Warning System

https://ews.kylemcdonald.net/
215•carlsborg•20h ago•99 comments

Eka’s robotic claw feels like we're approaching a ChatGPT moment

https://www.wired.com/story/when-robots-have-their-chatgpt-moment-remember-these-pincers/
150•zdw•2d ago•215 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?