frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

LLMs are eroding my software engineering career and I don't know what to do

https://human-in-the-loop.bearblog.dev/llms-are-eroding-my-software-engineering-career-and-i-dont...
321•poisonfountain•2h ago•249 comments

The OnlyFans Economy of American AI

https://leoveanu.com/2026-06-06-qwen3.7max/
7•futurisold•13m ago•0 comments

Anthropic, please ship an official Claude Desktop for Linux

https://github.com/anthropics/claude-code/issues/65697
137•predkambrij•1h ago•54 comments

The 29th International Obfuscated C Code Contest (IOCCC) 2025 Winners

https://www.ioccc.org/2025/
275•matt_d•9h ago•64 comments

Yon – a topos-oriented language with a content-addressed lattice heap

https://yon-lang.org/
28•amenn•2d ago•12 comments

Win16 Memory Management

http://www.os2museum.com/wp/win16-memory-management/
90•supermatou•2d ago•46 comments

Show HN: Kyushu – A self-hostable WASM sandbox for JavaScript workers

https://kyushu.dev/
22•le_chuck•7h ago•15 comments

Show HN: Lathe – Use LLMs to learn a new domain, not skip past it

https://github.com/devenjarvis/lathe
31•devenjarvis•3h ago•2 comments

Speculative KV coding: losslessly compressing KV cache by up to ~4×

https://fergusfinn.com/blog/kv-entropy-coder/
104•kkm•2d ago•15 comments

Netlify CTO Dana Lawson: Writing code is no longer the job

https://thenewstack.io/netlify-agent-experience-engineers/
16•Brajeshwar•44m ago•11 comments

My Software North Star

https://kristoff.it/blog/north-star/
147•kristoff_it•3d ago•81 comments

9 Mothers (YC P26) Is Hiring

https://9mothers.com/careers
1•ukd1•3h ago

Field of clones: How horse replicas came to dominate polo

https://knowablemagazine.org/content/article/technology/2026/cloned-polo-horses
125•gscott•12h ago•56 comments

Valve P2P networking broken for more than 2 months

https://github.com/ValveSoftware/GameNetworkingSockets/issues/398
220•babuskov•11h ago•103 comments

Public Domain Image Archive

https://pdimagearchive.org/
180•davidbarker•14h ago•26 comments

Ntsc-rs – open-source video emulation of analog TV and VHS artifacts

https://ntsc.rs/
373•gregsadetsky•19h ago•112 comments

How Long Does It Take for a QQuickItem to Become Visible?

https://www.kdab.com/how-long-does-it-take-for-an-item-to-become-visible/
13•jandeboevrie•2d ago•0 comments

The best relationships are all-encompassing.

https://andys.blog/the-best-relationships/
12•andytratt•3h ago•4 comments

Symbolica 2.0: Programmable Symbols for Python and Rust

https://symbolica.io/posts/symbolica_2_0_release/
110•mmastrac•1d ago•10 comments

Tokenomics: Quantifying Where Tokens Are Used in Agentic Software Engineering

https://arxiv.org/abs/2601.14470
134•Anon84•13h ago•58 comments

The Secret Life of Circuits with lcamtuf / Michał Zalewski (Audio Interview)

https://theamphour.com/725-the-secret-life-of-circuits-with-lcamtuf-michal-zalewski/
25•ChrisGammell•3d ago•4 comments

Partitions over Permutations

https://www.johndcook.com/blog/2026/06/04/partitions-over-permutations/
3•ibobev•1d ago•0 comments

Warren's Abstract Machine: A Tutorial Reconstruction

https://github.com/a-yiorgos/wambook
27•nextos•1d ago•4 comments

Biohub releases a world model of protein biology

https://biohub.org/news/world-model-of-protein-biology/
115•gmays•3d ago•17 comments

Harness engineering: Leveraging Codex in an agent-first world

https://openai.com/index/harness-engineering/
251•pramodbiligiri•1d ago•169 comments

How Liminalism Became the Defining Aesthetic of Our Time

https://hyperallergic.com/how-liminalism-became-the-defining-aesthetic-of-our-time/
112•zeech•12h ago•62 comments

Arithmetic Without Numbers – How LLMs Do Math

https://alvaro-videla.com/llm-arithmetic-internals/article_interactive/article.html
65•old_sound•2d ago•16 comments

Moving beyond fork() + exec()

https://lwn.net/SubscriberLink/1076018/16f01bbbb8e0d1f0/
326•jwilk•1d ago•312 comments

Introducing Boron Buckyballs: Theory that B80 cages can’t be made is disproved

https://cen.acs.org/materials/nanomaterials/buckyballs-boron-buckminster-fullerene-nanomaterials/...
106•crescit_eundo•2d ago•30 comments

Efficient and Training-Free Single-Image Diffusion Models

https://arxiv.org/abs/2606.04299
22•yorwba•5h ago•0 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?