home.social

#rxswift — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rxswift, aggregated by home.social.

fetched live
  1. Sins of Carthage: #RxSwift Re-Entrancy, Undetected christiantietze.de/posts/2025/

    I mixed ReSwift (which doesn't mind if you dispatch an action that updates the state from within a subscription) with RxSwift (to manage observable subscription lifetimes) in a naive way -- and only now got the bill handed to me.

    Reentrancy!

  2. Sins of Carthage: #RxSwift Re-Entrancy, Undetected christiantietze.de/posts/2025/

    I mixed ReSwift (which doesn't mind if you dispatch an action that updates the state from within a subscription) with RxSwift (to manage observable subscription lifetimes) in a naive way -- and only now got the bill handed to me.

    Reentrancy!

  3. Sins of Carthage: #RxSwift Re-Entrancy, Undetected christiantietze.de/posts/2025/

    I mixed ReSwift (which doesn't mind if you dispatch an action that updates the state from within a subscription) with RxSwift (to manage observable subscription lifetimes) in a naive way -- and only now got the bill handed to me.

    Reentrancy!

  4. Sins of Carthage: #RxSwift Re-Entrancy, Undetected christiantietze.de/posts/2025/

    I mixed ReSwift (which doesn't mind if you dispatch an action that updates the state from within a subscription) with RxSwift (to manage observable subscription lifetimes) in a naive way -- and only now got the bill handed to me.

    Reentrancy!

  5. Sins of Carthage: #RxSwift Re-Entrancy, Undetected christiantietze.de/posts/2025/

    I mixed ReSwift (which doesn't mind if you dispatch an action that updates the state from within a subscription) with RxSwift (to manage observable subscription lifetimes) in a naive way -- and only now got the bill handed to me.

    Reentrancy!

  6. I still believe that Reactive Extensions (as in: #rxswift) were a great idea, and that Combine is an amazing 1st party framework, and that async/await is not cutting it

  7. I still believe that Reactive Extensions (as in: #rxswift) were a great idea, and that Combine is an amazing 1st party framework, and that async/await is not cutting it

  8. I still believe that Reactive Extensions (as in: #rxswift) were a great idea, and that Combine is an amazing 1st party framework, and that async/await is not cutting it

  9. I still believe that Reactive Extensions (as in: #rxswift) were a great idea, and that Combine is an amazing 1st party framework, and that async/await is not cutting it

  10. I still believe that Reactive Extensions (as in: #rxswift) were a great idea, and that Combine is an amazing 1st party framework, and that async/await is not cutting it

  11. I've been using #RxSwift for a couple of years. Anything that's really complex, like combining multiple streams, then thottling them by uniquing parts of one stream, is not *that* straightforward and easy to understand and follow.

    All of programming is hard, no matter the tool.

  12. I've been using #RxSwift for a couple of years. Anything that's really complex, like combining multiple streams, then thottling them by uniquing parts of one stream, is not *that* straightforward and easy to understand and follow.

    All of programming is hard, no matter the tool.

  13. I've been using #RxSwift for a couple of years. Anything that's really complex, like combining multiple streams, then thottling them by uniquing parts of one stream, is not *that* straightforward and easy to understand and follow.

    All of programming is hard, no matter the tool.

  14. I've been using #RxSwift for a couple of years. Anything that's really complex, like combining multiple streams, then thottling them by uniquing parts of one stream, is not *that* straightforward and easy to understand and follow.

    All of programming is hard, no matter the tool.

  15. I've been using #RxSwift for a couple of years. Anything that's really complex, like combining multiple streams, then thottling them by uniquing parts of one stream, is not *that* straightforward and easy to understand and follow.

    All of programming is hard, no matter the tool.

  16. #Swift concurrency question:

    Do y'all migrate #RxSwift view-updating closures (e.g. RxCocoa.Binder's blocks) to MainActor-isolated closures, or do you do something different entirely?

  17. #Swift concurrency question:

    Do y'all migrate #RxSwift view-updating closures (e.g. RxCocoa.Binder's blocks) to MainActor-isolated closures, or do you do something different entirely?

  18. #Swift concurrency question:

    Do y'all migrate #RxSwift view-updating closures (e.g. RxCocoa.Binder's blocks) to MainActor-isolated closures, or do you do something different entirely?

  19. #Swift concurrency question:

    Do y'all migrate #RxSwift view-updating closures (e.g. RxCocoa.Binder's blocks) to MainActor-isolated closures, or do you do something different entirely?

  20. #Swift concurrency question:

    Do y'all migrate #RxSwift view-updating closures (e.g. RxCocoa.Binder's blocks) to MainActor-isolated closures, or do you do something different entirely?

  21. Marco Sanna zeigt in seinem Vortrag "Von UIKit zu SwiftUI - Eine Refactoring Reise" auf der #Macoun23 am Beispiel einer aktiv genutzten Produktivapp, wie eine komplexe Änderung der Architektur ohne Einschränkungen für Benutzer und Entwicklungsteam umgesetzt werden kann.

    Sei dabei: macoun.de/anmelden

    #SwiftUI #Storyboards #RxSwift #CleanArchitecture #AsyncAwait #macounFFM

  22. Marco Sanna zeigt in seinem Vortrag "Von UIKit zu SwiftUI - Eine Refactoring Reise" auf der #Macoun23 am Beispiel einer aktiv genutzten Produktivapp, wie eine komplexe Änderung der Architektur ohne Einschränkungen für Benutzer und Entwicklungsteam umgesetzt werden kann.

    Sei dabei: macoun.de/anmelden

    #SwiftUI #Storyboards #RxSwift #CleanArchitecture #AsyncAwait #macounFFM

  23. Marco Sanna zeigt in seinem Vortrag "Von UIKit zu SwiftUI - Eine Refactoring Reise" auf der #Macoun23 am Beispiel einer aktiv genutzten Produktivapp, wie eine komplexe Änderung der Architektur ohne Einschränkungen für Benutzer und Entwicklungsteam umgesetzt werden kann.

    Sei dabei: macoun.de/anmelden

    #SwiftUI #Storyboards #RxSwift #CleanArchitecture #AsyncAwait #macounFFM

  24. Marco Sanna zeigt in seinem Vortrag "Von UIKit zu SwiftUI - Eine Refactoring Reise" auf der #Macoun23 am Beispiel einer aktiv genutzten Produktivapp, wie eine komplexe Änderung der Architektur ohne Einschränkungen für Benutzer und Entwicklungsteam umgesetzt werden kann.

    Sei dabei: macoun.de/anmelden

    #SwiftUI #Storyboards #RxSwift #CleanArchitecture #AsyncAwait #macounFFM

  25. Marco Sanna zeigt in seinem Vortrag "Von UIKit zu SwiftUI - Eine Refactoring Reise" auf der #Macoun23 am Beispiel einer aktiv genutzten Produktivapp, wie eine komplexe Änderung der Architektur ohne Einschränkungen für Benutzer und Entwicklungsteam umgesetzt werden kann.

    Sei dabei: macoun.de/anmelden

    #SwiftUI #Storyboards #RxSwift #CleanArchitecture #AsyncAwait #macounFFM

  26. Currently refactoring my entire #swift app from #RxSwift to Combine is far more easy than expected. Most painful parts are type safety weirdness (hello CombineLatest!) and tests relying on test scheduler that need some revamp. Oh. By the way, that’s also a nice opportunity to properly split in #SwiftPackage for modularity. Still far from complete but in pretty good shape for now. #iosdev #refactoring

  27. Converted another library to #SwiftPM compatibility.
    github.com/CleanCocoa/Omnibar

    With that, I could likely transition my #RxSwift code to use SPM instead of Carthage.

  28. Converted another library to #SwiftPM compatibility.
    github.com/CleanCocoa/Omnibar

    With that, I could likely transition my #RxSwift code to use SPM instead of Carthage.

  29. Converted another library to #SwiftPM compatibility.
    github.com/CleanCocoa/Omnibar

    With that, I could likely transition my #RxSwift code to use SPM instead of Carthage.

  30. Converted another library to #SwiftPM compatibility.
    github.com/CleanCocoa/Omnibar

    With that, I could likely transition my #RxSwift code to use SPM instead of Carthage.

  31. Converted another library to #SwiftPM compatibility.
    github.com/CleanCocoa/Omnibar

    With that, I could likely transition my #RxSwift code to use SPM instead of Carthage.

  32. Dependency 2/N updated!

    This time a #RxSwift file monitor extension.

    --------------
    🎉 Congrats

    🚀 RxFileMonitor (4.0.0) successfully published
    📅 December 22nd, 16:23
    🌎 cocoapods.org/pods/RxFileMonit
    👍 Tell your friends!

  33. Dependency 2/N updated!

    This time a #RxSwift file monitor extension.

    --------------
    🎉 Congrats

    🚀 RxFileMonitor (4.0.0) successfully published
    📅 December 22nd, 16:23
    🌎 cocoapods.org/pods/RxFileMonit
    👍 Tell your friends!

  34. Dependency 2/N updated!

    This time a #RxSwift file monitor extension.

    --------------
    🎉 Congrats

    🚀 RxFileMonitor (4.0.0) successfully published
    📅 December 22nd, 16:23
    🌎 cocoapods.org/pods/RxFileMonit
    👍 Tell your friends!

  35. Dependency 2/N updated!

    This time a #RxSwift file monitor extension.

    --------------
    🎉 Congrats

    🚀 RxFileMonitor (4.0.0) successfully published
    📅 December 22nd, 16:23
    🌎 cocoapods.org/pods/RxFileMonit
    👍 Tell your friends!

  36. Dependency 2/N updated!

    This time a #RxSwift file monitor extension.

    --------------
    🎉 Congrats

    🚀 RxFileMonitor (4.0.0) successfully published
    📅 December 22nd, 16:23
    🌎 cocoapods.org/pods/RxFileMonit
    👍 Tell your friends!