Server-side Swift State Of The Union By Tim Condon

Поделиться
HTML-код
  • Опубликовано: 8 сен 2024
  • Server-side Swift State Of The Union By Tim Condon
    This talk takes a step back and looks at how server-side Swift is doing.
    We'll cover the recent changes due to async/await, how it compares to other languages and what the future holds.
    About our speaker
    Tim is a Swift developer from Manchester, UK and part of the Vapor Core Team. He's the server-side Swift team lead at raywenderlich.com and has written the unofficial-official book on Vapor with the founders of the framework.
    He founded Broken Hands a few years ago and delivers talks and workshops on Vapor and server-side Swift around the world.
    He also co-organises the ServerSide.swift conference - the world’s first and only conference focused on server-side Swift.
    Event details: www.meetup.com...
    This recording is also available on our PeerTube: watch.softinio...

Комментарии • 3

  • @pookiepats
    @pookiepats 4 месяца назад

    This presentation gave me the confidence in Swift I needed

  • @petersuvara
    @petersuvara Год назад

    Cannot believe I missed this! Need to save and watch during the week.

  • @eyesonly4451
    @eyesonly4451 Год назад +2

    I started work in 2018 on a Swift REST service built atop SwiftNIO. The service performs complex 3D structural analyses on large systems. Since many structural elements can be solved independently, Grand Central Dispatch queues were used to keep all cores saturated with computational work.
    I say *_GCD queues were_* because I eventually converted my original code from GCD to the new async/await paradigm. This proved to be far more difficult and less rewarding than I first imagined because (1) it meant flushing years of GCD experience and finely tuned code, and (2) the handoff from NIO's promise/future paradigm to the async/await model is not elegant.
    The whole experience has left me feeling that the juice was not worth the squeeze, and also that the current state of NIO is somewhat long in the tooth at this point. Can we anticipate an updated async/await version of NIO at some point?