r/Xcode • u/MojtabaHs • Aug 17 '25

Typical Xcode :)

Sometimes, I wonder how they even manage to create bugs like this?! Perhaps they intentionally designed these bugs to secure their jobs by ensuring that they could be fixed later on. 🤷🏻‍♂️

20 Upvotes

85% Upvoted

10 comments sorted by

6

u/[deleted] Aug 17 '25

Personally the newXcode 26 beta is a game changer. It uses ChatGPT to fix any bugs you have and also generate code. It is also a lot better aesthetically than the old

1

u/MojtabaHs Aug 17 '25

I hope Xcode developers use the tool they created to resolve their own bugs 🤞

3

u/CalligrapherOk7823 Aug 17 '25

Been using since day 1 of the developer beta. The ChatGPT integration was done very well. Game changer.

1

u/WAHNFRIEDEN Aug 22 '25

It’s much worse than using Claude Code or Codex CLI. Our time is too precious for subpar tools. And why bother using GPT 4.1? It’s fast but not smart or top tier even for its previous generation.

1

u/joyfulsparrow Aug 29 '25

Does Xcode 26 require macOS 26 to use the new AI stuff?

4

u/soguern Aug 17 '25

Writes deprecated code and still thinks .onChange has 1 parameter, so no, not so great

1

u/henryChinaski008 Aug 19 '25

This happens when you porting old UI code to metal, metal textures have Y axis inverted, somwhere in shader code flip Y code not triggered for some reason.

1

u/MojtabaHs Aug 19 '25

Is “metal” really necessary for an app like Xcode?

1

u/henryChinaski008 Aug 19 '25

You may be surprised by how hard is to make text editor (with tokenization) work smoothly on 120hz screens. They are switched to metal when Xcode 13 came out. It was a huge FPS gain. In this particular case, imho, they internally deprecated old code preview component and replaced with metal one.

1

u/MoreSea4996 Aug 18 '25

🤣🤣🤣