I'd be willing to bet that Apple's call start with a statement that they are recording the call, that means you can record the call to because they know it's being recorded.
When a call starts with "this call may be recorded for quality assurance", I always say "thank you" to express my gratitude for them granting me explicit permission to record it.
"two-party consent" laws have been adopted in California, Connecticut, Florida, Illinois, Maryland, Massachusetts, Montana, New Hampshire, Pennsylvania and Washington.
Its unfortunate that this doesn't promote trying to get business users to look at the code. In our organization 3 or 4 users are read only and really just go in at times to check specific errors, or logic for certain SQL queries, they don't really contribute. We will now have to pay $9 per month for these type of "read only" users.
Couldn't you use some other kind of display for these users? Seems like you'd only need 2 or 3 of these to justify a small project to get them the information they need without needing to be a paying GitHub user.
It seems like Disque is a "simplified" Kafka, or a more vertically purposed Redis. It seems that it differs from RabbitMQ significantly because rabbit requires a queue to push the messages in, while Disque allows jobs to be pushed independently of consumers being setup.
Kafka is arguably simpler, at least in terms of data model, than Disque. Disque needs to handle acking and queue mutation and things like lock timeouts and dead lettering, all of which complicates its queue structure and API. Kafka queues (partitions, to be precise) are append-only, which simplifies a lot of things.
Yes, salesforce has no interest in appealing to the hobbiest developer. They focus purely on enterprise. Even as an SMB customer, I have a terrible experience with them.
Oh, I'm interested in the business decision behind that. For example why didn't they just buy (not acquire) the slack product. What were the reasons to host it in-house and manage it themselves.
