@vatsal_manot Why would it hurt them? The end consumer doesn’t care about Swift directly

@signalgaining It’ll increase the cost of development for them internally.

@signalgaining Apple lifers internally are retiring with fewer and fewer people left who actually understand how iOS and macOS fundamentals work (this reflected in the piss poor quality of almost every single new app they’ve worked on in the last few years).

@signalgaining Even in an absurdly bad case where they switch to web technologies like Electron, it’s a massive shift from their existing engineering bets, and that is a costly transition.

@signalgaining iOS and macOS development is becoming more and more arcane by the day. The cost of this is hemorrhaging time in all the futzing/trial-and-error (that is increasingly becoming the norm of any development cycle).

@signalgaining Worse still, the more the engineering culture rots, the harder it’ll be for them to fix. Complacency and sheer fucking imbecility has been sharply rising year-over-year for most of their software suborgs. You can’t just fire managers overnight, especially when your cultural

@signalgaining The rot will cost them more than the raw time lost due to it, because fixing it will take years at minimum. I’m not even factoring in how Swift already lags behind in being represented in frontier model datasets, the codegen experience for Swift is horribly stunted compared to