frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Usborne 1980s Computer Books

https://usborne.com/us/books/computer-and-coding-books
21•ngram•1h ago•8 comments

DeepSeek reasonix, DeepSeek native coding agent with high caching and low cost

https://esengine.github.io/DeepSeek-Reasonix/
136•Alifatisk•3h ago•79 comments

Omarchy Is Not A Distro

https://abyss.fish/your_dotfiles_are_not_a_distro
59•j3s•2h ago•36 comments

Mastering Dyalog APL

https://mastering.dyalog.com/README.html
83•tosh•5h ago•18 comments

Constraint Decay: The Fragility of LLM Agents in Back End Code Generation

https://arxiv.org/abs/2605.06445
50•wek•3h ago•29 comments

Childhood Computing

https://susam.net/childhood-computing.html
90•blenderob•4h ago•47 comments

I spent 50 hours drawing a line graph

https://www.dougmacdowell.com/50-hours-to-draw-some-lines.html
256•dougdude3339•3d ago•42 comments

Ruby for Good

https://ti.to/codeforgood/rubyforgood
4•mooreds•54m ago•0 comments

I keep bouncing off the Scheme language

https://www.sicpers.info/2026/05/i-keep-bouncing-off-the-scheme-language/
70•ingve•2d ago•26 comments

Microsoft open-sources "the earliest DOS source code discovered to date"

https://arstechnica.com/gadgets/2026/04/microsoft-open-sources-the-earliest-dos-source-code-disco...
360•DamnInteresting•15h ago•114 comments

Perceptual Image Codec: What Matters in Practical Learned Image Compression

https://apple.github.io/ml-pico/
34•ksec•4h ago•8 comments

'AI washing': firms are scrambling to rebrand themselves as tech-focused

https://www.theguardian.com/technology/2026/may/24/ai-washing-pr-firms-scrambling-rebrand
32•Brajeshwar•1h ago•25 comments

Scammers are abusing an internal Microsoft account to send spam links

https://techcrunch.com/2026/05/21/scammers-are-abusing-an-internal-microsoft-account-to-send-spam/
212•spike021•15h ago•115 comments

Wake up! 16b

https://hellmood.111mb.de/wake_up_16b_writeup.html
341•MaximilianEmel•16h ago•25 comments

Curly braces: An evolution of Unix and C

https://thalia.dev/blog/unix-braces/
13•thaliaarchi•3d ago•3 comments

When (if ever) it's appropriate to make jokes before the US Supreme Court

https://www.scotusblog.com/2026/05/when-if-ever-its-appropriate-to-make-jokes-take-selfies-or-cur...
21•mooreds•56m ago•1 comments

Swap tables, flash-friendly swap, swap_ops, and more

https://lwn.net/SubscriberLink/1072657/394b87abd7cc215e/
47•mkesper•4d ago•0 comments

Silk: Open-source cooperative fiber scheduler

https://github.com/ClickHouse/silk
79•animetyan•3d ago•11 comments

The C64 Dead Test Font

https://www.masswerk.at/nowgobang/2026/c64-dead-test-font
100•masswerk•12h ago•17 comments

Predicting the 2026 Bristol Bay and Kodiak Salmon Runs

https://www.salmonfinder.com/2026/05/13/bristol-bay-kodiak-predictions-2026
6•mooreds•2d ago•2 comments

Alexander Grothendieck Revolutionized 20th-Century Mathematics

https://www.quantamagazine.org/how-alexander-grothendieck-revolutionized-20th-century-mathematics...
101•anujbans•13h ago•22 comments

Time to talk about my writerdeck

https://veronicaexplains.net/my-first-writerdeck/
426•hggh•21h ago•252 comments

Converting an Integer to a Decimal String in Under Two Nanoseconds

https://onlinelibrary.wiley.com/doi/10.1002/spe.70079
88•mpweiher•5d ago•43 comments

DeepSeek to Make Permanent 75% Discount on Flagship AI Model

https://www.bloomberg.com/news/articles/2026-05-23/deepseek-to-make-permanent-75-discount-on-flag...
72•moh_maya•2h ago•78 comments

On The <dl> (2021)

https://benmyers.dev/blog/on-the-dl/
419•ravenical•1d ago•124 comments

Artificial egg hatched 26 healthy chickens

https://www.nationalgeographic.com/science/article/artificial-egg-colossal-chickens-moa-dodo
43•BaudouinVH•3d ago•66 comments

Show HN: Git-based front-end interface for Hugo

https://github.com/arashthr/hugo-flow
26•arashThr•3d ago•6 comments

Why is Vivado 2026.1 dropping Linux support for free tier?

https://adaptivesupport.amd.com/s/question/0D5Pd00001YQLdMKAX/why-is-vivado-20261-dropping-linux-...
259•zdw•12h ago•144 comments

Greg Brockman interview [video]

https://fs.blog/knowledge-project-podcast/greg-brockman/
132•prakashqwerty•8h ago•109 comments

My two-part desk setup (2025)

https://arslan.io/2025/11/18/my-two-part-desk-setup/
326•James72689•3d ago•200 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?