BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.all-systems-go.io//all-systems-go-2025//VFBWNK
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-all-systems-go-2025-8WW7YH@cfp.all-systems-go.io
DTSTART;TZID=CET:20250930T112500
DTEND;TZID=CET:20250930T115000
DESCRIPTION:Communication is paramount in modern application development. T
 his applies equally well to the process of writing applications and to the
  code itself. The complexity of the tasks ahead of us calls for a distribu
 ted and coordinated development effort\, and this often manifests in our c
 ode: We design distributed\, communicating systems to split complexity and
  responsibility among many people and teams\, and at the same time meet th
 e demand for ever faster systems.\n\nThe last decade showed significantly 
 increased popularity in API design\, network protocols\, and distributed c
 omputations. At the same time some of the most intriguing language researc
 h improves how multi-threaded applications synchronize and exchange inform
 ation without sacrificing safety or performance. Between these two lies an
  almost forgotten world: Linux Inter-process communication (IPC) has lost 
 ground to thread-communication and networking protocols.\n\nLet us look at
  how other operating systems have evolved their IPC layers\, what new syst
 ems decide to go with\, and why Linux IPC has not seen any major changes s
 ince the 90s. And finally\, can we lift Linux IPC out of stagnation and ca
 tch up with everyone else?
DTSTAMP:20260315T014322Z
LOCATION:Galerie
SUMMARY:Linux IPC: Lost between Threading and Networking - David Rheinsberg
URL:https://cfp.all-systems-go.io/all-systems-go-2025/talk/8WW7YH/
END:VEVENT
END:VCALENDAR