frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Claude Opus 4.7

https://www.anthropic.com/news/claude-opus-4-7
1635•meetpateltech•16h ago•1151 comments

Codex for almost everything

https://openai.com/index/codex-for-almost-everything/
795•mikeevans•13h ago•399 comments

CadQuery is an open-source Python library for building 3D CAD models

https://cadquery.github.io/
101•gregsadetsky•2d ago•15 comments

A Python Interpreter Written in Python

https://aosabook.org/en/500L/a-python-interpreter-written-in-python.html
23•xk3•3d ago•5 comments

Guy builds AI driven hardware hacker arm from duct tape, old cam and CNC machine

https://github.com/gainsec/autoprober
147•scaredpelican•8h ago•32 comments

Show HN: SPICE simulation → oscilloscope → verification with Claude Code

https://lucasgerads.com/blog/lecroy-mcp-spice-demo/
56•_fizz_buzz_•5h ago•11 comments

Official Clojure Documentary page with Video, Shownotes, and Links

https://clojure.org/about/documentary
161•adityaathalye•10h ago•43 comments

A Better R Programming Experience Thanks to Tree-sitter

https://ropensci.org/blog/2026/04/02/tree-sitter-overview/
114•sebg•9h ago•11 comments

ReBot-DevArm: open-source Robotic Arm

https://github.com/Seeed-Projects/reBot-DevArm
35•rickcarlino•3d ago•2 comments

Android CLI: Build Android apps 3x faster using any agent

https://android-developers.googleblog.com/2026/04/build-android-apps-3x-faster-using-any-agent.html
194•ingve•11h ago•64 comments

Playdate’s handheld changed how Duke University teaches game design

https://news.play.date/news/duke-playdate-education/
118•Ivoah•11h ago•44 comments

Discourse Is Not Going Closed Source

https://blog.discourse.org/2026/04/discourse-is-not-going-closed-source/
65•sams99•2h ago•24 comments

Substrate AI Is Hiring Harness Engineers

https://www.ycombinator.com/companies/substrate/jobs/QJU9023-harness-engineer
1•kunle•3h ago

A Git helper tool that breaks large merges into parallelizable tasks

https://github.com/mwallner/mergetopus
17•schusterfredl•3d ago•3 comments

Qwen3.6-35B-A3B: Agentic coding power, now open to all

https://qwen.ai/blog?id=qwen3.6-35b-a3b
1014•cmitsakis•16h ago•440 comments

Bluesky has been dealing with a DDoS attack for nearly a full day

https://www.theverge.com/tech/913638/bluesky-has-been-dealing-with-a-ddos-attack-for-nearly-a-ful...
34•dotmanish•2h ago•16 comments

Cloudflare's AI Platform: an inference layer designed for agents

https://blog.cloudflare.com/ai-platform/
264•nikitoci•17h ago•60 comments

US Bill Mandates On-Device Age Verification

https://reclaimthenet.org/us-bill-mandates-on-device-age-verification
75•ronsor•3h ago•23 comments

Everything we like is a psyop?

https://techcrunch.com/2026/04/16/everything-we-like-is-a-psyop/
200•evo_9•7h ago•119 comments

New unsealed records reveal Amazon's price-fixing tactics, California AG claims

https://www.theguardian.com/us-news/ng-interactive/2026/apr/16/amazon-price-fixing-california-law...
190•kmfrk•8h ago•39 comments

The future of everything is lies, I guess: Where do we go from here?

https://aphyr.com/posts/420-the-future-of-everything-is-lies-i-guess-where-do-we-go-from-here
571•aphyr•16h ago•612 comments

30 Years of HPC: many hardware advances, little adoption of new languages

https://chapel-lang.org/blog/posts/30years/
9•matt_d•3d ago•0 comments

Launch HN: Kampala (YC W26) – Reverse-Engineer Apps into APIs

https://www.zatanna.ai/kampala
85•alexblackwell_•15h ago•65 comments

GPT‑Rosalind for life sciences research

https://openai.com/index/introducing-gpt-rosalind/
86•babelfish•10h ago•22 comments

Qwen3.6-35B-A3B on my laptop drew me a better pelican than Claude Opus 4.7

https://simonwillison.net/2026/Apr/16/qwen-beats-opus/
369•simonw•12h ago•77 comments

The beginning of scarcity in AI

https://tomtunguz.com/ai-compute-crisis-2026/
41•gmays•9h ago•66 comments

Artifacts: Versioned storage that speaks Git

https://blog.cloudflare.com/artifacts-git-for-agents-beta/
184•jgrahamc•17h ago•20 comments

FCC exempts Netgear from ban on foreign routers, doesn't explain why

https://arstechnica.com/tech-policy/2026/04/fcc-exempts-netgear-from-ban-on-foreign-routers-doesn...
20•rawgabbit•2h ago•4 comments

Human Accelerated Region 1

https://en.wikipedia.org/wiki/Human_accelerated_region_1
15•apollinaire•2h ago•0 comments

Show HN: Marky – A lightweight Markdown viewer for agentic coding

https://github.com/GRVYDEV/marky
58•GRVYDEV•14h ago•28 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?