Adam Parkhomenkowho made this
Krystian Kopeć
- 8 Followers
- 65 Following
- 282 Posts
@Migueldeicaza I agree. As long as you push most of the code into services/view models (or any kind of code separated from the view) and make the view lean and dumb, the overhead of having multiple platform-specific views should be small. I’d definitely prefer to go this way in the era of LLM instead of having non-native cross-platform frameworks.
kravietz 🦇Interesting case from #CERN where #Russia team leaving the project sabotaged continued operations of the module they delivered by refusing to supply documentation on its operations, thus threatening continuity of the project:
When CERN definitively ended its cooperation with Russia, engineers were left with Russian equipment for which complete documentation was lacking. Shutting down the equipment threatened to paralyse the key ALICE experiment. That’s when the Poles stepped in, figured out how the Russian equipment worked, reverse engineered it, and not only saved the project, but became key players in the Large Hadron Collider. Krystian Rosłon from the Warsaw University of Technology revealed the details of this incredible operation to the PAP Nauka news agency.
Source: https://spidersweb.pl/2026/02/rosjanie-cern-odejscie-polacy-zlamali.html (in Polish)
@stroughtonsmith now make a similar poll about SwiftUI/UIKit 😜
@simonbs I think you can write this quite easily in AppKit. I generally prefer using SwiftUI for views but for my latest project I simply gave up and created a NSSplitViewcontroller with hosting controllers and unified toolbar. Worked like a charm, gave me a lot of customisation options and was much more reliable than NavigationSplitView.
@alexozun @mattiem I agree that paying down existing technical debt will become easier than ever. At the same time, the opposite is also true: it will be easier than ever to accumulate it. Without proper guardrails, the amount of technical debt introduced by AI will scale directly with the volume of code it generates.
@stroughtonsmith @mjtsai Well, the writing was on the wall for quite a long time. At my day job, we moved away from Combine a while ago and are much better for it. Instead we use much simpler solutions: async await, delegates and closures. Ultimately they are much more testable, scalable and approachable. One of the biggest mistakes we have ever made was trying to shoehorn Combine everywhere. But when you have a hammer, everything becomes a nail. So they say.
Robert Reich
Steve Troughton-SmithClear indicator that Apple's DMA implementation never actually met its obligations under the DMA in the first place. Apple scared developers away from ever signing up to their poison pill Core Technology Fee terms, so alternative app stores simply have no apps to offer.
The pretense of avoiding 'political retaliation' from the US when the US is openly discussing invading and conquering EU member territory is utter nonsense. Fine Apple what they should be fined
https://www.macrumors.com/2026/01/15/setapp-mobile-eu-app-store-closing-next-month/
