Learn More
Resend Email
8
xcodesucks
2d

Q: How do you know Xcode 16.2 is a mess?

A: The code it generates for a new project is rejected by the compiler.

You generate a framework project, and besides having to manually sign the damn thing (really, can't setup for success?), it won't compile and link due to some other obscure error IT generates.

/<pathToFramework>/<ProjectName>.framework: resource fork, Finder information, or similar detritus not allowed
Command CodeSign failed with a nonzero exit code

Yes, boys and girls, Xcode is broken right out of the gate on building a framework template it creates!

I'll tell you what is "detritus", it's Xcode. Hint to Xcode team: "Just Say NO" - Nancy Regan

devrant

#xcode #💩
Favorite
Ranter
Comments
  • 1
    2d
    "Finder information not allowed" then why is it there!? It's the same fucking vendor! Why do they ship tools that break each other? Who buys this crap?
  • 2
    2d
    I just feel like if you take the stance that creating arbitrary hidden files in every directory is acceptable, then you should design your tools to skip arbitrary hidden files in directories.
  • 1
    2d
    Finder's strategy isn't even that strange, the idea is basically that you should only read a hidden file if you're looking for that specific hidden file. All that's required to support it perfectly is to skip hidden files in all processes that are based on directory enumeration. It's not hard to design a dev toolchain that works like this.
  • 2
    2d
    The most surprising thing here is your surprise
  • 0
    2d
    @lorentz Worste crap ever. We have a lot of network drives and oh boy you can just follow the trace where the mac user went and opened folders... This is crazy, .DS_Store files in every folder just to remember icon sizes? It’s overkill.

    Maybe they think macOS users want customization on every freaking folder and would riot if it didn’t work that way.
  • 2
    2d
    My crapple using teammates would sometimes push giving .DS_stores to repos. That unnerved me greatly.
  • 0
    2d
    Q: How do you know Xcode 16.2 is a mess?

    A: it's Xcode. what do you expect?
  • 0
    1d
    @atheist 🤣
  • 0
    1d
    @tosensei I wish DevRant threaded... Your Q&A, spot on.
  • 0
    1d
    @Grumm It used to be that there was a data fork and a resource fork, or just one of the forks. It really worked well, especially the resource fork which was a binary precursor to .plist files. Elegant actually. But when storing such on Windows servers, in Windows you saw both file forks. Nothing was "invisible" on either side. Invisible files were a rarity. Now it's like the file system has STDs everywhere in the form of invisible crap.
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment