frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Grazing sheep in fields with solar arrays

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

Outages reported at Bank of America, Chase, U.S. Bank, Wells Fargo and Zelle

https://apnews.com/article/bank-outage-chase-wells-fargo-truist-50fee2693c22f597fa6ca51a97ef2cda
43•samk3nny•47m ago•14 comments

Jiff 1.0: A datetime library for Rust

https://burntsushi.net/jiff/
147•burntsushi•2h ago•37 comments

The Secret ThinkPad Powerbutton Code to Bring Dead Laptops Back to Life (2007)

https://masnick.com/posts/the-secret-thinkpad-powerbutton-code-to-bring-dead-laptops-back-to-life/
249•sammatilda•7h ago•99 comments

Aristotle Expands into Rust

https://www.harmonic.fun/news/aristotle-rust-verification/
36•maufl•1h ago•14 comments

Frame – 31.5" color ePaper display

https://trmnl.com/blog/introducing-frame
61•geerlingguy•2h ago•27 comments

Michael Mann's 'Heat' Copyright Fight Turns on a Deal with Himself

https://copyrightlately.com/michael-mann-heat-copyright-termination/
26•speckx•1h ago•3 comments

Many of Amazon’s Black Friday and Cyber Monday “deals” offered no savings

http://groundworkcollaborative.org/news/amazons-decoy-deals-groundwork-investigation-reveals-near...
615•DeepLogin•5h ago•383 comments

How to make almost anything

https://pub.cba.mit.edu/863.26/site/
753•o4c•13h ago•126 comments

Jolt – Clojure that speaks C

https://jolt-lang.net/
27•michaelsbradley•2h ago•7 comments

Just 400 US Data Centers Use More Electricity Than Michigan

https://www.wired.com/story/data-centers-use-more-electricity-than-michigan/
37•Betelbuddy•1h ago•24 comments

Universal XSS in uBlock Origin from website-driven element picker

https://iter.ca/post/ubo-uxss/
576•zaik•17h ago•163 comments

Smallest possible nopert polyhedra: the Septopert

https://github.com/tom7/noperts/blob/main/septopert.md
30•RebelPotato•2d ago•2 comments

Interpreting claims that a theorem is correct because it was checked in Lean

https://xenaproject.wordpress.com/2026/11/12/and-the-proof-is-checked-in-lean/
241•matt_d•11h ago•106 comments

OOS – an open operating system for the Rigol Scopes

https://www.eevblog.com/forum/testgear/oos-an-open-operating-system-for-the-rigol-scopes/
104•qwezxcrty•2d ago•33 comments

The Active Directory Era Is Finally Over

https://infisical.com/blog/active-directory-machine-identity
77•FinnLobsien•5h ago•49 comments

Software is breaking down at a systemic level

https://www.breck-mckye.com/blog/2026/11/software-is-breaking-down-at-a-systemic-level/
87•zero_shift•1h ago•76 comments

Show HN: Fakemetrics.com – "build in public" like a superstar

https://fakemetrics.com/
13•tigranbs•1h ago•0 comments

Giant Roadside Attractions Face Mounting Costs and an Uncertain Future

https://www.nytimes.com/2026/11/08/world/canada/roadside-attractions-giant-dinosaur.html
3•bookofjoe•6d ago•3 comments

A 512 KiB binary message teaching chess without a shared language

https://artemlegotin.com/golden-board/
25•legotin•4h ago•4 comments

Qwen4-Max

https://qwen.ai/blog?id=qwen4-max
828•ilreb•17h ago•438 comments

What's Next for Nvidia?

https://steveblank.com/2026/11/15/whats-next-for-nvidia/
433•zdw•19h ago•552 comments

Researchers track whole body movement with just a smartwatch

https://news.cornell.edu/stories/2026/11/researchers-track-whole-body-movement-just-smartwatch
173•PaulHoule•3d ago•61 comments

Quxnet Is a Breath of Fresh Air

https://moddedbear.com/quxnet-is-a-breath-of-fresh-air/
10•surprisetalk•4d ago•4 comments

Old Bitly links are being hijacked

https://ransomnews.com/burger-king-tweet-bitly-link-hijack-2026/
368•hspeiser•21h ago•195 comments

Winudf – DVD / BluRay driver for DOS, Windows 1.x – 3x / 95 / 98 / ME

https://github.com/ages2001/WINUDF
74•Oxodao•11h ago•12 comments

Protomaps: Self-hosting map tiles has gotten cheap and easy

https://bruceroettgers.eu/blog/protomaps/
450•bcye•23h ago•81 comments

Tor Project Issues Rapid-Response DoS-Defense Fix Amid Sustained DDoS Attack

https://forum.torproject.org/t/security-release-0-4-9-17/22454
236•aillia•18h ago•62 comments

Handwriting, as a Font

https://ductus.sorenblank.com
441•coinfused•23h ago•73 comments

Coffeehouses and the Rise of Science [pdf]

https://www.monirbounadi.com/Bounadi_JMP.pdf
157•Michelangelo11•8h ago•95 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...)