Commonly the 1 unhappy customer might tell his story to ten of their friends or thousands+ of readers online. Fixing customer problems (especially drastic ones) carries large incentives, because those single stories will actually be observed, while the 1000 happy customers won‘t be mentioned.

The company will only fix problems for customers with sufficient social reach in that case.

Case in point:

20 years ago DHL told me the credit cards I was waiting for in Santa Cruz, California were suddenly in transit to South Korea.

As a one off it was a funny story. 10 years later they told me the computer that was sitting in a depot in London was on a ship back to the US.

I'll keep telling those stories until everyone involved had long since retired.

I would assume that a large chuck of the revenue is generated by few highly successful developers, for which they continue to charge 30%

B-but those are corporations! You can't have empathy for anyone who revenues more than 1 million a year, right?

We build a web app for e2ee file transfer:

https://arcano.app

Does this actually mean that LittleSnitch could continue to function as is - with the same kernel extensions used until now?

> To allow installation of software that uses kernel extensions, select the “Allow user management of kernel extensions from identified developers” checkbox.

Would LittleSnitch now not technically be able to continue using the kernel extensions it relied upon?

> To allow installation of software that uses kernel extensions, select the “Allow user management of kernel extensions from identified developers” checkbox.

Mapbox if you are looking to integrate something into your website / app

This is still my primary reason to use GMaps - I wish they would prioritize Public Transport in Apple Maps - SBB even provides an API they could easily use to get any schedule they need as far as i know.

Good point about the billing. In our case FAAS is not offered by the cloud provider (yet), but we are stuck with them. They want us to spin up a server for every service. We started doing micro-services, but it’s just so much overhead compared to serverless. I rather deploy something like this, even without 1-1 mapping in regards to billing.

I’ve been using Concourse CI and it’s fairly light weight and has great declarative pipelines. Learning curve is not too steep and it has a command-line tool to update your pipelines. Maybe it’s a stupid suggestion, but you could connect the worker in that setup through ssh to a Mac for building, but of course that takes away some of the comfort, but you will have to run a dedicated build machine anyway.

Also, doesn’t Travis CI have macOS support ?

+1 to Concourse. Though if the OP needs OS X build support, there is no escaping needing a Mac box to run it on.

One can still run Concourse on a Mac Mini if one chooses, not that much extra work. This is the simplest solution but you will still need XCode Server last time I checked (been a while). I'm sure there are ways to hack around it, just a matter of time vs money question.

Both Travis CI and Circle CI offer Mac builds, so if one is willing to spend some money, that's an option.

Having had to run my own CI infrastructure, I'd rather pay someone else to deal with it. Especially if your deploys are tied to it, as once it breaks, and it will do it, your entire pipeline is down.

I ended up spending a good chunk of my own time dealing with failing builds or having a couple of people on my team be the point-persons for CI/CD infra.

I need to build and run tests on macOS, so I‘d need to circumvent the core principle of Concourse (containerized builds). I really don‘t want to work against my CI system...

When you enable airplane mode, you can actually see WiFi and Bluetooth crossed out as opposed to grayed out. So there is a difference in UI, but I agree - this is not intuitive to the user.