algrid

@Zhuinden "That was ridiculous! But, of course, what we're doing now is a completely different story!"

If you think you're following some kind of "best practice" that is used by "many developers" and is "agreed upon as best practice" so you know it has to be "the greatest idea of all time no one should ever question it", then: Remember when people thought this was a good idea?

@tsoding Showing off, no other reason 😛

People often ask me why do I choose to do pre-increments in my for-loops instead of post-increments. The answer is actually very simple. I don't fucking know, stop asking me that.

@SamProgramiz @MongoDB Pure SQLite without any ORM(-like) stuff is the best approach ever.

Third party dependencies are a huge liability. Just learnt that @MongoDB dropped support for RealmSwift This is the second critical open source project I depend on that has been killed. I need to schedule time for migration, should have gone with SQLite from the start

@jacobtechtavern Finally some sanity from Apple. UIKit ftw!

Is Apple giving up on SwiftUI? Maybe: Mastodon went wild recently over a rumour shared by Steve Troughton-Smith: “I have heard that SwiftUI has been losing political capital, and credibility, internally at Apple because it has repeatedly failed to meet software engineering goals, and needs. It’s no longer thought of as the clear default choice for new stuff. That might explain why it was deemphasized at WWDC compared to the past few years.” Spicy stuff. I look forward to the next edition of "Apple’s internal use of SwiftUI" by Alexandre Colucci. We can cross-reference whether this rumour is substantiated by seeing whether the SwiftUI usage has plateaued across the internal iOS binaries. Read the ultimate scientific performance comparison right here 🧪 blog.jacobstechtavern.com/p/swiftui-vs-u…

@TimSweeneyEpic @Zhuinden Uhm, but their plans to close Android from installing apps from "unauthorized" developers remain unchanged?

Google is opening up Android all the way with robust support for competing stores, competing payments, and a better deal for all developers. So, we've settled all of our disputes worldwide. THANKS GOOGLE!

@valigo It's funny how they say "that one is just for basic tasks like web browsing" while the web stuff is so bloated nowadays that it consumes enormous amounts of RAM.

8gb of RAM laptops are back on the table. Programmers better figure out how to write software, because bloated Electron slop won't cut it going forward with prices the way they are )))

@Zhuinden Still the best way of doing UI on Android!

This is what newly written code looks like in 2026 #androiddev

@mahersafadii @pepicrft @SwiftLang Yup, and that concurrency stuff with the actor model was probably last nail in the coffin.

@pepicrft @SwiftLang I saw it coming ngl, the concept of Swift sounds good on paper but once you get your hands dirty with it you realize how bad of a language it's become, Swift peaked around version 4 and went downhill around version 5.7 when apple decided bloat it to make swiftUI look good

@SumitM_X It means you'd rather switch from json to something else.

Your API needs to process huge JSON payloads (5–20 MB) from clients. How do you design it so parsing alone doesn’t choke your CPU?

@Codelaby @krzyzanowskim Aren't Kotlin coroutines also a mess?

@krzyzanowskim I've only been developing iOS for two years, coming from a solid architecture and a modern language like Kotlin/android. I'm completely lost with swift concurrency.

🤔 but if Swift Approachable Concurrency is so approachable, why would it need so many lengthy explanations? I keep reading about it for months and apparently again everyone else is using it wrong

@valigo Look what FP people do for calling functions! 🤣

OOP people are crazy. They will take the most mundane thing in programming ever - passing arguments to a function, and call it DEPENDENCY INJECTION, and then will sell you books and courses about it.

@ayushagarwal You should, actually. On different systems people may want slightly different stuff there.

can you put .gitignore in .gitignore?

@ronaldmannak UIKit is still the best way to develop for iOS. Just like Java + Android Views for Android. The most simple and direct way of implementing things...

I don’t know what happened to Android development but sure can confirm the decline of native iOS/macOS development due to Apple dropping the ball on SwiftUI (great idea, bad execution) and Swift itself. In hindsight, UIKit+AppKit weren’t really so bad. But can we please kill the word ‘scale-up’ wtf is a scale-up anyway?

@krzyzanowskim The Guardian? Isn't that UK? 🙂

America puts cookie banners on a whole other level. I prefer the EU way, thank you very much.

@twannl Hmm, I recall they recommended to avoid doing heavy computations with Swift Concurrency. Did they solve that issue?

I've migrated 20+ packages to Strict Concurrency recently. I see this misconception trapping developers all the time: "Swift Concurrency is only for network calls." Many developers add async/await onto their URLSession calls and call it done. Meanwhile, their CoreData fetches block the main thread, file operations crash randomly, and image processing stutters the UI. Swift Concurrency brings cooperative multitasking to every part of your app that touches shared state. Your networking library most likely already worked fine. I've seen codebases where every disk write used DispatchQueue.global() without any coordination and that's basically data corruption waiting to happen. What ended up fixing the "weird crashes that couldn't be reproduced", was migrating to actors and async file operations. Bottom line, your local operations need async/await too: • Database queries (CoreData, SQLite, Realm) • File system operations (reading files, caching images) • Heavy computation (image processing, video conversion) It is only natural that network code gets attention because it's obviously async, but we should also not assume that local code works because "it's fast enough.". — 📌 I love helping iOS developers write better concurrent code. And over the years, I've identified the exact patterns that separate smooth migrations from disaster. It's how I help developers ship async/await code with confidence. That's why I created The Swift Concurrency Playbook - which breaks down 5 critical mistakes that even experienced Swift developers make. See the link in my bio to get instant access. #swiftdevelopment #iosdevelopment #swiftui #swiftlanguage

@JustJake Madness.

At Uber, we had 5000 microservices when I joined, and 8000 when I left just 18 months later One of the best developer experiences I've ever used, but hundreds of people required to maintain it Microservices are great, but only with the right tooling

@thekitze Lol, swiftui, kotlin compose - all that nonsense is made under the influence of React, so we know who's to blame. 🤣

some of you mfs live like this ??? 🤮

So, this Swift bug is still there? 🫤 forums.swift.org/t/didset-is-no…

Say whatever you want, but Swift enums are really inconvenient. It's a constant source of pain. stackoverflow.com/questions/5010…

@krzyzanowskim That’s for their training set? 🙂

@algridmd oh no

I don't understand coding agents score less than 100% on a test that is known upfront. do you manage to fail questions you had a year to learn and still decided: "nah, I know better" and fail gracefully?