_mlxl's comments

I had this and then got an M1 MBP and it flickers wildly on dark backgrounds when connected via USB-C. I think that's going to be my last Apple laptop.

I don't even know how to make strings in C, how the hell am I going to code on a quantum computer. Sigh.

Haha I didn't notice the reference, that's great!

Bit off topic but I love the NetBSD logo. It's very pleasing on the eye.

Are you sure they aren't being run through Rosetta? If I remember correctly, x86 apps run through a translation process on first launch which obviously takes time. An acceptable trade off given the alternative is to not have the app at all on Apple Silicon.

I was just thinking the other day that searching for TODO is probably a very good way to search a project for potential bugs or security issues. E.g; I see a bunch of todos in Firebase iOS SDK that look kind of interesting to an attacker. Without looking into how the methods are called I can't say if they are actually exploitable (and I am sure Firebase is fuzzed to high-hell) but it was a little seed planted in my head.

It uses async/await so they are still coloured functions - which, while coloured, doesn’t make it more painful to call than Non-concurrent methods I guess

Yeah according to Apple TSan introduces from 2x to 20x slowdown

Assumption but I wonder if the thread sanitiser crashes the app on thread access violations in debug builds so you can debug?

I have an 8 core i9 @ 2.4 and 32GB Of RAM and opened this page in Safari and good grief it’s the worst performance of a web page I’ve ever seen, not joking. It’s practically unusable.

Given the product I’m curious is the performance of your landing page by design?

That reason being digital signatures. You can get the same confidence from posting an MD5 hash to check. Xips are an awful solution to fix a solved problem.

Other people in this thread have expressed it, but the reason it's not useful is because most developers are doing something like UML, but it's not UML - so you get none of the benefits of the Unified part.

When I see a good UML diagram I know immediately what the bit of modelled code does. When I see a weird, cobbled together diagram of bits of code the creator thinks defines the state, I have gained nothing of value from viewing the diagram.

I want people who haven't used Xcode to understand that this isn't a connection issue, there is something specifically weird happening with Xcode when you try to upgrade it.

It has to be wed to the OS in such a way that makes the propensity for this vague failure state to occur, because I've never had it happen with anything else.

Upgrading from the App Store sometimes will hang at 99% and no matter what you do save some weird incantations to remove stuff from this secret App Store cache to remove the download to begin its excruciatingly slow download again, only with the hope in your heart this impenetrable and silent error doesn't happen again.

And of course none of this is addressed by Apple. You think you can just download versions from the developer site? Well enjoy, and I am not joking, a 30+ minute unzipping of the .xip file (yep that's right, it's not a .zip).

Apple does not care about it's developer ecosystem, even though you are such a huge part of it's success. It's apparent in their thread bare documentation, their terrible tools, their greedy practises.

I get it. They are a business. But they do not deserve their halo.

Xcode unironically made me try to change career from iOS developer to pen tester. I've spent way too much time in its guts and I think its left a little bit of taint on my soul. It is unfathomably bad.

And Apple keep bolting stuff on to it (and the new stuff doesn't work - Canvas for SwiftUI previews for example).

It's slow, broken in numerous ways, depends on file formats that aren't used anywhere outside of Apple and completely undocumented. It is such a painful tool to use.

Insult? No no no! I didn't mean to insult you at all, I was trying to find a good common ground to try explain why the Xcode 12.5 release fixes this issue without belabouring points you already know!

A swift package manager product before 12.5 will be embedded inside your target and statically linked.

If you have more than one target using that product, you will end up embedding it more than once, which creates duplicated symbols in your binary, which leads to undefined behaviour when calling that symbol at runtime (which Apple don't allow for apps on the AppStore - ironically Big Sur on M1 Macs has a lot of duplicated libraries for x86 and arm64 which will cause a warning about undefined behaviour when you call them - do as I say, not as I do).

What happens now in 12.5 onwards is those products will be dynamically linked, meaning there will be one copy of it in your binary, that each of your targets can call symbols on, which gets rid of the duplication and the potential for undefined behaviour.

Do you know the difference between dynamic and embedded binaries?

Carthage supports XCFrameworks now which means this is no longer required.

> if you depend on a static library, it will both statically link it _and_ embed the binary

That's fixed in Xcode 12.5 https://developer.apple.com/documentation/xcode-release-note...

Looks like they've made an web-app (https://pod-sources.cocoapods.org/) to check the distinct sources of a pod so you can have a fish to see if a source location url changed behind your back.

Would be good to show a list of all repositories where there are more than 1 distinct source as most people who make pods just point to their Github repo release page.

It's very tedious to check the impact of this without that list.

I agree.

Coinbase is the trusted inlet to trading crypto for individual investors. One of the blockchains, Bitcoin, has a 1 trillion dollar market cap, and the next largest has 259 bn. And coinbase captures a fee of some large percentage of transactions on those.

He should be worth much more.