158 karma · joined April 17, 2011
Swift 5.0 and 5.1 each supposedly made some 10-20% gain in ARC performance compared to the previous version (4.2 and 5.0), so that may also help. I think Swift's performance can be very hit or miss but they (Apple) are making some good strides.
From the growth numbers listed in the report, the gross merchant volume (and therefore the Merchant Solutions revenue) is increasing so maybe more merchants are being successful or the existing successful merchants are selling more. The Merchant Solutions revenue is growing about 18% faster than Subscription Services.
Shopify seems to be trying to make more merchants successful (more merchants selling more goods) versus just making it easy to open (and close) unsuccessful stores.
Hopefully Shopify is able to capitalize on increase in merchandise volume if they haven't been able to negotiate a good deal on the payment processing fees themselves. While they might make profits (and not just revenue) from their monthly fees and their App Store, I just can't imagine a merchant platform which does not capitalize on gross merchant volume since that's where the significant profit comes from (like eBay, for better or worse).
Shopify's revenue from https://investors.shopify.com/financial-reports/default.aspx is $362 million and their GMV is $13.8 billion. Looking at their fees at https://www.shopify.com/pricing , they charge between 2% to 3%. This seems to be about right.
This is a superficial look but, I think to your original question, the revenue should be comparable.
However, for the issue mentioned in the post, wouldn't 2FA have saved him? Supposedly, the compromised credential is from 2015.
The book iOS and macOS Performance Tuning ( https://www.amazon.com/iOS-macOS-Performance-Tuning-Objectiv... ) has pretty damning benchmarks against Swift versus Objective-C even without using any tricky optimizations (not what you originally asked but something to consider). Of course the whole book (written by a former Apple engineer IIRC) is pretty much full of performance gotchas across many Apple frameworks/APIs, but the chapter on Swift was pretty harsh and basically said Swift fails to live up to its name versus Objective-C (at least at the time the book was written).
I think most people think that Swift performs like Rust/C++/C since it doesn't have a garbage collector and imagine ARC is providing relatively free memory management, but it seems Swift performs closer to languages with a garbage collector due to the various design constraints on the language (interoperability with Objective-C, ARC isn't free, and maybe without the explicit lifetime/ownership declarations in the code like Rust, ARC can't be optimized as well).