frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Codeberg.org Not Reachable

https://social.anoxinon.de/@codebergstatus/117636437840688845
133•hans_castorp•1h ago•68 comments

Java4Shell: RCE in OpenJDK when processing Base64

https://calif.io/java4shell/
964•werrett•14h ago•246 comments

Google's AI answers reducing search traffic by 40%

https://revscope.co/blog/search-seo-geo-2026/
425•slashdev•11h ago•311 comments

ID.me terms required for IRS sign-in

https://consumerrights.wiki/w/ID.me_terms_required_for_IRS_sign-in
371•DeepLogin•10h ago•166 comments

Quad9's withdrawal from France: A canary in the coal mine

https://blog.cloudflare.com/quad9-withdrawal-from-france/
634•subset•13h ago•221 comments

Energy-Based Reasoners: 385x more efficient inference

https://energy-based-reasoners.github.io/
19•frenchmajesty•2h ago•2 comments

Nvidia stopped disclosing Singapore sales as revenues hit $104B

https://www.ft.com/content/dbde7a30-548c-4f9d-a4be-7898a0c24dcf
558•louiereederson•18h ago•249 comments

Why is Gemini 4 Carbon taking so long?

https://kernel.dev/blog/why-is-gemini-4-carbon-taking-so-long/
110•deenadz•7h ago•54 comments

Talos Linux

https://www.siderolabs.com/talos-linux
48•SweetSoftPillow•3h ago•22 comments

Microsoft's ONNX Runtime has disappeared from GitHub

https://github.com/microsoft/onnxruntime
340•nvader•12h ago•73 comments

Highly classified US national security communications network goes down

https://www.cnn.com/2026/11/17/politics/highly-classified-national-security-communications-networ...
593•monkeydust•19h ago•679 comments

Archive Team is archiving the Apple Support Community

https://wiki.archiveteam.org/index.php/Apple_Discussions
201•digitaldragon•11h ago•72 comments

AI is killing All About Berlin

https://nicolasbouliane.com/blog/death-by-ai
375•grey-area•4h ago•346 comments

Claude was trained on protein sequences at scale

http://xinmingtu.cn/blog/2026/claude-opus-5-5-protein-sequences/
66•gmays•7h ago•26 comments

My Emacs 31 contributions

https://xenodium.com/my-emacs-31-contributions
17•xenodium•1d ago•0 comments

350 years ago, Ole Rømer discovered that light has a finite speed

https://www.sciencenorway.no/culture-history-history-of-science/350-years-ago-this-man-discovered...
339•dxs•16h ago•108 comments

MAI Code 2 and Code 2 Flash

https://microsoft.ai/news/introducing-mai-code-2-and-mai-code-2-flash/
367•lemonish97•17h ago•155 comments

jQuery 4.1.0

https://github.com/jquery/jquery/releases/tag/4.1.0
329•petecooper•15h ago•167 comments

Phrack 73

https://phrack.org/issues/73/introduction_md
390•notmine1337•16h ago•53 comments

Harvard researchers find AI coding agents shifted the bottleneck to code review

https://complexdiscovery.com/harvard-researchers-find-ai-coding-agents-shifted-the-bottleneck-to-...
193•judahmeek•14h ago•270 comments

Why Fibonacci?

https://www.evilgeniuslabs.org/why-fibonacci
39•_Microft•5h ago•5 comments

Australia's full national topographic library at your fingertips

https://www.ga.gov.au/news/australias-full-national-topographic-library-at-your-fingertips
23•bryanrasmussen•4h ago•11 comments

GPT‑6.2 Astra and Sol

https://openai.com/index/introducing-gpt-6-2-astra-sol/
1283•jasondavies•17h ago•798 comments

Solid 2.0

https://www.solidjs.com/blog/solid-2-0-the-long-hold/
319•pier25•16h ago•98 comments

Launch HN: StarSling (YC P25) – Self-improving CI for agent-volume repos

81•yonasb•16h ago•39 comments

Show HN: Unref – A Python dead code finder built on Ruff's parser

https://github.com/Apakottur/unref
31•McAvey•1d ago•5 comments

What is the best harness for each model?

https://runta.com/blog/introducing-frontierharness-eval-v1-1/
379•Edward40•20h ago•128 comments

Cerebras Disaggregated Inference

https://www.cerebras.ai/blog/cerebras-launches-disaggregated-inference
85•emschwartz•10h ago•19 comments

Fun with Constrained Programming (2012)

https://blog.cmpxchg8b.com/2012/09/fun-with-constrained-programming.html
76•colejohnson66•3d ago•3 comments

Flattening Every Memory Peak in Long-Context Mixture-of-Experts Training

https://arxiv.org/abs/2609.14306
5•gmays•3d ago•1 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...)