XTool – Cross-platform Xcode replacement

https://github.com/xtool-org/xtool

#HackerNews #XTool #Xcode #Replacement #Cross-platform #Development #Open #Source #Software

Yes, Xcode, that's exactly what I was looking for, I wanted to print the CSSM_CERT_X_509v1'th timer in the timers array

If you are having trouble reading Instruments flame graphs, the following article may help:

https://swiftdevjournal.com/posts/instruments-flame-graph-intro/

I spent days figuring out how to get a piece of data from .xcactivitylog. Why does #Xcode make everything so hard?

Well, fine then, don't tell me. #Xcode

Xcode 16.4 release notes contains a note on excessive CPU utilization from diskimagesiod which reduces simulator performance, increasing boot time, process launch times, and test execution times. (146716769) (FB16818022)

Apple Weather App (Benja’s Version)
A minimalist take inspired by the original Apple Weather app.

Check it out on GitHub: github.com/benjaminrsalgado/weather

Very rewarding to be at the point where new features build on foundational code I've already written

Added export of maps as images and copying a map to the clipboard in about 2 hours.

That may not seem all that quick but consider you are starting with #Xcode -> New Project and think about how much goes into getting to what feels like magic where you press Cmd-C and boom, there is an image of the map on the clipboard.

Did iOS 18.5 released without a released version of Xcode? I went to install the simulator in 16.3 and nothing...

I'd really prefer to not be required to use a beta version different from our CI version.

That feeling when you finally recall how to resolve that nagging #Xcode console warning that's been there for months.

Is your iOS app slowing down due to network calls?

In my latest video, I’ll show you how to use Instruments to find network bottlenecks and fix them with image caching using NukeUI.

Watch now and speed up your SwiftUI apps!
https://azamsharp.teachable.com/courses/azamsharp-pro-for-all-content/lectures/61401178

When using Swift Packages in #Xcode, why can't we give a name to the new created file from a template?

It's always the same default name like "SwiftUIView.swift" for a #SwiftUI view...

Did #Apple finally release the promised

NSWritingToolsBehaviorNone

for NSTextFields in #macOS 15.5?

So far that only works with the more massive NSTextViews, and I really need to disable this stupid "feature" for most of the text input fields in my pro application that doesn't need useless AI slob...

Xcode Cloudで任意のバージョンのRubyを使う
https://dev.classmethod.jp/articles/xcode-cloud-custom-ruby-version/

Random Xcode shortcut discovery: if you're using a string catalog (e.g. Localizable.xcstrings) and you have a call to something that takes a String.LocalizationValue or LocalizedStringKey (e.g. String(localized:) or any SwiftUI component like Text() that takes a localized key argument), command-clicking on the string constant will jump you directly to the corresponding entry in the string catalog. #Xcode #SwiftUI

I never said how much I appreciate the person at Apple who decided to add specific doc links to every separate notarisation error

Enabling selective testing in Xcode projects is as simple as prefixing your xcodebuild command with tuist; such a clean and easy adoption pattern. And to top it off, you also get a handy dashboard to better understand your test suite #Xcode #Swift

XCMetrics revolutionized the collection and presentation of metrics from Xcode builds, transforming them into useful and accessible insights. Now, we're elevating the experience, enhancing it with top-notch design and developer-friendly features.
#Xcode

I really like Swift Testing custom traits because they're incredibly useful for enhancing the ergonomics of writing tests. Here's an example we're including in the next version of FileSystem: https://github.com/tuist/FileSystem/pull/125

I guess Xcode still doesn't have a way to catch these errors? I load assloads of data asynchronously via operations and putting breakpoints/logging in each is not a fun task. Why can't I set a breakpoint where this error happens or force Xcode to throw an exception? This "you have an error but we're damned will not going to help you find it" attitude from Apple is so tiring.