frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

How the European Commission rolled out Matrix to more than 40k staff

https://element.io/blog/how-the-european-commission-rolled-out-matrix-to-more-than-40-000-staff/
331•liotier•3h ago•142 comments

Garage Door Spam

https://blog.harrison.page/garage-door-spam/
217•harrisonpage•2d ago•76 comments

PHP 8.5.13

https://www.php.net/ChangeLog-8.php
16•petecooper•26m ago•9 comments

Making 8-page foldable zines from a single A4 sheet in the browser

https://krthr.co/paper-folds-and-whats-new-in-fanzines-app/
44•krthr•1h ago•12 comments

Nintendo takes Picofly firmware down from GitHub [video]

https://www.youtube.com/watch?v=-TLCGUpoD6c
98•cowlevel•23h ago•19 comments

Show HN: Foolscap – a writing app that reads your book and never writes for you

https://foolscap.works/
25•atugard•1h ago•9 comments

Ruby2ßhell: Pre-authentication RCE on stock Rails

https://verialabs.com/ruby2shell/
255•jdns•9h ago•97 comments

We taught robots to carve marble sculptures

https://eleanorwiesler.com/blog/robotic-stone-carving/
51•ewiesler•21h ago•35 comments

What's New in PHP 8.6

https://www.php.net/releases/8.6/en.php
162•netol•5h ago•82 comments

Distributed, high-performance blob storage on SQLite

https://zerodha.tech/blog/high-performance-distributed-blob-storage/
139•ghostfoxgod•5h ago•26 comments

Oregon library dropped Dewey Decimal system, adopted bookstore-like arrangement

https://www.fastcompany.com/91597520/oregon-library-ditched-dewey-decimal-wayfinding-system
56•bookofjoe•1d ago•48 comments

Gemini 4 Neon

https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-neon/
914•yigitdemirag•17h ago•713 comments

Mass launched to orbit each year by rocket builder

https://www.kadoa.com/companies/insights/spacex-europe-payload
52•hubraumhugo•1d ago•31 comments

Two stealth models just appeared on the leaderboard, both ahead of Fable 5.2

https://contralabs.com/frontierdesign
58•cheptsov•3h ago•14 comments

SSD prices will start going down the second half of next year

https://www.drivevault.io/blog/when-will-hard-drive-prices-come-down.html
181•illidan1000•5h ago•152 comments

Unauthenticated remote code execution in Nginx

https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
1454•speedping•23h ago•612 comments

Exponential Behavior in Magic: The Gathering

https://levineuwirth.org/essays/exponential-magic/
33•neuwirth•1d ago•11 comments

C's designated initializers give us named arguments

https://quuxplusone.github.io/blog/2026/11/16/named-arguments-in-c/
22•joshcsimmons•1d ago•14 comments

15M web servers on one VM – smoltcp, DPDK, AF_XDP

https://kapteko.com/15-million-webservers/
255•fessguid•8h ago•30 comments

Unblockable communication with gravity – Science Advances

https://www.science.org/doi/10.1126/sciadv.aee0802
25•rbanffy•2h ago•9 comments

Someone reported java4shell bug in September 2026

https://github.com/openjdk/jdk/pull/32781
34•notmine1337•2h ago•4 comments

Multiple vulnerabilities in Regexp and String case conversion

https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/
304•runesoerensen•14h ago•112 comments

Anthropic prices initial public offering

https://www.anthropic.com/news/anthropic-prices-initial-public-offering
323•surprisetalk•15h ago•599 comments

Funkycache: A Python library to cache functions in SQLite

https://alexwlchan.net/2026/funkycache/
4•wmchen•2d ago•0 comments

Seven new models at scalable price-performance

https://microsoft.ai/news/microsoft-ignite-2026/
574•gmays•22h ago•361 comments

Inside Deutsche Bank

https://www.inside-db.com/
741•gyre007•22h ago•246 comments

The first ping from Tonga (1997)

https://colo.to/firstping.html
61•Eric_Gullichsen•3d ago•6 comments

LLM assisted reverse engineering

https://www.slowchronicle.com/posts/llm-assisted-reverse-engineering
275•ioma8•16h ago•69 comments

Logitech Harmony IR code online database archive

https://github.com/pickysysadmin/logitech-harmony-ir-archive
62•cf100clunk•2d ago•14 comments

Building Lego Machines to Destroy Tall Lego Towers (2024)

https://kottke.org/24/07/building-lego-machines-to-destroy-tall-lego-towers
26•sammatilda•1d ago•4 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...)