frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Gemini 4 Neon

https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-neon/
731•yigitdemirag•10h ago•615 comments

Unauthenticated remote code execution in Nginx

https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
1310•speedping•16h ago•573 comments

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

https://kapteko.com/15-million-webservers/
42•fessguid•1h ago•7 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/
210•runesoerensen•7h ago•68 comments

Seven new models at scalable price-performance

https://microsoft.ai/news/microsoft-ignite-2026/
518•gmays•15h ago•343 comments

Anthropic prices initial public offering

https://www.anthropic.com/news/anthropic-prices-initial-public-offering
162•surprisetalk•8h ago•167 comments

Inside Deutsche Bank

https://www.inside-db.com/
655•gyre007•16h ago•215 comments

Axelera Titania Brings Native FP8 and FP4 to In-Memory Compute

https://futurumgroup.com/insights/axelera-titania-brings-native-fp8-and-fp4-to-in-memory-compute/
21•muxamilian•2d ago•0 comments

LLM assisted reverse engineering

https://www.slowchronicle.com/posts/llm-assisted-reverse-engineering
172•ioma8•9h ago•44 comments

Genie 4 is now available

https://blog.google/innovation-and-ai/models-and-research/google-deepmind/genie-4-now-available-p...
236•leumon•12h ago•161 comments

DaisyRose-27B

https://www.radixark.com/blog/daisyrose-27b
189•de_sty•12h ago•60 comments

Dumping an AES key from a MyQ garage opener to stop rebooting when offline

https://kusha.me/blog/stop_myq_homebridge_819lmb_rebooting/
110•kusha•2d ago•36 comments

Mosquitoes are Ladakh's latest tourists

https://ruralindiaonline.org/article/mosquitoes-are-ladakh-s-latest-tourists
40•akbarnama•1d ago•1 comments

Camera Index

https://www.cameraindex.co.uk/
21•bookofjoe•1d ago•6 comments

Logitech Harmony IR code online database archive

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

Show HN: An API for word timestamps from speech, 75% within 20ms

https://quebec.yarn.so
4•jasperstory•1d ago•0 comments

The Cambridge Dictionary has named ‘human’ as the Word of the Year 2026

https://www.cam.ac.uk/news/cambridge-dictionary-reveals-word-of-the-year-2026
270•DeepLogin•17h ago•195 comments

Unreal Tournament 2004 in the Browser

https://ut2004.dev/
147•TheAceOfHearts•6h ago•63 comments

Palo Alto Networks to Acquire Applied Compute for $4.5B

https://investors.paloaltonetworks.com/news-releases/news-release-details/palo-alto-networks-acqu...
52•alpb•7h ago•11 comments

Advancing chip design with OpenAI models

https://openai.com/index/advancing-chip-design-with-our-models/
200•vighneshiyer•13h ago•130 comments

Show HN: ExitPath – Open-source ways out of Slack, Notion and Microsoft 365

https://exitpath-ruddy.vercel.app/
202•zerocool0101•15h ago•62 comments

F-22 Next-Generation micro–Data Transfer Cartridge (mDTC)

https://sam.gov/workspace/contract/opp/8948e8601e964c6aba9c801eee16b1be/view
167•birdboat00•16h ago•109 comments

We need smart people who give a shit

https://violetpixel.com/blog/2026-11-17-we-need-smart-people-who-give-a-shit/
473•ExMachina73•7h ago•243 comments

Show HN: Take Voyager 1 apart, down to a single memory chip

https://rshekhar.com/voyager/
185•raj-shekhar•15h ago•46 comments

Show HN: Open-source, real-time object tracking for live video feeds

https://github.com/aryamandarda/tamserve
78•aryaman_darda•2d ago•3 comments

Gemini 4 Neon looks like an Opus 5.5 competitor

https://micjm.com/blog/gemini-4-neon-looks-like-a-top-model/
213•seizethecheese•7h ago•67 comments

Cuttlefish on Mac: Android's Virtual Device Framework on Apple Silicon

https://engineering.fb.com/2026/11/13/android/cuttlefish-on-mac/
63•acossta•3d ago•12 comments

AI agents ask better questions than KPMG accountants in audit trial

https://europeanbusinessmagazine.com/ai-agents-better-questions-kpmg/
443•Betelbuddy•15h ago•193 comments

DNS resolvers are the wrong place to fight piracy

https://techstackups.com/articles/quad9-leaves-france-dns-blocking/
653•ritzaco•18h ago•263 comments

The x86 CPU: From 4004 to 486

https://pikuma.com/blog/history-of-x86-4004-to-486
167•ibobev•16h ago•51 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...)