frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Toyota, Nissan, and Honda to standardize parts to lower costs

https://www.caranddriver.com/news/a74490092/toyota-nissan-honda-standardize-parts-lower-costs/
596•zdw•7h ago•359 comments

Pill to treat pancreatic cancer hailed as 'biggest breakthrough in decades'

https://www.theguardian.com/society/2026/nov/20/pill-pancreatic-cancer-breakthrough-daraxonrasib
1072•rafaelc•1d ago•226 comments

A real Linux kernel, compiled to WebAssembly

https://github.com/pithings/unkernel
47•DonAtimator•4d ago•9 comments

Harsher on Male? Evaluating LLMs on Gender-Asymmetric Moral Framing in Conflicts

https://arxiv.org/abs/2606.14068
38•rzk•2h ago•11 comments

Lean verification of the Riemann Hypothesis

https://leanprover-community.github.io/blog/posts/riemann-hypothesis/
1065•g-b-r•21h ago•885 comments

Sandwich Simulator

https://stulle.app/
299•subdomain•11h ago•103 comments

Inkling-2-Mini in 5.4 GB Memory

https://github.com/ShinMegamiBoson/lookatmyquant
479•k__•18h ago•120 comments

Self-hosted library branch over public web OPDS

https://joinmayberry.com/
12•philips•2d ago•0 comments

Show HN: The Riemann Proof Handbook

https://github.com/tamnd/riemann-handbook
59•tamnd•6h ago•27 comments

Detonating a pile of lead azide

https://www.science.org/content/blog-post/detonating-huge-pile-lead-azide-really
625•beginning_end•22h ago•391 comments

Data Processing Incidents on Inference Providers

https://openrouter.ai/blog/announcements/data-processing-incidents-on-inference-providers/
173•sdko•9h ago•66 comments

Getting the mind to steer the body to steer you

https://notnottalmud.substack.com/p/getting-the-mind-to-steer-the-body
298•jger15•1d ago•100 comments

Notes on the discrete Fourier transform (DFT)

https://eli.thegreenplace.net/2026/notes-on-the-discrete-fourier-transform-dft/
35•kouosi•5h ago•5 comments

If tiny 'primordial' black holes exist

https://phys.org/news/2026-11-tiny-primordial-black-holes.html
39•wglb•2d ago•17 comments

My monitor was cutting my download speed by 75%

https://blog.tymscar.com/posts/studiodisplayethernet/
600•soheilpro•1d ago•279 comments

Fast-Anything: Don't rewrite it in Rust. Rewrite the 5% that's slow

https://github.com/EL4CTEO/fast-anything
48•BaselAshraf81•7h ago•30 comments

PcapAnalyzer – self-hosted pcap analyzer with 27 problem detectors

https://github.com/sebaandrada-cell/PcapAnalyzer
125•sebaandrada•13h ago•18 comments

Is 'fork' missing operation in sandboxes?

https://avrea.com/blog/avrea-sandboxes-computers-should-be-forkable
9•damezumari•2d ago•6 comments

The Mythology of Conscious AI

https://www.noemamag.com/the-mythology-of-conscious-ai/
80•Anon84•9h ago•166 comments

87% of the Anthropic power will come from gas and 11% from coal in 2028

https://betterdatacenterproject.com/2026/11/16/how-ai-is-powered-a-breakdown-of-byop-and-grid-power/
181•happosai•3h ago•252 comments

Split Radiance Cascades

https://www.jacktollenaar.top/articles/split-rc.html
40•ibobev•2d ago•0 comments

Reversing the Next-Page Prefetcher in Skylake-X

https://devsh0.github.io/microarchitecture,/intel,/computer-architecture/2026/11/17/reversing-the...
13•todsacerdoti•3d ago•0 comments

Advice for the next 100 Rust GUIs

https://linebender.org/blog/next-100-guis/
183•raphlinus•14h ago•78 comments

Pandex – Official European Law for AI Agents, over MCP

https://www.pandex.io
101•vasie•15h ago•25 comments

Upload2Shell (CVE-2026-125396)

https://pwn.ai/upload2shell
127•f311a•17h ago•63 comments

LLMs can read and write executables byte by byte from a hex dump

https://sgiannopoulos.github.io/blog/machine-code-programming/
260•fortran77•3d ago•160 comments

GnuPG Security Advisory for GPGME

https://lists.gnupg.org/pipermail/gnupg-announce/2026q4/000517.html
257•gdgghhhhh•1d ago•106 comments

Hurried Announcement: Alessandro Masullo GRH

https://math216.wordpress.com/2026/11/20/hurried-announcement-alessandro-masullo-grh/
2426•jasondavies•1d ago•1179 comments

Show HN: Compile the same source for GPUs and CPUs

https://github.com/ThrudTheBarbarian/xc
19•spacedcowboy•1w ago•2 comments

PostgreSQL Extensions in Go

https://jespino.github.io/gopgext/
154•valyala•18h ago•25 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...)