frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

LLM from scratch, part 28 – training a base model from scratch on an RTX 3090

https://www.gilesthomas.com/2025/12/llm-from-scratch-28-training-a-base-model-from-scratch
85•gpjt•6d ago•10 comments

The Joy of Playing Grandia, on Sega Saturn

https://www.segasaturnshiro.com/2025/11/27/the-joy-of-playing-grandia-on-sega-saturn/
58•tosh•2h ago•14 comments

Show HN: AlgoDrill – Interactive drills to stop forgetting LeetCode patterns

https://algodrill.io
18•henwfan•1h ago•2 comments

No ARIA is better than bad ARIA

https://www.w3.org/WAI/ARIA/apg/practices/read-me-first/
72•robin_reala•6d ago•35 comments

A deep dive into QEMU: The Tiny Code Generator (TCG), part 1

https://airbus-seclab.github.io/qemu_blog/tcg_p1.html
14•costco•6d ago•0 comments

Epsilon: A WASM virtual machine written in Go

https://github.com/ziggy42/epsilon
60•ziggy42•1w ago•16 comments

Icons in Menus Everywhere – Send Help

https://blog.jim-nielsen.com/2025/icons-in-menus/
591•ArmageddonIt•16h ago•246 comments

The universal weight subspace hypothesis

https://arxiv.org/abs/2512.05117
297•lukeplato•11h ago•104 comments

Kroger acknowledges that its bet on robotics went too far

https://www.grocerydive.com/news/kroger-ocado-close-automated-fulfillment-centers-robotics-grocer...
185•JumpCrisscross•12h ago•165 comments

Brent's Encapsulated C Programming Rules (2020)

https://retroscience.net/brents-c-programming-rules.html
3•p2detar•52m ago•1 comments

Manual: Spaces

https://type.today/en/journal/spaces
70•doener•12h ago•7 comments

Jepsen: NATS 2.12.1

https://jepsen.io/analyses/nats-2.12.1
376•aphyr•17h ago•138 comments

Strong earthquake hits northern Japan, tsunami warning issued

https://www3.nhk.or.jp/nhkworld/en/news/20251209_02/
324•lattis•21h ago•148 comments

Microsoft increases Office 365 and Microsoft 365 license prices

https://office365itpros.com/2025/12/08/microsoft-365-pricing-increase/
399•taubek•22h ago•464 comments

AMD GPU Debugger

https://thegeeko.me/blog/amd-gpu-debugging/
256•ibobev•20h ago•46 comments

Has the cost of building software dropped 90%?

https://martinalderson.com/posts/has-the-cost-of-software-just-dropped-90-percent/
304•martinald•17h ago•443 comments

Launch HN: Nia (YC S25) – Give better context to coding agents

https://www.trynia.ai/
118•jellyotsiro•18h ago•75 comments

Horses: AI progress is steady. Human equivalence is sudden

https://andyljones.com/posts/horses.html
438•pbui•11h ago•344 comments

Let's put Tailscale on a jailbroken Kindle

https://tailscale.com/blog/tailscale-jailbroken-kindle
292•Quizzical4230•19h ago•69 comments

A thousand-year-long composition turns 25 (2024)

https://longplayer.org/news/2024/12/31/a-thousand-year-long-composition-turns-25/
26•1659447091•5h ago•5 comments

Trials avoid high risk patients and underestimate drug harms

https://www.nber.org/papers/w34534
132•bikenaga•17h ago•40 comments

IBM to acquire Confluent

https://www.confluent.io/blog/ibm-to-acquire-confluent/
407•abd12•22h ago•325 comments

Paramount launches hostile bid for Warner Bros

https://www.cnbc.com/2025/12/08/paramount-skydance-hostile-bid-wbd-netflix.html
331•gniting•21h ago•344 comments

The Lost Machine Automats and Self-Service Cafeterias of NYC (2023)

https://www.untappedcities.com/automats-cafeterias-nyc/
79•walterbell•11h ago•24 comments

Hunting for North Korean Fiber Optic Cables

https://nkinternet.com/2025/12/08/hunting-for-north-korean-fiber-optic-cables/
260•Bezod•19h ago•95 comments

Periodic Spaces

https://ianthehenry.com/posts/periodic-spaces/
26•surprisetalk•5d ago•8 comments

Cassette tapes are making a comeback?

https://theconversation.com/cassette-tapes-are-making-a-comeback-yes-really-268108
105•devonnull•5d ago•175 comments

AI should only run as fast as we can catch up

https://higashi.blog/2025/12/07/ai-verification/
175•yuedongze•18h ago•152 comments

Show HN: Fanfa – Interactive and animated Mermaid diagrams

https://fanfa.dev/
119•bairess•4d ago•26 comments

Microsoft Download Center Archive

https://legacyupdate.net/download-center/
171•luu•3d ago•26 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•6mo ago

Comments

balloob•6mo 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•6mo ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•6mo ago
Comments moved thither. Thanks!
pabs3•6mo ago
They are two different articles, I don't think that was correct.
tomhow•6mo 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•6mo ago
Thanks for the response, guess that makes sense.
pabs3•6mo 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?