“smb big sur”

I figured I should try and see how much faster I can make a simple test by using simd vectors rather than the equivalent struct types (in Xcode 7 / 7.1 beta 2).As a simple start I wanted to compare simd's float4 with a simple struct like this:struct MyFloat4 { var x, y, z, w: Float }So I used big Array<MyFloat4> / Array<float4>, and measured the time it took to assign them all, perform some operation on them like multiplying them with some constant MyVector4 / float4, etc.As I have not yet managed to write a test where simd makes the code any faster, I'm thinking:- Probably the compiler is producing simd code on its own when optimizing my simple benchmarks, thus it doesn't matter if I use simd or not.- But In what kind of code will it matter? Can anyone write a simple example that shows using simd is faster?(Yes I'm using highest optimization level, no emitted debug info, whole module opt)

I'm running iOS 9.0.1 and using the 10.11 GM and cannot get airdrop to work between my iOS device and OSX.I've spent days trying to troubleshoot this issue.I've got a Macbook Air (2014) (currently El Capitan GM) and an iPhone 6 (9.0.1).My wife has another iPhone 6 (iOS 8.4)I've tried for days to get airdrop to work and it's simply not working from OS X to iOS.It's so frustrating. I've had it work before in the past, but never reliably.Anyway,iOS to iOS airdrop works between the two iPhones (8.4 to 9.0.1) and vice versa. No problem every time - either way.I've followed every article I can find, from voodoo like 'pairing' my iPhone to my Mac, all the way to having the firewall disabled or enabled, to having bluetooth preferences open to SMB sharing being enable to AFP sharing on or off, such nonsense but I tried...For a while I was playing with trashing various BT preferences/network prefs, but since the 3 complete clean installs I'm gonna guess prefs have nothing to do with it. iCloud signed in and ou

Hello!Basically, I've been working on a project for a rather long time now - and today I finally finished it. However, XCode seems to be unable to archive my project. What I mean by that is that it just stops on 'Compiling Swift Sources, and then it stops forever. My project is not big at all, and if my computer is righ - the size of my project is only 860kb. However, the project contains a huge array with over 1200 words. I don't know if this is what causes the problem?It may be worth mentioning that my Mac is from mid 2010 (13-inch Macbook pro), and I fear this might be the problem - that my PC is just unable to handle the compiling process, with its only 4GB of RAM. I just wanted to hear from someone here, before I eventually buy a macincloud subscription, or if this can be solved.Thanks in advance.

I'm trying to submit an app to iTunesConnect for Apple TV.When I try to upload, the build goes into processing, then I get an email like this:Thinned app size is too large - The app bundle at '/Payload/appname.app' exceeds the maximum allowable size. A tvOS app bundle must be less than 200MB after app thinning.Wow, pretty helpful. Am I at 205MB, or 2GB?I have split some of my resources up into On Demand Resources. Xcode shows me sizes for each of the ODR sets, but how do I know how big my main bundle is?

Hi,My app Chronic Timer is on both iOS and WatchOS. On iOS I use iAds as a method of montization. I'm surprised Apple doesnt allow you to set seperate price points for iOS app vs Apple Watch app.Because there is no ad model for Apple Watch (justified), I want to set the price for the Apple Watch app at lets say $1 and keep the iOS app free (Ad supported). Currently I would need to seperate the apps into two projects and thats ugly because of several reasons- No handoff support- I would need to add all the functionality on Apple Watch app. Right now I let users create routines on iPhone/iPad and push it to Apple Watch app- Apple Watch app would have a blank iOS appThis in my opinion is critical to the success of Apple Watch. I already mentioned this on several occasions to Apple. Without developers ESPECIALLY indie developers, iOS and WatchOS will go the direction of Windows. And though the initial hype is working and there are 10000 WatchOS apps already, they are weak. Thats due to several reasons:- WatchOS h