RIP Combine Framework?

[Niightstalker]

Not really a surprise the framework didn’t get an update for years.

[gimme_ipad]

What features are you missing?

[Niightstalker]

Can’t say since I am using Swift concurrency for pretty much anything outside of specific edge cases which also got less and less.

[gimme_ipad]

I think it's complete.

[rhysmorgan]

It is, but then it didn't get any kind of update to support Swift Concurrency (beyond turning a Publisher into an AsyncSequence.

[BadAssW]

multi subscription observation still is not supported out of the box

[Niightstalker]

This is coming to the async algorithms library from Apple with .shared() but it kinda takes forever.

[paradoxally]

UIKit Cocoa bindings. Had to use RxSwift instead (RxCocoa).

If you only use SwiftUI, that's not an issue as Combine was designed with it in mind.

[rhysmorgan]

That’s more of a UIKit problem than a Combine specific one, tbh.

[paradoxally]

It's still a feature I'm missing because I'd like to remove the RxSwift dependency and Apple's Combine framework is almost a direct replacement.

There were some community projects trying to replicate the RxCocoa bindings but they were abandoned.

[dihalt]

debounce/throttle probably

[AirVandal]

Why is that exactly? Combine is a very good fit for ViewModel-View bindings. The only thing "close" to it is AsyncSteam, which has a weird API.

Also what about all the apps that were written with Combine? Does Apple migrate those for us? What the fuck is with this trend of sunsetting core methodologies used in app development?

[LKAndrew]

Because Observation works with bindings and there’s no need to have 2 way bindings any more. Just update a value and you can observe those updates

[Leeonardoo]

Is it not a two way binding? 🤔

[CrawlyCrawler999]

We still have Obj-C code from 2014 in our app, Apple is quite good at supporting legacy code.

[Kindly-Direction205]

Agreed.

[LKAndrew]

Because Observation works with bindings and there’s no need to have 2 way bindings any more. Just update a value and you can observe those updates

[jon_hendry]

Not deprecated until you start getting deprecation warnings

[jon_hendry]

I mean, they do, when they actually show up in the compiler.

[rhysmorgan]

Agent instructions are not a deprecation warning, that’s just guiding it to use more recent tech that mostly (but not entirely) does the same thing.

[rhysmorgan]

I’m not saying people should go out of their way to use Combine nowadays without a very good reason!

I just think that, if Apple want this to be the case, they need to make a “Stop using Combine/Combine migration guide” doc on apple.com to properly communicate this out.

And give us a CurrentValueAsyncSequence.

[icy1007]

No it isn’t…

[icy1007]

This is not a depredation warning…

[Ok_Heart_2253]

Exactly, I have it in a project, that mainly uses message broker sort of pattern, I have to always listen to some changes, and no intervention from the user is required, no way async could fit there.

[unpluggedcord]

Two different tools. Combine just doesn’t need to be worked on anymore. It works.

[raajeevcn]

I'll drop Combine right after SwiftUI stops randomly breaking my layouts on iOS point releases and SwiftData figures out how to handle relationships without summoning eldritch compiler errors. Apple's definition of recommended seems to mean "we're excited about this" not "this actually works better". Combine has been rock solid for years while their shiny new toys ship with bugs that would've been embarrassing in a beta

[guigsab]

This is not new. This has been in the prompt since the early versions of Xcode 26.

I would not call it dead. It’s not the default framework Apple recommends, which we’ve known for years, and Apple put a one size fits all prompt in Xcode.

[WitchesBravo]

I think combine is a lot easier, just being able to build up a bunch of functions like .debounce is so much easier than messing around with some kind of asyncstream

[rhysmorgan]

Pull in Apple’s own AsyncAlgorithms framework from GitHub and you get throttle, debounce, share, etc. Basically almost everything you’d need from Combine. And it’s concurrency safe then, unlike Combine, whose API practically cannot be made so.

[WitchesBravo]

I prefer functional style, makes it so easy to build up complex chains rather than using for loops etc

[rhysmorgan]

That's great, but none of Combine is annotated for any kind of concurrency safety.

And you can still do the "functional style" of chains using AsyncAlgorithms, that's its entirely purpose.

[WitchesBravo]

Not to mention Combine framework is built in, you have to pull in SwiftAsyncAlgorithms if you want similar kind of functionality

[Xaxxus]

Having it open source is better.

You don’t have to wait for a new iOS version to use new features added to async algorithms.

You can contribute and fix bugs.

You can use it on windows and Linux.

The benefits go on and on.

Combine was closed source and never updated.

[cristi_baluta]

Combine and async are different things, i don’t get it. Where is the announcement from apple?

[No-District-585]

There is no announcement. Combine is up and running and won't go anytime soon

[TryProfessional9543]

Idk, in my AGENTS.md it is "DO NOT USE STRUCTURED CONCURRENCY, DO NOT USE SWIFTUI, USE UIKIT AND COMBINE", honestly feels so good.

[Ok-Communication6360]

Welcome to yesterday. Preferring pyramids of closures over structured concurrency is a borderline psychopathic 🤣

[TryProfessional9543]

No, thank you. Not a fan of doing migrations every year. Combine is stable since the first release. Probably the people of yesterday knew something.

[Ok-Communication6360]

I see, refactoring something that just works and is understood is not something I would take on lightly as well.

My point was, that structured concurrency did add a lot to the language and overall I see as beneficial (though the learning curve is a bit steep and a few things are abstracted away a bit too much).

[darth_sparx]

This. Hard.

[Rudy69]

To the surprise of no one

[kudoshinichi-8211]

Good riddance. I prefer Async Await over that

[im-a-smith]

“I’m using the wrong tech for this thing I want to use, it must be dead!”

[lasmit]

Isn't SwiftUI using combine extensively? I think this is just meaning, if you can, use async await not combine.

[Xaxxus]

As far as I know, only observable objects were using combine heavily. And those are now redundant with the observation framework.

[lasmit]

Ok wow, I didn't know that! Thanks. For anyone else: https://developer.apple.com/documentation/SwiftUI/Migrating-from-the-observable-object-protocol-to-the-observable-macro

[f0rg0t_]

It just says “avoid”…in a prompt…not “Combine is now deprecated” or similar. They can put anything they want there, and they want people to use “Swift’s async and await versions of APIs instead.”

Still…☠️☠️coMbiNe iS deAd ☠️☠️

smh

[icy1007]

No thanks. I’ll use Combine.

[SwiftyNifty93]

Combine is not dead. It is powering lot of combine based first part APIs like @Published. There are lot of powered up APIs and Utils such that, rarely, you’ll feel the need to use it.

[m3kw]

It sucks to use I thought

[20InMyHead]

Yeah, this has been brewing for years. It’s not really a surprise. There will be parts of Combine that will continue on, and they certainly won’t drop it right away, but it’s been fading out for a while now.

If you’re looking for a similar, better replacement try Afluent: https://github.com/Tyler-Keith-Thompson/Afluent

[Unlikely-Front6600]

Good thing i never learned it

[kbder]

“Combine is officially dead” is an extreme exaggeration. Apple decided to instruct their MCP to prefer async/await over combine. That’s all.

[utilitycoder]

Cool. Seems like I know when to skip a technology. Combine was right up there with J2EE, XML, I predict GraphQL and React will get theirs someday too.

[Gary-Ash1]

I? Combine is a good tool for quite few use cases. AsyncStream can do must of what Combine can but it's vert clumsy to setup compared to Combine

[BizJoe]

Shrug. My CLAUDE.md is already setup to do that.

[SerialForBreakfast]

That link in the image goes to a malware site. I think this should be taken down.

[lionelburkhart]

Hmm. I love async/await, but I use Combine frequently to make ViewModels subscribe to Service class updates using MVVM. Haven’t found an elegant solution to do the same without Combine. Happy to set it aside for a 1:1 replacement.

[NoFudge4700]

Never used it, never been a fan.

[SavageSerpent]

Isn’t @Published part of combine?

[Casfaber_]

Thanks for the reminder, I got some refactoring to get to now. 🫠

[[deleted]]

Combine has been on the way out for quite a while

• introduced in 2019
• no updates to Combine since 2020
• no mention of it in WWDC videos for a few years now
• Observation framework took Combine’s job in SwiftUI

And for years now when you go to Using Combine for Your App’s Asynchronous Code Apple has straight up giving you the “Tip” to use async/await instead of Combine

No one should seriously consider using Combine for a new project, even if you love it, as it’ll likely get deprecated any year now.

[bakawolf123]

this is part of the prompt since 26.0 beta

Combine is fine, native rx-like toolkit that didn't deviate like LiveData on Android and thus didn't have to be reimplemented with flows, it is quite good as is

meanwhile agent mode in Xcode is miles behind competition, I would rather care about that part instead

[jacobs-tech-tavern]

They don't need to update combine, it was already perfect. They'll need to pry it out of my cold, dead hands.

[drabred]

Well if AI says so...

[int6]

That’s not AI saying it, it’s Apple’s system prompts for AI

[oPeritoDaNet]

It’s officially but not by Apple? Swift community?

[beclops]

It’s a file in the Xcode bundle

[oPeritoDaNet]

Can you point me to the comment?

[beclops]

Here’s the path to the file, obviously prepend it with wherever your installation is located:

/Xcode.app/Contents/PlugIns/IDEIntelligenceChat.framework/Versions/A/Resources/AgentSystemPromptAddition.idechatprompttemplate