frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

In 27,280 coding agent runs, 64% of inference spend went to runs that failed

https://runta.com/blog/introducing-frontierharness-eval-v1-1/
82•Edward40•1h ago•28 comments

New Evidence Shows School Phone Bans Are Gradually Improving Test Scores

https://www.nytimes.com/2026/11/17/upshot/school-phone-bans-study-scores.html
707•donohoe•4h ago•356 comments

First Photos of the Poles of a Rod-Shaped Bacterium

https://nautil.us/check-out-the-first-photos-of-the-poles-of-a-rod-shaped-bacterium-1286664
62•dustfinger•1d ago•13 comments

Show HN: Alloy CSS, dialogs, menus and tabs that work with JavaScript off

https://alloyhtml.com/example.html
51•prafandy•1h ago•11 comments

Carnegie Mellon is putting computer science courses on YouTube for free

https://www.cs.cmu.edu/learn/
2047•pcompeau•20h ago•274 comments

Highly classified US national security communications network goes down

https://www.cnn.com/2026/11/17/politics/highly-classified-national-security-communications-networ...
117•monkeydust•1h ago•86 comments

VisualBasic.World: A gallery of Planet Source Code programs from 1997 to 2012

https://visualbasic.world/
163•broast•1d ago•59 comments

Loopholes Are for Assholes

https://actsofvolition.com/2026/11/loopholes-are-for-assholes/
135•speckx•2h ago•116 comments

We don't need more apps. We need better open source

https://jordankrueger.com/blog/better-open-source-not-more-apps/
240•pandemicsoul•1h ago•145 comments

Optimizely compromised, served malware on Zoom, GitLab

https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/
549•kristjansson•17h ago•219 comments

Turbo Pascal Compiler Written in Turbo Pascal

https://turbo51.com/compiler-design/tpc16-turbo-pascal-compiler-written-in-turbo-pascal
70•andsoitis•1d ago•27 comments

Rows vs. Columns: How different are they, really?

https://spiraldb.com/blog/rows-vs-columns
97•eatonphil•4d ago•36 comments

BugMeNot has closed

https://www.bugmenot.com/
671•lode•19h ago•306 comments

NSA Internal Network Down

https://www.reuters.com/technology/highly-classified-us-national-security-communications-network-...
29•nodoodles•53m ago•10 comments

Nimony: A New Compiler for Nim

https://nimony.org/
142•Fervicus•1d ago•66 comments

Show HN: VennDB: append-only in-memory Rust DB for rows queried using bit flags

https://github.com/plabayo/venndb
23•gdcbe•1d ago•1 comments

If an App Asks for Full Disk Access or System and App Protection Override

https://support.apple.com/en-us/149699
199•jshier•14h ago•106 comments

How the Claude Code team thinks about verification

https://claude.dev/blog/how-the-claude-code-team-thinks-about-verification/
135•craigmart•6h ago•135 comments

Mistral offers three months of Vibe Pro free in Europe

https://x.com/MistralAI/status/2122713540666806397
12•DavCreator•28m ago•10 comments

Why 3dfx 1 cards had such a washed out color output?

https://twitter.com/id_aa_carmack/status/2122478083319992513
242•mfiguiere•16h ago•88 comments

Elephant-Goldfish Model

https://egm.dev/
4•_tk_•1d ago•1 comments

Chemistry is Actually Geometry

https://chillphysicsenjoyer.substack.com/p/chemistry-is-actually-geometry
300•sebg•20h ago•129 comments

Comcast's "fiber-powered Wi-Fi" is cable, AT&T says in false advertising case

https://arstechnica.com/tech-policy/2026/11/comcast-falsely-advertises-cable-internet-as-fiber-po...
218•jaredwiener•19h ago•191 comments

Frame – 31.5" color ePaper display

https://trmnl.com/blog/introducing-frame
499•geerlingguy•1d ago•364 comments

Microsoft blames monster email outage on software defect introduced in July fix

https://www.theregister.com/saas/2026/11/16/microsoft-blames-monster-email-outage-on-software-def...
418•Bender•1d ago•308 comments

Jiff 1.0: A datetime library for Rust

https://burntsushi.net/jiff/
423•burntsushi•23h ago•91 comments

Baidu, Xiaomi CEOs warn of growing gap between AI hype and returns

https://www.scmp.com/tech/big-tech/article/3374774/baidu-xiaomi-ceos-warn-growing-gap-between-ai-...
140•larrysalibra•2h ago•169 comments

Japan's Hometown Tax (2018)

https://www.kalzumeus.com/2018/10/19/japanese-hometown-tax/
107•waximabbax•1d ago•62 comments

Grazing sheep in fields with solar arrays

https://news.cornell.edu/stories/2026/10/sheep-grazing-solar-fields-offers-farmers-economic-ecolo...
313•PaulHoule•23h ago•316 comments

What is w2rt6byl5nf1opmc-a.com?

https://jack.cab/blog/siterate
392•dverlaeckt80•1d ago•155 comments
Open in hackernews

The Scalar Select Anti-Pattern

https://matklad.github.io/2025/05/14/scalar-select-aniti-pattern.html
47•goranmoomin•1y ago

Comments

castratikron•1y ago
As long as processing one event does not affect any of the other events in the batch. E.g. events are file IO, and processing one event causes another event's descriptor to get closed before that event can be processed.
wahern•1y ago
If the close routine on an event source, or the low-level (e.g. epoll) registration, deregistration, and dequeueing logic doesn't know how to keep polling and liveness state consistent between userspace and the kernel, they've got much bigger problems. This looks like Rust code so I would hope the event stream libraries are, e.g., keeping Rc'd file objects and properly managing reference integrity viz-a-viz kernel state before the application caller ever sees the first dequeued event in a cycle. This is a perennial issue with event loop libraries and buggy application code (in every language). One can't just deal with raw file descriptors, call the close syscall directly, etc, hoping to keep state consistent implicitly. There's an unavoidable tie-in needed between application's wrappers around low-level resources and the event loop in use.
taeric•1y ago
I'm not entirely clear on what the proposal is at the end? Seems that the long term answer as to "which of these implications to pursue" is "all of them?" Simply taking in a batch of instructions doesn't immediately change much? You still have to be able to do each of the other things. And you will still expect some dependencies between batches that could possibly interact in the same ways.

In a sense, this is no different than how your processor is dealing with instructions coming in. You will have some instructions that can be run without waiting on previous ones. You will have some that can complete quickly. You will have some that are stalled on other parts of the system. (I'm sure I could keep wording an instruction to match each of the implications.)

To that end, part of your program has to deal with taking off "whats next" and finding how to prepare that to pass to the execution portion of your program. You can make that only take in batches, but you are almost certainly responsible for how you chunk them moreso than whatever process is sending the instructions to you? Even if you are handed clear batches, it is incumbent on you to batch them as they go off to the rest of the system.

lmz•1y ago
I guess the proposal is "instead of fetching and acting on one event at a time, consider fetching all available events and look for opportunities to optimize which ones you process (e.g. by prioritization or by skipping certain events if superseded by newer ones)".
taeric•1y ago
I mean, I got that. But you could as easily say "instead of fetching and acting on one event at a time, fetch and triage/route instructions into applicable queues."

In particular, there is no guarantee that moving to batches changes any of the problems you may have from acting on a single one at a time. To that end, you will have to look into all of the other strategies sooner or later.

Following from that, the problem is not "processMessage" or whatever. The problem is that you haven't broken "processMessage" up into the constituent "receive/triage/process/resolve" loop that you almost certainly will have to end up with.

malkia•1y ago
in CPU's - pipelining!
jchw•1y ago
I believe something similar is going on internally in Windows with event queues. It coalesces and prioritizes input events when multiple of them pile up before you're able to pop new events off of the queue. (For some events, e.g. pointer events, you can even go and query frames that were coalesced during input handling.) On the application/API end, it just looks like a "scalar select" loop, but actually it is doing batching behavior for input events!

(On the flip side, if you have a Wayland client that falls behind on processing its event queue, it can crash. On the whole this isn't really that bad but if you have something sending a shit load of events it can cause very bad behavior. This has made me wonder if it's possible, with UNIX domain sockets, to implement some kind of event coalescing on the server-side, to avoid flooding the client with high-precision pointer movement events while it's falling behind. Maybe start coalescing when FIONREAD gets to some high watermark? No idea...)