3 ms·

This. I don't want to be in an event loop by default.

• throwawaymaths 3y ago
  Hate to break it to you but in the BEAM you're always in an event loop.
  • ch4s3 3y ago
    No really. The scheduler isn’t really like an event loop. The scheduler will only allow a task so many units of execution before pulling it off the processing queue and scheduling other work. You can block an event loop, but not the scheduler.
    • toast0 3y ago
      Adding preemption doesn't make it not an event loop, IMHO.
      • ch4s3 3y ago
        The context of the discussion was the node event loop, which doesn’t have preemption. The BEAM scheduler is only like an event loop when you’re locked to one physical processor core, otherwise the schedule is spreading work across multiple OS level threads. You could squint and call this an event loop manager with preemption, but I think the phrase “event loop” detracts from the clarity of any correct description.
  • gpderetta 3y ago
    At the limit, there is always an event loop in the kernel. The question is how leaky are the abstractions on top.