But America is a big place. Americans living in cities probably know a first or second gen Persian, there’s lots of them everywhere. They even have a reality TV show.

Outside the urban archipelago the average person couldn’t tell you the difference from India, Turkey. and everything in between.

A weaker theorem can be postulated that any such filter provides a second order sufficient condition.

This means we can filter content by account creation date, for example, by hiding all posts and comments from accounts created after the digital death event. This won’t always guarantee human-only content but certainly more than otherwise.

But then we wouldn’t be having this most definitively human-to-human conversation, right?

The artificial stuff often has an odd taste, but boy it sure is quick and convenient.

That aside, there was a larger point I was making that was lost in the forest because you poking at a tree. iOS apps are more than Swift. Metal was one example, there are plenty of other tooling components that absolutely suck to use in vim, or just missing support entirely. Bundle management, plist files, custom build phases, code signing, asset previews, canvas previews, interface builder, profiling, and unit testing UI is a bunch of stuff that has nothing to do with swift, sucks in vim, and integral to application development.

Otherwise swift works just like any other clang/llvm project and the tooling is basically the same.

tcp_now’s maximum cannot physically reach 2^32 because the trailing zeros of that number exceeds the bit width of data type.

Therefore, tcp_now + 30000 will wrap when tcp_now is equal to 2^32 - 3000. Your inequality sign should be strict <, otherwise the result does not follow.

My uptime resets only when forced by an OS upgrade and I have never experienced this issue. This is consistent with the sleep-heals-the-stack theory.

Not sensible. completely insane.

That means there are exactly two of us.

But you can bridge build setting variables using some clever xcconfig macros that combine both preprocessor systems.

But a lot of what you said, except for the concurrency and property wrapper stuff, largely exists for Obj-C interop. The generated interface is more readable, and swift structs act like const C structs. It’s nice.

There is a particular hard drug that I could be easily addicted to if it were cheaper and more accessible. Nothing else like it gives me irresistible craving for more. Not nicotine, ADHD meds or speed, benzos, and not even opioids have the same effect. So after I discovered this about myself, I went on a little journey to self test myself other possible addictions.

Social media? Nope. Video games and tv? yes. Gambling, hoarding, shopping: No. Sex: yes. Exercise: yes

I can’t rationalize any of it.

Go look at any of Apple’s sample code. Outside of UIKit/Appkit, most of their samples target both platforms simultaneously

And no just because the compass is #ifdef’d out when CoreLocation is compiled for MacOs does not count as “divergent”

What does this mean? Mac Catalyst is native. It’s just a thin bridge between iPhone’s UIKit and AppKit on MacOS, which are really the only two divergent frameworks in the entirety of the massive Apple SDK.

What is this in reference to? I tried to search for it but only found this comment. “Github while loop fix that was in review for a year”?