frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Carnegie Mellon is putting computer science courses on YouTube for free

https://www.cs.cmu.edu/learn/
838•pcompeau•6h ago•140 comments

Windows 11 Is Collecting Data on Which Coding Agents and Developer Tools You Use

https://xusheng.dev/posts/windows-coding-agent-telemetry/
300•cwaffles•4h ago•168 comments

BugMeNot has closed

https://www.bugmenot.com/
351•lode•5h ago•178 comments

Running coding agents without handing them my credentials

https://blog.antonio.cx/running-agents-with-lend
38•antoniomika•1h ago•8 comments

Optimizely Compromised, Served Malware on Zoom, GitLab

https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/
139•kristjansson•4h ago•76 comments

OpenCode Browse

https://opencode.ai/product/browse
141•mfiguiere•5h ago•62 comments

Mem Is Shutting Down

https://get.mem.ai/blog/mem-is-shutting-down
13•qainsights•54m ago•14 comments

Chemistry is Actually Geometry

https://chillphysicsenjoyer.substack.com/p/chemistry-is-actually-geometry
132•sebg•6h ago•51 comments

How to Break into Security, Ptacek Edition (2012)

https://krebsonsecurity.com/2012/06/how-to-break-into-security-ptacek-edition/
86•ronfriedhaber•4h ago•20 comments

Frame – 31.5" color ePaper display

https://trmnl.com/blog/introducing-frame
323•geerlingguy•10h ago•223 comments

Jiff 1.0: A datetime library for Rust

https://burntsushi.net/jiff/
323•burntsushi•10h ago•76 comments

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

https://support.apple.com/en-us/149699
8•jshier•51m ago•4 comments

Grazing sheep in fields with solar arrays

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

Formal Verification Is Not Verifiable

https://alperenkeles.com/posts/formal-verification-is-not-verifiable/
75•zdw•2d ago•17 comments

Do Repeat Yourself

https://arcentry.com/blog/do-repeat-yourself/
39•max_sendfeld•15h ago•14 comments

Technical issue at JPMorgan Chase triggers online banking delays for US banks

https://apnews.com/article/bank-outage-chase-wells-fargo-truist-50fee2693c22f597fa6ca51a97ef2cda
728•samk3nny•8h ago•602 comments

Show HN: Sutra-OS – A self-hosted ontology platform

https://github.com/0nelight/sutra-os
36•0nelight•3h ago•13 comments

Squircles

https://linebender.org/wiki/curves/squircle/
139•raphlinus•19h ago•42 comments

New open source C4 Diagram tool

https://www.youtube.com/watch?v=ZCAHP50Zly8
21•oliveralbertini•1d ago•5 comments

Rust changed me as a developer

https://blog.startifact.com/posts/how-rust-changed-me/
198•speckx•6h ago•127 comments

Launch HN: Axonnic (YC F26) – Sleeves that track fingers and estimate force

30•arshpatankar•6h ago•10 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...
233•Bender•13h ago•175 comments

United Airlines experiencing a widespread system outage, airline says

https://www.cnn.com/2026/11/16/us/united-airlines-outage
187•bearsyankees•4h ago•98 comments

My Quest to push native Three.js quality match AAA Game Engines

https://ben3d.ca/blog/building-the-aaa-lighting-pipeline-in-threejs
101•bhouston•6h ago•41 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/
300•sammatilda•15h ago•117 comments

Show HN: A free interactive course on AI agent governance

https://studio.sinapsdata.com.br
7•sadrk•56m ago•2 comments

Large Angle Period of the Pendulum

https://jslandy.com/pendulum/
5•efavdb•20h ago•1 comments

Aristotle Expands into Rust

https://www.harmonic.fun/news/aristotle-rust-verification/
107•maufl•9h ago•55 comments

Claude Mythos slashed software work to onboard AMD GPUs to around three days

https://www.tomshardware.com/tech-industry/artificial-intelligence/anthropic-says-claude-mythos-s...
19•nsoonhui•1h ago•2 comments

Pentagon fails ninth straight audit despite progress in organizing finances

https://www.reuters.com/business/aerospace-defense/pentagon-fails-ninth-straight-audit-despite-pr...
51•petethomas•2h ago•10 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...)