frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Chemistry behind the Garden Grove chemical tank

https://www.science.org/content/blog-post/methyl-methacrylate-tank
205•nooks•5h ago•83 comments

A few interesting modern pixel fonts

https://unsung.aresluna.org/a-few-interesting-modern-pixel-fonts/
229•zdw•1d ago•51 comments

I Bypassed Adobe and Microsoft to Build a Git-Tracked Book Production Pipeline

https://www.djspeckhals.com/posts/2026-05-22-how-i-bypassed-adobe-and-microsoft-to-build-a-git-tr...
150•dustin1114•4d ago•36 comments

Agent Memory: An Anatomy

https://brgsk.xyz/agent-memory-anatomy/
14•brgsk•27m ago•2 comments

Cloudflare Flagship

https://developers.cloudflare.com/flagship/
16•tjek•1h ago•4 comments

C array types are weird

https://anselmschueler.com/blogposts/2025-c-pointers/
49•signa11•1d ago•23 comments

A portentous reunion

https://bcantrill.dtrace.org/2026/05/25/a-portentous-reunion/
38•cafkafk•18h ago•13 comments

Big tech's anti-labor playbook has come for Wikipedia

https://medium.com/@jakeorlowitz/wikipedia-is-doing-the-capitalist-thing-56a393232943
252•cdrnsf•4h ago•134 comments

Rosalind: A genomics toolkit in Rust running whole-genome pipelines on a laptop

https://github.com/logannye/rosalind
119•samuell•5d ago•29 comments

Spain blocks prediction markets Polymarket, Kalshi over lack of gambling licence

https://www.reuters.com/business/spain-blocks-prediction-markets-polymarket-kalshi-over-lack-gamb...
754•thm•11h ago•343 comments

The Steinwinter Supercargo

https://www.thedrive.com/article/12603/the-forgotten-steinwinter-supercargo-is-unlike-anything-on...
38•itronitron•3d ago•6 comments

Dropbox CEO Drew Houston to step down

https://www.cnbc.com/2026/05/26/dropbox-ceo-drew-houston-ashraf-alkarmi.html
277•aghuang•11h ago•316 comments

Liverpool and Manchester Railway

https://en.wikipedia.org/wiki/Liverpool_and_Manchester_Railway
6•daverol•2d ago•1 comments

The real cost of owning a home

https://ericturner.dev/posts/cost-of-home-ownership/
259•ggcr•8h ago•585 comments

Launch HN: Minicor (YC P26) – Windows desktop automations at scale

https://www.minicor.com/
69•fchishtie•9h ago•46 comments

The Ballad of TIGIT

https://www.owlposting.com/p/the-ballad-of-tigit
92•crescit_eundo•8h ago•17 comments

What color is your function? (2015)

https://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/
90•tosh•8h ago•106 comments

C64 Basic: Game Map Overhead “Camera View”

https://retrogamecoders.com/overhead-camera-view/
74•ibobev•10h ago•10 comments

Show HN: Rapel – chunked resumable downloads in unstable networks

https://github.com/redraw/rapel
4•autorun•21h ago•1 comments

Sage Care (YC S24) Is Hiring Software Engineers

https://www.ycombinator.com/companies/sagecare/jobs/xtloH8r-senior-software-engineer
1•ian-gillis•7h ago

Sonny Rollins, Jazz's Saxophone Colossus and Greatest Improvisor, Dead at 95

https://www.rollingstone.com/music/music-news/sonny-rollins-jazz-legend-saxophone-colossus-dead-o...
10•boarsofcanada•42m ago•0 comments

Use boring languages with LLMs

https://jry.io/writing/use-boring-languages-with-llms/
165•evakhoury•4d ago•137 comments

Outsourcing plus local AI will soon become more economical vs. frontier labs

https://www.signalbloom.ai/posts/outsourcing-plus-localai-will-soon-become-more-economical-vs-fro...
238•GodelNumbering•12h ago•257 comments

Opaque Types in Python

https://blog.glyph.im/2026/05/opaque-types-in-python.html
111•lumpa•3d ago•49 comments

Are we self-sovereign PKI yet?

https://buffrr.dev/blog/are-we-self-sovereign-pki-yet/
72•ca98am79•5d ago•44 comments

The worst job interview I ever had

https://www.oliverio.dev/blog/the-worst-job-interview-i-had
132•oliverio•4h ago•110 comments

Netherlands blocks US takeover of vital digital supplier

https://www.politico.eu/article/netherlands-blocks-us-takeover-vital-digital-supplier/
521•vrganj•12h ago•206 comments

Phantasy Star IV – 1993 Developer Interviews

https://shmuplations.com/phantasystariv/
132•speckx•4d ago•55 comments

DeepSWE: A contamination-free benchmark for long-horizon coding agents

https://deepswe.datacurve.ai/blog
26•ammar_x•5h ago•8 comments

The user is visibly frustrated

https://pscanf.com/s/354/
273•croes•20h ago•242 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?