frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Reputation Scores for GitHub Accounts

https://shkspr.mobi/blog/2026/02/reputation-scores-for-github-accounts/
1•edent•3m ago•0 comments

A BSOD for All Seasons – Send Bad News via a Kernel Panic

https://bsod-fas.pages.dev/
1•keepamovin•6m ago•0 comments

Show HN: I got tired of copy-pasting between Claude windows, so I built Orcha

https://orcha.nl
1•buildingwdavid•6m ago•0 comments

Omarchy First Impressions

https://brianlovin.com/writing/omarchy-first-impressions-CEEstJk
1•tosh•12m ago•0 comments

Reinforcement Learning from Human Feedback

https://arxiv.org/abs/2504.12501
2•onurkanbkrc•12m ago•0 comments

Show HN: Versor – The "Unbending" Paradigm for Geometric Deep Learning

https://github.com/Concode0/Versor
1•concode0•13m ago•1 comments

Show HN: HypothesisHub – An open API where AI agents collaborate on medical res

https://medresearch-ai.org/hypotheses-hub/
1•panossk•16m ago•0 comments

Big Tech vs. OpenClaw

https://www.jakequist.com/thoughts/big-tech-vs-openclaw/
1•headalgorithm•19m ago•0 comments

Anofox Forecast

https://anofox.com/docs/forecast/
1•marklit•19m ago•0 comments

Ask HN: How do you figure out where data lives across 100 microservices?

1•doodledood•19m ago•0 comments

Motus: A Unified Latent Action World Model

https://arxiv.org/abs/2512.13030
1•mnming•19m ago•0 comments

Rotten Tomatoes Desperately Claims 'Impossible' Rating for 'Melania' Is Real

https://www.thedailybeast.com/obsessed/rotten-tomatoes-desperately-claims-impossible-rating-for-m...
3•juujian•21m ago•2 comments

The protein denitrosylase SCoR2 regulates lipogenesis and fat storage [pdf]

https://www.science.org/doi/10.1126/scisignal.adv0660
1•thunderbong•23m ago•0 comments

Los Alamos Primer

https://blog.szczepan.org/blog/los-alamos-primer/
1•alkyon•25m ago•0 comments

NewASM Virtual Machine

https://github.com/bracesoftware/newasm
2•DEntisT_•27m ago•0 comments

Terminal-Bench 2.0 Leaderboard

https://www.tbench.ai/leaderboard/terminal-bench/2.0
2•tosh•28m ago•0 comments

I vibe coded a BBS bank with a real working ledger

https://mini-ledger.exe.xyz/
1•simonvc•28m ago•1 comments

The Path to Mojo 1.0

https://www.modular.com/blog/the-path-to-mojo-1-0
1•tosh•31m ago•0 comments

Show HN: I'm 75, building an OSS Virtual Protest Protocol for digital activism

https://github.com/voice-of-japan/Virtual-Protest-Protocol/blob/main/README.md
5•sakanakana00•34m ago•1 comments

Show HN: I built Divvy to split restaurant bills from a photo

https://divvyai.app/
3•pieterdy•36m ago•0 comments

Hot Reloading in Rust? Subsecond and Dioxus to the Rescue

https://codethoughts.io/posts/2026-02-07-rust-hot-reloading/
3•Tehnix•37m ago•1 comments

Skim – vibe review your PRs

https://github.com/Haizzz/skim
2•haizzz•38m ago•1 comments

Show HN: Open-source AI assistant for interview reasoning

https://github.com/evinjohnn/natively-cluely-ai-assistant
4•Nive11•39m ago•6 comments

Tech Edge: A Living Playbook for America's Technology Long Game

https://csis-website-prod.s3.amazonaws.com/s3fs-public/2026-01/260120_EST_Tech_Edge_0.pdf?Version...
2•hunglee2•42m ago•0 comments

Golden Cross vs. Death Cross: Crypto Trading Guide

https://chartscout.io/golden-cross-vs-death-cross-crypto-trading-guide
3•chartscout•45m ago•1 comments

Hoot: Scheme on WebAssembly

https://www.spritely.institute/hoot/
3•AlexeyBrin•48m ago•0 comments

What the longevity experts don't tell you

https://machielreyneke.com/blog/longevity-lessons/
2•machielrey•49m ago•1 comments

Monzo wrongly denied refunds to fraud and scam victims

https://www.theguardian.com/money/2026/feb/07/monzo-natwest-hsbc-refunds-fraud-scam-fos-ombudsman
3•tablets•54m ago•1 comments

They were drawn to Korea with dreams of K-pop stardom – but then let down

https://www.bbc.com/news/articles/cvgnq9rwyqno
2•breve•56m ago•0 comments

Show HN: AI-Powered Merchant Intelligence

https://nodee.co
1•jjkirsch•58m ago•0 comments
Open in hackernews

Backpressure in Distributed Systems

https://blog.pranshu-raj.me/posts/backpressure/
43•andection•3mo ago

Comments

adamzwasserman•3mo ago
Off topic: a guaranteed way to start a flame war in an automotive forum is to state that there is no such thing as "backpressure" and that fluid dynamics and the continuity equation fully explain why restricting exhaust pipe diameter results in increased performance.

Light the fire and then sit back and enjoy.

pryelluw•3mo ago
It gets even more fun when the back pressure is in the intake side (aka boost). I was tuning a friends turbo 300zx after he upgraded to a bigger turbo. At the same boost levels as before the car was slower. He was confused. After a quick chat around turbos, air speed, etc., I simply told him we needed to crank up the boost. Some tweaks to timing and fuel maps and this thing could now really fly.
01HNNWZ0MV43FF•3mo ago
I wanna tell them how torque vs horsepower isn't real, horsepower is all that matters unless your transmission sucks

(Not to say that the width of the power band doesn't matter)

mikert89•3mo ago
I feel like backpressure was a common topic in 2010, and now modern event driven system design just naturally handles this issue.
convolvatron•3mo ago
its still pretty easy to screw up. how does the system you're using handle back pressure and how does that behavior affect other parts of your system. if you have two systems that each do back pressure, are you certain that the system remains closed? that is if those systems aren't coupled implicitly through the scheduler or explicitly in some other way, then you can balloon state or drop results between them.
titanomachy•3mo ago
Not all modern systems are event-driven. The large-scale systems I've worked on have plenty of RPC.
cyberax•3mo ago
Backpressure applies to regular request-based systems just as well.

As in: should your request handler try to do retries if one of the dependent services fails?

normalaccess•3mo ago
I recall this in the form of buffer bloat.
supportengineer•3mo ago
I want to believe
PaulKeeble•3mo ago
I have often found limiting the buffer size as a simple way to communicate back to producers that more work can't be taken. Then what happens is all a producer strategy to drop work or wait for a period of time then drop or just hold onto the work until the buffer has a clear space. Its about the simplest message from consumer to producer you can do and how games tend to do backpressure and how Go channels work.
pranshu-raj-211•3mo ago
Can you give examples of which games have implemented this (if open source) for reference?
PaulKeeble•3mo ago
It is how DirectX works. The call to present that ends the stream of the commands to the GPU and tells it to render causes the CPU to be stalled waiting for this to be possible. This causes a backpressure into the game engine as the next simulation can't start or at the very least the next frame can't be started to be processed until it returns. It has been used by GPU makers to frame pace games as well to avoid stuttering.

So its not just some games, its all games its part of the core of how DX works.

pranshu-raj-211•3mo ago
Hi, author of above blog here.

Thanks for posting, I'm glad you found this interesting.

Would be glad to know any feedback or requests you have, to improve further.

jbn•3mo ago
This whole topic seems to be a re-discovery of https://en.wikipedia.org/wiki/Control_theory and https://en.wikipedia.org/wiki/System_dynamics with non-linearities and saturation.

In the same vein, on the consumer side we talk of admission control (which is just another name for "drop incoming messages") and throttling...